Talk:Vuze: Difference between revisions

Content deleted Content added

Inline

Latest revision as of 17:47, 1 August 2024

This is the talk page for discussing improvements to the Vuze article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: 1, 2, 3: 2 months

Software: Computing Low‑importance

	This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.SoftwareWikipedia:WikiProject SoftwareTemplate:WikiProject Softwaresoftware
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Computing.

Java Low‑importance

	This article is within the scope of WikiProject Java, a collaborative effort to improve the coverage of Java on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.JavaWikipedia:WikiProject JavaTemplate:WikiProject JavaJava
Low	This article has been rated as Low-importance on the project's importance scale.

Archives

1, 2, 3

This page has archives. Sections older than 60 days may be automatically archived by when more than 4 sections are present.

Mention and link to BiglyBT

BiglyBT is the continuation of the Vuze/Azureus open source project first created in 2003, and is being actively developed by the original coders. Bubbletruble (talk) 20:45, 7 January 2020 (UTC)[reply]

Call me suspicious, but to me it looks like another promotion campaign for Bigly is running again. The Banner talk 09:24, 8 January 2020 (UTC)[reply]

Yes, you are being overly suspicious. This is nothing to do with any promotion campaigns, this is an effort to document the reality which you’re actively disrupting. Andrej Shadura (talk) 11:58, 16 January 2020 (UTC)[reply]

It's worth mentioning it and even to have a dedicated article IMHO. This continuation is definitely quite active compared to Vuze: https://github.com/BiglySoftware/BiglyBT/graphs/contributors

--Tuxayo (talk) 18:29, 26 March 2021 (UTC)[reply]

To add to this, my question is whether or not this should be it's own article...or if we should just update the Vuze article with BiglyBT? It's a bit of an odd scenario, as the fundamentals around mainstream (because the 'fundamentals' technically have been around for 60+ years) coding have significantly changed since Azureus launched and even since it rebranded as Vuze. Realistically, Vuze is a fork of Azureus in the same way that BiglyBT is a fork of Vuze...yet Azureus redirects to Vuze. ^[1] Should the page be updated as BiglyBT, with Vuze being a redirect? Or should in it's own page like in the every body wiki? Thoughts? EarthBoundX5 (talk) 02:27, 14 September 2022 (UTC)[reply]

Expanding the "hiatus" section

After trying and failing to write a full article, as suggested by User:1292simon here and by User:Newslinger here, I’m going to expand the current Development hiatus section with more details about the infamous continuation of the project. Here’s a draft of it, please comment and help improve it.

Development hiatus and fork

The pace of development slowed in early 2017.^[2] As of February 2020, the latest entry in the development blog was dated April 2017^[3] and the latest code change was dated February 2018.^[4] The two main developers left the project and focused their efforts on a fork called BiglyBT^[5]^[6]. In the fork, the developers removed support for Vuze’s premium products and proprietary features^[7]^[8], namely DVD burning capabilities^[9], gaming promotions, sponsored offers and advertisement. In an interview with the Free Software Foundation, the project claimed^[7] to have changed the license from GPL 2 or later to GPL 3, but as of April 2020 the license statement in the Git repository remains GPL 2 or later.^[10]

In April 2020, TorrentFreak named BiglyBT the tenth popular BitTorrent client.^[11]^[12] As of that date, the client is only shipped by Arch Linux, Debian^[13] and Ubuntu.^[14]

In September 2020, BiglyBT was the first BitTorrent client to implement the version 2 of the BitTorrent protocol.^[15]^[16]

Andrej Shadura (talk • contribs) 19:53, 6 September 2020 (UTC)[reply]

References

