FrostWire beta 4.9.34
p2p news / p2pnet:- With the Digital Restrictions Management (DRM) LimeWire now out of the indie p2p picture, the growing FrostWire community has released its latest beta 4.9.34, less than 24 hours after the beta release of LimeWire 4.9.34.
FrostWire is proving that the open source community is ready if the network is threatened with unacceptable restrictions.
The primary task of the LimeWire beta is to allow users to edit metadata of programs, images and documents. As usual for a point release, there are some minor maintenance fixes as well.
The FrostWire beta mainly focuses on making sure the Windows, Linux, and Mac OS X installers are working as they should, and that the code synchronization with the main LimeWire repository is also up to snuff.
“However we are also trying to get more people working on the Java core, the interface and the C++ windows installer (based on GnucDNA – http://www.sourceforge.net/projects/gnucleus/) and NSIS (http://www.sourceforge.net/projects/nsis/),” say the FrostWire guys.
“If you are interested in maintaining LimeWire’s legacy get involved!”
Meanwhile, p2pnet has learned from usually reliable sources that LimeWire has been beating the bushes around Mashboxx, RealNetworks and Napster.
We asked the company for comments on this some days ago, but LimeWire continues to ignore requests for information.
Stay tuned.
Something you think we should know? tips[at]p2pnet.net
First they ignore you, then they laugh at you, then they fight you, then you win
- Mohandas Gandhi
Tired of being treated like a criminal? They depend on you, not the other way around. Don’t buy their ‘product’. Do bug your local political representatives. Use emails, snail-mail, phone calls, faxes, IM, stop them in the street, blog. And if you’re into organizing, organize petitions, organize demonstrations and then turn up on your local political rep’s doorstep, making sure you’ve contacted your local tv/radio station/newspaper in advance.
October 19th, 2005 at 3:45 pm
I can’t find it’s source code anywhere. On the download talk page, Gregorio links to LimeWire’s SourceForge CVS server, but nowhere is Frostwire’s own code available.
Is it just something I’ve misunderstood or are the Frostwire guys in breach of the GPL?
And, SourceForge’s rules say that all projects hosted on sourceforge must have a SF button or banner to keep getting hosted. I see no SourceForge banners (like the one on phoenixlabs.org for example) on Frostwire’s home page.
October 19th, 2005 at 4:14 pm
I’m not going to dignify that kind of stupidity with a constructive answer.
October 19th, 2005 at 4:19 pm
Humm, DaBlade is lost, really lost. Source is at the same place than other projects at sourceforge. If you can get the source via CVS, it has to be somewhere right? You don’t have to put a button or banner on a website not hosted on sourceforge either.
Please no bull, ok?
-et voilà
October 19th, 2005 at 4:42 pm
First of all, it says sourceforge.net/projects/limewire/. <–Note the _lime_
I don’t know if that’s what they call their SourceForge page. Might be.
If that’s the case, than their CVS is okay, no GPL breach.
But then they breach LimeWire’s trademark, unless they’ve gotten explicit permission from LimeWire to use that.
And sourceforge seems to be timing out right now, I’ll check the rules later. Maybe I got it wrong.
Oh, and chill, no reason to go postal!
Now don’t get me wrong, I don’t have anything against FrostWire whatsoever. I think it’s great that LW is finally getting a non-commertial alternative.
October 19th, 2005 at 4:43 pm
It’s a real shame about LimeWire. It was probably the best of the commercial p2p apps and contributed a lot to the p2p world. Just ask Penn State University. http://p2pnet.net/story/6326. I really hope it doesn’t end up with the likes of Mashboxx.
But as the post says, “FrostWire is proving that the open source community is ready if the network is threatened with unacceptable restrictions.”
It doesn’t matter what the RIAA and MPAA, etc, do, innovators will continue to innovate and the world will continue to move forward, leaving them and their masters on the sidelines.
Morg
October 19th, 2005 at 5:04 pm
The name on sourceforge.net is limewire because we didn’t know we would create an alternative at first. The creation of the project was to maintain source code of limewire as a backup elsewhere than the official LimeWire.org. Now with all the work done, it would be difficult to move to frostwire without loosing lots of time.
And we’re very friendly with LW devs, we talk with them everyday. We are just not tied like them to a corporation
When sourceforge active again look there for the source http://sourceforge.net/cvs/?group_id=142481
Under the project mailing lists, you can also see all the CVS commits made.
ciao
-et voilà
October 19th, 2005 at 5:13 pm
What is the indie P2P picture? Creative commons filtering would enhance the visibility of indie artists.
October 19th, 2005 at 5:47 pm
“Is it just something I’ve misunderstood”
I said that in my first post, so there was no reason to blast at me like the first two replies did.
October 19th, 2005 at 6:21 pm
sorry if I sounded rude in my first post, but the second was definitly not rude
Ciao
-et voilà
February 29th, 2008 at 10:39 am
SHIT STUFF HERE