^ https://www.ghacks.net/2017/08/05/biglybt-new-vuze-based-torrent-client-without-ads/
^ Andy (2017-08-03). "Tumbleweed at Vuze as Torrent Client Development Grinds to a Halt". Archived from the original on 2020-02-12.
^ "Vuze Dev Blog". Archived from the original on 2020-02-12.
^ "Vuze - Azureus / List azureus-commitlog Archives". Archived from the original on 2020-02-12.
^ Ernesto Van der Sar (2017-08-03). "Former Vuze Developers Launch BiglyBT, a 'New' Open Source Torrent Client". TorrentFreak. Retrieved 2020-05-05.
^ Petr Urban (2017-08-07). "Vývoj Vuze stojí, původní vývojáři stvořili otevřeného nástupce. BiglyBT je bez reklam" [Development of Vuze halts, original developers created an open successor. BiglyBT has no ads] (in Czech).
^ ^a ^b "The Licensing and Compliance Lab interviews BiglyBT". Free Software Foundation. 2017-11-29. Archived from the original on 2018-10-28. Retrieved 2019-12-30.
^ "BiglyBT". Chip (in German). Die Entwickler der Software BiglyBT wollen das Vuze/Azureus-Projekt fortsetzen. Falls Sie Nutzer von Vuze/Azureus sind, können Sie die vorhandenen Einstellungen, Downloads und Plug-ins direkt in BiglyBT übernehmen. So ersparen Sie sich eine Neu-Konfiguration und können das Torrent-Netzwerk sofort nutzen.
^ Jon Martindale (2020-05-14). "The best torrent clients". Digital Trends.
^ "BiglyBT/LICENSE at 31511721436a92beab1358577f43f61c81050545 · BiglySoftware/BiglyBT". GitHub. Retrieved 2020-04-29.
^ Ernesto Van der Sar (2020-04-05). "uTorrent is the Most Used BitTorrent Client By Far". TorrentFreak. The list is further completed by qBitTorrent, Deluge, Free Download Manager (FDM), and BiglyBT. The latter is operated by former developers of Vuze, which was the second most-used torrent client ten years ago, but is no longer actively developed.
^ Gordon, Whitson (2019-09-13). "The Best BitTorrent Clients for 2019". PC Magazine. Retrieved 2020-04-29.
^ "Accepted biglybt 2.2.0.2-1 (source all) into unstable, unstable". Debian. Retrieved 2020-04-29.
^ "Information for biglybt". Repology. Retrieved 2020-04-29.
^ Ernesto Van der Sar (2020-10-11). "BiglyBT is the First Torrent Client to Support the BitTorrent V2 Spec". TorrentFreak. BiglyBT is the first torrent client to add full support for the BitTorrent v2 specification, including hybrid torrents. The client is far ahead of the curve as the first torrent site has yet to adopt the new specification.
^ Дмитрий Степанов (2020-10-13). "Выпущен первый торрент-клиент нового поколения с ускоренной закачкой и экономией трафика". CNews.ru.

Please note that @1292simon: did ask for a disclosure of any possible Conflict of Interest. This issue is not yet addressed. The Banner talk 20:56, 6 September 2020 (UTC)[reply]

That issue has been addressed by me from the very beginning: I have no conflict of interest to declare. Andrej Shadura (talk) 15:43, 7 September 2020 (UTC)[reply]

Then why are you so furiously trying to give BiglyBT a place op WP after the many, many earlier rejections and removals? The Banner talk 16:38, 7 September 2020 (UTC)[reply]

And please note that I am not an administrator, so I do not push my own agenda with removals of BiglyBT. It is all done in correspondence with the community and in accordance with the notability guidelines. That seems already to be a major stumbling block for your campaign. The Banner talk 17:03, 7 September 2020 (UTC)[reply]

I'm afraid to disappoint you, but there's no campaign anywhere except maybe your imagination, you're fighting with windmills here. I'm not furious, and I'm doing this because that's the right thing to do. As I mentioned in the archived thread, BiglyBT is the same project as Vuze, similarly as Vuze is the same as Azureus, with the same people working on it. It obviously belongs in this article: Vuze as such no longer exists really. Andrej Shadura (talk) 12:53, 8 September 2020 (UTC)[reply]

I only happen to notice that you are already pushing BiglyBT for the last three years or so. The Banner talk 13:29, 8 September 2020 (UTC)[reply]

That claim is grossly untrue. I'm not pushing for BiglyBT, and I only learnt about its existence last summer. Andrej Shadura (talk) 13:56, 8 September 2020 (UTC)[reply]

BiglyBT is the 10th most used BitTorrent client in 2020 and is frequently mentioned in reliable sources (in the rare case that any specific BT clients are mentioned at all). Vuze on the other hand is very rarely mentioned in the media since the development stopped. The most recent reference on the Vuze page is from 2017. As such I would say that Vuze no longer meets the criteria for notability. I propose that the content of this article should be moved to the "History" section on a newly created BiglyBT article (Although the list of features and the weird "only shipped by" comment should definitely be removed from Draft:BiglyBT before the article is created). Disclosure: I am in no way affiliated with Bigly Software or any of the people involved, nor have I seen any marketing material from them, just a random user who went to the Comparison of Clients page while considering switching from qBittorrent and was surprised that BiglyBT wasn't there. Zarano (talk) 16:12, 28 December 2020 (UTC)[reply]

10th out of 13 listed with a market share of 0.3%. Not really proof of notability. The Banner talk 19:05, 28 December 2020 (UTC)[reply]

Vuze isn't listed at all and has no references newer than 2017. So why does Vuze meet the criteria for notability? What does Vuze's article have that Bigly's doesn't? Zarano (talk) 11:16, 30 December 2020 (UTC

Notability is not temporary. The Banner talk 15:33, 30 December 2020 (UTC)[reply]

And Free Download Manager (0.2%) and BitLord (0.1%) do have articles while MediaGet (3.7%) doesn't and BitSpirit (0.2%) was deleted in 2017 for not having any updates since 2010. Zarano (talk) 11:59, 30 December 2020 (UTC)[reply]

As notability is not temporary, it is not unlikely that Free Download Manager and BitLord were more important in the past. At the same time it is very possible that nobody was interest to write an article about MediaGet. BitSpirit was deleted as non-notable. The Banner talk 18:59, 26 March 2021 (UTC)[reply]

May 2024

I'm going to try and start this again. @The Banner, I also agree that information about this should be added. In fact, I think that the sources above even meet significant coverage; I'm counting at least 5 articles that go in depth. Sure it could use some better writing and some of the details are cruft, but as a matter of principle we definitely should include this.
There can be a very simple reason that Andrej tried to add this other than bad-faith imaginations: he uses it and is a fanboy, duh. Aaron Liu (talk) 12:53, 10 May 2024 (UTC)[reply]

Sorry, what do you mean? The Banner talk 14:39, 10 May 2024 (UTC)[reply]

Which part? Aaron Liu (talk) 14:42, 10 May 2024 (UTC)[reply]

Your whole edit. Not a clue where you are referring too. Specific packages? The Banner talk 16:02, 10 May 2024 (UTC)[reply]

Where the heck did I say package?

TL;DR I believe that the amount of coverage BiglyBT has warrants a paragraph here, and perhaps even an article. Aaron Liu (talk) 17:00, 10 May 2024 (UTC)[reply]

Ah, yes. Another round of BiglyBT. Good luck. The Banner talk 11:04, 11 May 2024 (UTC)[reply]

I'll take that as a go-ahead for working on a draft to include into this article first. Aaron Liu (talk) 15:10, 11 May 2024 (UTC)[reply]

BiglyBT is not a Vuze project, so it does not belong here. Write it as a draft for a new article. My advice is to click on the link BiglyBT and see how much the article is protected due to spamming and disruptive editing. The Banner talk 00:02, 13 May 2024 (UTC)[reply]

Nobody said that you can't include notable forks under their parent articles. Just look at Terraform (software). Notability and worthiness can change, and the events in 2020 definitely make this worthy enough of inclusion if it wasn't already; which is why I tried to discuss here first. Aaron Liu (talk) 00:16, 13 May 2024 (UTC)[reply]

WP:OTHERSTUFFEXISTS is not an argument. The Banner talk 09:26, 13 May 2024 (UTC)[reply]

Then what policy do you base yours on? Aaron Liu (talk) 11:08, 13 May 2024 (UTC)[reply]

WP:NOTPROMO. The Banner talk 14:24, 13 May 2024 (UTC)[reply]

How are we writing unverifiable puffery here? Aaron Liu (talk) 14:42, 13 May 2024 (UTC)[reply]

My advice is that you write a a draft and submit that for inclusion. The history of BiglyBT & Wikipedia is rough and complicated enough that it is better to follow the high road. The Banner talk 15:46, 13 May 2024 (UTC)[reply]

I do not want this to be a separate article, as I don't think it has sufficient notability to warrant an independent article. But there is enough weight for coverage in this article, and the only reasons I see against including this are your vehement opposition plus past proponents not knowing how to argue. resulting in sanctions on the latter for the good reason of being unproductive. So, could you tell me why you're that opposed to including BiglyBT in this article? Aaron Liu (talk) 16:39, 13 May 2024 (UTC)[reply]

BiglyBT is not a Vuze-project, so it does not belong in this article. The Banner talk 17:24, 13 May 2024 (UTC)[reply]

There is no guideline that states that articles must only contain information on the subject itself, and I see no reason to argue for that. Also, here's an example that has been reviewed: OpenOffice.org was reviewed at FAC. Despite its entire section dedicated to forks, no complaints were made because of that; instead, it was declined due to awkward prose (and a place where citations weren't bundled). So, yes, there is precedent to include notable forks. Not to mention that BiglyBT is arguably an Azureus project as its creators were active developers of the latter.

I sincerely doubt that other editors would agree with you. As we seem to have reached an irreconcilable point, I have listed this at WP:3O. The diff I intend to introduce is Special:Diff/1223559975. Aaron Liu (talk) 19:49, 13 May 2024 (UTC)[reply]

You are predictable. The Banner talk 20:04, 13 May 2024 (UTC)[reply]

3O Response: The Banner, I think you're having a knee-jerk reaction to the information Aaron Liu is trying to include because of the history of spammers associated with it. What is relevant for inclusion in an article is based primarily on what reliable sources have to say about it. Aaron Liu has presented several independent sources that cover Vuze and BiglyBT in the same breath. Snowmanonahoe (talk · contribs · typos) 20:19, 13 May 2024 (UTC)[reply]

I advised mr. Liu to write a draft for a separate article about BiglyBT. He refused that, stating that the package is not notable enough for an own article. If it is not notable, why should you add the info to another article as it is still not notable? The Banner talk 21:01, 13 May 2024 (UTC)[reply]

Notability applies to the topics of articles, not all the information inside them. Snowmanonahoe (talk · contribs · typos) 21:02, 13 May 2024 (UTC)[reply]

It may be borderline notable, but due to what little information there is, I doubt that merging wouldn't be better. Aaron Liu (talk) 21:34, 13 May 2024 (UTC)[reply]

Are there any more sources that states it use by the public, more recent than 2020? I would love to see if it garners more use than the 0.3% in the Torrentfreak list. The Banner talk 21:49, 13 May 2024 (UTC)[reply]

I can't find any sources newer than TorrentFreak's on torrent client market share, but 0.3% is already pretty big and notability isn't temporary anyway. Something of note is that Vuze isn't even reported by their <0.1% mentions. Aaron Liu (talk) 23:29, 13 May 2024 (UTC)[reply]

True, notability is not temporary. And please note that BiglyBT was removed in the past as being not notable, despite the 0.3 percent market share. The Banner talk 10:10, 14 May 2024 (UTC)[reply]

Well, nobody else has ever removed it other than you. Aaron Liu (talk) 11:38, 14 May 2024 (UTC) Clarification: by removed, I mean remove from this article. My nature is to associate "removal" with "take away" instead of any deletion as a whole, which includes article deletion. Aaron Liu (talk) 18:03, 14 May 2024 (UTC)[reply]

So you ignore the history of the BiglyBT-article and now invent a consensus. The Banner talk 11:55, 14 May 2024 (UTC)[reply]

I believe the history of sanctions is due to previous proponents not discussing, your opposition, and less notability back in 2017.

You also haven't came up with more unaddressed arguments in opposition since 3O, so I think this is a rough consensus. Aaron Liu (talk) 14:35, 14 May 2024 (UTC)[reply]

I call it spamming of a non-notable package with very limited usage on top of that. You offered no new sources to back up the notability. The Banner talk 14:58, 14 May 2024 (UTC)[reply]

0.3% is not "very limited usage". It's a lot. Even if you somehow manage to ignore the fact that it's the tenth most popular, 0.1% market share [...] translates to roughly 25,000 logged connections. That is not "very limited usage at all".

You have not demonstrated why 9 reliable sources that cover BiglyBT is not enough for inclusion, not to mention that the Neowin one was new. Aaron Liu (talk) 15:13, 14 May 2024 (UTC)[reply]

0.3% is limited use, despite your claim. No matter what, 99.7% was using another package. The Banner talk 15:55, 14 May 2024 (UTC)[reply]

Please, I'm sure no one else agrees with this reasoning, which also doesn't change the existence of the nine sources. Aaron Liu (talk) 16:15, 14 May 2024 (UTC)[reply]

Sorry, but you sound like the marketing department... The Banner talk 16:28, 14 May 2024 (UTC)[reply]

And you sound like Hulk. Cheerio. Aaron Liu (talk) 16:33, 14 May 2024 (UTC)[reply]

I agree with that reasoning. 0.3% is limited use. MrOllie (talk) 20:48, 14 May 2024 (UTC)[reply]

Okay, it's nice that we can progress in this discussion.

While it would have more of a claim to inclusion if it were a biggest percentage, first and foremost, I do not see how our own interpretation of their market share has any bearing on Wikipedia guidelines and how we have 9 great sources that support inclusion and establish weight. Aaron Liu (talk) 21:04, 14 May 2024 (UTC)[reply]

If there are 9 great sources, why isn't there a stand alone article? MrOllie (talk) 21:07, 14 May 2024 (UTC)[reply]

Because there isn't enough material for a standalone article, 4 of these cover the same event, and 1 only mentions it in 2 sentences, but due weight isn't necessarily precluded by non-notability, and I believe that these sources establish due weight.

About the percentage, maybe the problem is that I'm a person who likes to think "this can save $1 billion from the US debt" instead of "this only saves less than 0.1% from the US debt". Aaron Liu (talk) 21:12, 14 May 2024 (UTC)[reply]

As Aaron Liu has explicitly pointed out to you, you have not presented any reason why the sources presented don't demonstrate due weight. Snowmanonahoe (talk · contribs · typos) 16:55, 14 May 2024 (UTC)[reply]

That's reversing the burden of proof. As WP:ONUS says, "The responsibility for achieving consensus for inclusion is on those seeking to include disputed content." MrOllie (talk) 20:50, 14 May 2024 (UTC)[reply]

This is different from ONUS, as we've already provided our proof, yet there has been no argument made against it save "they got 10th most used with only 0.3%", which doesn't seem very compelling, policy-based or principle-related. Aaron Liu (talk) 21:14, 14 May 2024 (UTC)[reply]

ONUS is about consensus, not 'proof', and you pretty clearly do not have it. MrOllie (talk) 21:15, 14 May 2024 (UTC)[reply]

Consensus is based on arguments made and to the extent Wikipedia policies and guidelines align with them, and the market share of the client has nothing to do with Wikipedia policy. Snowmanonahoe (talk · contribs · typos) 21:31, 14 May 2024 (UTC)[reply]

That matters for formally closed processes like AFDs and RFCs, but you will find that in other sorts of discussions you can't just tell someone you think that their argument is bad and then claim consensus. MrOllie (talk) 21:38, 14 May 2024 (UTC)[reply]

Okay, I expected that ONUS was a synonym for BURDEN. Apparently that's not the case. Thanks.
I believe that the modern, covered continuation driven by two original developers of this dead project really warrants inclusion. This is a similar situation to the relationship between OOo and LibreOffice, and IMO not including it would be doing knowledge a great disservice. Also, what do you think about being the first client to implement BitTorrentv2? Aaron Liu (talk) 22:33, 14 May 2024 (UTC)[reply]

IMHO irrelevant and spam. But that would be no surprise. The Banner talk 14:12, 15 May 2024 (UTC)[reply]

And what are your arguments against the fact that it is the current, working continuation, and how Vuze doesn't even appear in the usage ranking anymore? Aaron Liu (talk) 00:54, 19 May 2024 (UTC)[reply]

You are the one promoting BiglyBT, not me. The Banner talk 09:12, 19 May 2024 (UTC)[reply]

Your only arguments are that 1. It's not called Vuze and 2. I want to add BiglyBT? Aaron Liu (talk) 13:05, 19 May 2024 (UTC)[reply]

@MrOllieI wonder what your own opinion about this is? Aaron Liu (talk) 23:39, 21 May 2024 (UTC)[reply]

My own opinion is that a mention of a sentence or two might be warranted, but what is presently in the article drifts off topic. This is the article about Vuze, not 'Vuze and its forks'. Any discussion should be tightly limited to how the fork relates to its parent. The current version of the article goes beyond that. MrOllie (talk) 02:35, 22 May 2024 (UTC)[reply]

Pretty much every piece of notable software with significant forks has a section about the fork. For example Debian#Forks and derivatives (a good, peer-reviewed article!) and OpenOffice.org#Forks and derivative software. Per Wikipedia:Merging#Reasons for merging, If a page is very short (consisting of perhaps only one or two sentences) and is, in your opinion as editor, unlikely to be expanded within a "reasonable" (unspecified) amount of time, it often makes sense to merge it into a page on a broader topic. For example, parents or children of a celebrity who themselves are otherwise unremarkable are generally covered in a section of the article on the celebrity. Therefore, I feel like notable/significant forks are related enough to the topic here. Aaron Liu (talk) 11:40, 22 May 2024 (UTC)[reply]

Those are examples where the forks and derivatives are essential for understanding the impact of the original project. That is not the case here. MrOllie (talk) 12:05, 22 May 2024 (UTC)[reply]

I'm not sure how LibreOffice is more essential to understand the impact. Could you explain? Aaron Liu (talk) 12:58, 22 May 2024 (UTC)[reply]

You're comparing major projects which spawned a whole ecosystem of forks and derivatives, some of which (like LibreOffice) have more active users than all the bittorrent clients put together - with a project that has one fork that has a tiny market share. MrOllie (talk) 13:15, 22 May 2024 (UTC)[reply]

Good point. There's also Hudson (software) and Terraform (software), but these are both start-class; DOSBox is GA, but it only has a sentence for each fork, and the forks aren't as significant in this case either. I will check back later today to see if I can find nominal market share data. Aaron Liu (talk) 14:53, 22 May 2024 (UTC)[reply]

What you are doing is run up al kind of side tracks to avoid answering the real issues. In my humble opinion: WP:IDIDNOTHEARTHAT. The Banner talk 14:08, 22 May 2024 (UTC)[reply]

And what, exactly, is the real issue? Snowmanonahoe (talk · contribs · typos) 14:10, 22 May 2024 (UTC)[reply]

Lack of notability and promo. The Banner talk 15:37, 22 May 2024 (UTC)[reply]

How do we have a lack of notability? How do we have promotional language? Aaron Liu (talk) 15:53, 22 May 2024 (UTC)[reply]

While Ollie has been discussing with a lot of good points, I believe that you're doing here may constitute Wikipedia:Status quo stonewalling. Aaron Liu (talk) 14:53, 22 May 2024 (UTC)[reply]

I am not so much stonewalling, as you notice it is still in the article. But I challenge the usefulness of this addition. Fact is that there is no article BiglyBT to prove its notability beyond doubt. A prior redirect to a section is also removed. Plus you have no sources beyond 2020, when a source stated that 99,7% of BitTorrent users was using another program proving that it is limited in use. The Banner talk 15:37, 22 May 2024 (UTC)[reply]

A prior redirect to a section [was] also removed because you removed the section, duh.
How does the fact that it was from 2020 have any bearing on all of this? If you really want it, here's coverage from late 2021, but I think our current coverage is already enough.
You can't just zoom in on everything a source does not say. The fact is that torrent clients' competition are niche (save muTorrent), and you should not ignore that this is top-ten, has 75k connections, and was the first client to implement v2. You could be making the same argument for every competitor except muTorrent.
Also, not reverting does not preclude stonewalling. Aaron Liu (talk) 15:49, 22 May 2024 (UTC)[reply]

Are there any objections to redirecting BiglyBT to this page? I haven't been following this discussion, but glancing over it I get the impression that 2 users support inclusion of BiglyBT here, and two are against? It's certainly not notable enough to warrant a standalone article, but a redirect is appropriate as long as it's at least mentioned here. OhNoitsJamie ^Talk 20:57, 14 May 2024 (UTC)[reply]

See Wikipedia:Redirects_for_discussion/Log/2020_January_9#BiglyBT. The Banner talk 21:44, 14 May 2024 (UTC)[reply]

So TL;DR: the existence of the redirect hinges on whether BiglyBT material is accepted into this article. Back then, 4 of the sources we have here did not exist. Aaron Liu (talk) 22:25, 14 May 2024 (UTC)[reply]

It has more to do with the link being salted due to multiple recreations, so a redirect (or article) is not possible at this moment. The Banner talk 22:33, 14 May 2024 (UTC)[reply]

I may have forgotten to disclose that, but I contacted Jamie's talk page to have it unsalted before Ollie commented, as they is the last person to salt the page. Aaron Liu (talk) 22:35, 14 May 2024 (UTC)[reply]

You are invited to join the discussion at MediaWiki talk:Spam-blacklist § Remove BiglyBT.com. Aaron Liu (talk) 17:47, 1 August 2024 (UTC)[reply]

Present Tense

Why is this article in present tense when Vuze hasn't been actively developed, maintained, or used^[1] since 2017? Zarano (talk) 16:41, 28 December 2020 (UTC)[reply]

This Wiki lists the last version of Vuze as 5.7.6.0. I was just on the Vuze Page, and downloaded the installer. It is for 5.7.7.0, no idea of a Date of release. This suggests that Vuze is not as In-Active as it has been for around 5 years. Also it now has 2 levels, Free, and Paid with some unlocked features.

As to BiglyBT, it deserves it's own page with info on the Vuze page mentioning it is a Fork. While it says earlier in this Talk "Vuze is a fork of Azureus", this is not entirely true. A Fork is a Split from the original code. Vuze is the Re-Branding of Azureus. So redirecting Azureus to Vuse is logical. And unlike the recently updated Vuze, BiglyBT is Free, no hidden features. Though they do periodically have a popup for Optional Donations. NaPurHab (talk) 01:23, 15 September 2022 (UTC)[reply]

References

^ uTorrent is the Most Used BitTorrent Client By Far April 5, 2020

[1] ttps://www.ghacks.net/2017/08/05/biglybt-new-vuze-based-torrent-client-without-ads/

[2] Andy (2017-08-03). "Tumbleweed at Vuze as Torrent Client Development Grinds to a Halt". Archived from the original on 2020-02-12.

[3] "Vuze Dev Blog". Archived from the original on 2020-02-12.

[4] "Vuze - Azureus / List azureus-commitlog Archives". Archived from the original on 2020-02-12.

[5] Ernesto Van der Sar (2017-08-03). "Former Vuze Developers Launch BiglyBT, a 'New' Open Source Torrent Client". TorrentFreak. Retrieved 2020-05-05.

[6] Petr Urban (2017-08-07). "Vývoj Vuze stojí, původní vývojáři stvořili otevřeného nástupce. BiglyBT je bez reklam" [Development of Vuze halts, original developers created an open successor. BiglyBT has no ads] (in Czech).

[fsf2017-7] "The Licensing and Compliance Lab interviews BiglyBT". Free Software Foundation. 2017-11-29. Archived from the original on 2018-10-28. Retrieved 2019-12-30.

[chip-8] "BiglyBT". Chip (in German). Die Entwickler der Software BiglyBT wollen das Vuze/Azureus-Projekt fortsetzen. Falls Sie Nutzer von Vuze/Azureus sind, können Sie die vorhandenen Einstellungen, Downloads und Plug-ins direkt in BiglyBT übernehmen. So ersparen Sie sich eine Neu-Konfiguration und können das Torrent-Netzwerk sofort nutzen.

[9] Jon Martindale (2020-05-14). "The best torrent clients". Digital Trends.

[10] "BiglyBT/LICENSE at 31511721436a92beab1358577f43f61c81050545 · BiglySoftware/BiglyBT". GitHub. Retrieved 2020-04-29.

[11] Ernesto Van der Sar (2020-04-05). "uTorrent is the Most Used BitTorrent Client By Far". TorrentFreak. The list is further completed by qBitTorrent, Deluge, Free Download Manager (FDM), and BiglyBT. The latter is operated by former developers of Vuze, which was the second most-used torrent client ten years ago, but is no longer actively developed.

[pcmag-12] Gordon, Whitson (2019-09-13). "The Best BitTorrent Clients for 2019". PC Magazine. Retrieved 2020-04-29.

[13] "Accepted biglybt 2.2.0.2-1 (source all) into unstable, unstable". Debian. Retrieved 2020-04-29.

[14] "Information for biglybt". Repology. Retrieved 2020-04-29.

[tf-btv2-15] Ernesto Van der Sar (2020-10-11). "BiglyBT is the First Torrent Client to Support the BitTorrent V2 Spec". TorrentFreak. BiglyBT is the first torrent client to add full support for the BitTorrent v2 specification, including hybrid torrents. The client is far ahead of the curve as the first torrent site has yet to adopt the new specification.

[cnewsru-btv2-16] Дмитрий Степанов (2020-10-13). "Выпущен первый торрент-клиент нового поколения с ускоренной закачкой и экономией трафика". CNews.ru.

[17] uTorrent is the Most Used BitTorrent Client By Far April 5, 2020

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[1]