Slashdot Mirror
Freedb.org Ending
haroldag writes "Freedb, the free music database used by tons of CD ripping software, has been shut down due to a disagreement among its developers. One of its developers used a data dump from the original freedb.org and is providing the service at freedb2.org, though, and will be adding features and posting them at his site as they become available. Unfortunately, a database dump or source code for freedb2.org is yet nowhere to be found."
I'm sorry the staff fell out, costing us access to a useful resource. freedb was a useful tool but it was always in need of improvement.
It really should have had facilities for submitting an md5 hash of the CD so end-users could avoid collisions, perhaps an easy way to edit or rate database entries, so that submissions where the track titles were wrong could be corrected by the community, etc...
Hopefully whatever replaces it will be better and more robust..
--
Damn is right.
Just stop being a bunch of cheap a-holes and BUY music that you like.
Umm if I was downloading MP3s from P2P networks, why would I need a freedb tagger? Find a source with EAC verified, high bitrate, properly tagged music and forget using this, chances are if it doesn't got the tags it'll suck anyway. CDDB, FreeDB and the like are fixes for an outdated format (CD Audio) from a time when noone needed those tags. Unless you think all the people ripping their own CDs to their iPod / PCs / HTPCs / media centers are thieves. This is too braindead to even be good flamebait.
Live today, because you never know what tomorrow brings
on behalf of all of us geeks,
Thanks!
At least when egos get in the way of OSS, the community can muddle along with the source code. When the same thing happens to closed source software, what are we left with?
I went to the city because I wished to live without deliberation.
Yeah, we all know that egotism would never play a part in any closed source project or company.
Kindness is the language which the deaf can hear and the blind can see. - Mark Twain
At the end of proprietary software development, the project ends and the free software community has to either do without or start anew from whatever they've got (which is not the proprietary program's source code and a license to run, inspect, share, and modify at any time for any reason). At the end of a free software project, others can pick up where the former free software hackers left off and continue improving the free software. If the license for the program is a copylefted free software license, the improved software continues to be free.
Let's hope source code for freedb2.org and database dumps from freedb2.org are shared under a free software license so that if freedb2.org dies we're not left with nothing but an increasingly out-of-date freedb.org database and freedb.org software.
Thanks so much for all the work, freedb.org hackers. Your efforts are greatly appreciated.
Digital Citizen
It does, but then money comes along and closes the argument right there, right now.
While I believe that free, open source software is very good and should be used more widely, this is an example of where corporate solutions can prevail.
I've used FreeDB for a while now with the CD ripping program I use (Goldwave, highly recommended), and it had its pros and cons.
On the plus side, I could find listings for more foreign/anime CDs than I could using CDDB (a corporate company, used by the likes of WinAmp and WMP, I believe).
On the minus side, there were a few moderately popular to very popular CDs that had no listing. Also, more than a few CDs (including the foreign CDs mentioned) had more than one listing, each with small differences (some with large differences, such as translated song titles, or even just misspelled words), so you had to go through each one to find one that suited you. (One might argue that the choice was good, but in this case it was just annoying.)
The reason that FreeDB stopped is because those in the lead couldn't come to a decision. This would almost never happen in a corporate environment. Any dispute would go up the chain until it hit the CEO or board of directors, where a firm decision one way or another would be made. In the mean time, the product would merely remain unchanged (unless company policy specifies otherwise), so there would be no interruption in service.
Had FreeDB used a similar hierarchy (which they may have had, but it just fell apart), this might have been avoided. The programmers/engineers would dispute something, and the project lead/lead engineer would hear both sides and say "This is this, and that's that."
Certainly, this will be an inconvenience to those who use programs that use FreeDB, but have no idea that the program does.
Thanks a lot for that! Also, freedb is still accepting lookup requests, at least for now. I guess things aren't that bad. It's just weird to see a project that I thought was stable end so suddenly.
Also, more than a few CDs (including the foreign CDs mentioned) had more than one listing, each with small differences (some with large differences, such as translated song titles, or even just misspelled words), so you had to go through each one to find one that suited you.(One might argue that the choice was good, but in this case it was just annoying.)
Is offering a choice of original and translated titles more or less annoying than if they had standardised on the language you like less? Do multiple language and subtitle tracks on DVDs annoy you too?
US Democracy:The best person for the job (among These pre-selected choices...)
Document, as in release the code, as in free, as in freedb?
Ah. Thought not. Please take your advertising elsewhere, then.
--
*Art
And I've heard criminals can use pencils to stab people. What does your law breaking have to do with freedb?
Maybe not
In the world of litigation we live in, it's all or nothing. Keeping even a single bit to your chest gives you the munitions to go after others, and prevents them from legally creating a derivative.
That you're going to release it to the public "Real Soon Now" just doesn't cut it -- it either is or it isn't, and those of us who remember GIF, RSA, JPEG and others will treat this as "isn't". This isn't paranoia -- it's experience.
--
*Art
Better organization sounds like a good idea, but perhaps it could be done with less work for the editors. I believe those pages already have standard templates that are used, so couldn't you just make the templates special? I mean, provide a way for a template variable to be treated as metadata for a page, so if you have a song template and an artist variable, a search could be done for songs by that artist. It would not make sense to give this treatment to the vast majority of template arguments, so there would have to be special way to mark them. Then again, you could also just use categories and include variable categories in the template (ex. <includeonly>[[Category:Songs by {{{artist}}}]]</includeonly>). A recursive category display could show a similar listing to the IMDB listing. Ex. Actor has subcategories TV shows with Actor and Movies with Actor, the Actor category could be made to show the contents of its subcategories. The again, that would still appear not as "smart" as the IMDB system which knows to list by year in that instance and alphabetically/by relavance in searches (and include "also known as" titles in searches).
I agree that Wikipedia has trouble dealing with locations. It is a hard problem in part because that pretty much requires graphics to work well.
Centralization breaks the internet.
I don't buy the all or nothing thing. If he releases the code in the next several weeks, and as he says, he's adding documentation, cleaning it up. etc., where is the problem? If he just dumped the code, there are likely to be just as many complaints.
If I take some GPL code, I can make any changes I want to it and no one can force me to distribute the source. (As long as I do not attempt to distribute/sell the binaries, of course). If Andrew (or whatever his name is) hasn't attempted to distribute binaries that contain GPL code (and I'm not sure we know that he has for a fact), then we need to back the fuck up.
It's not offtopic, dumbass. It's orthogonal.
And who deals with the copyright issues for the artwork?
Yeah, we all know that egotism would never play a part in any closed source project or company. Why is it every time someone points to a flaw in any OSS, someone immediately jumps in to say how no matter what the flaw is, OSS is still better than closed-source software? The point is OSS isn't flawless. "Hey OSS community! You've got this problem! Why don't you fix it?" is how I always interpret them, but the modded-up responses never seem to reflect my interpretation; it's always "Oh yeah? Well Microsoft does the same thing, but worse, and they also do this other horrible thing!"
The fact that he has promised to release the source "the next couple of weeks" for the last 2 years?
I think the point being made was that in a world where someone can be sued and forced to remove software from distribution - either from legal rulings or the threat of litigation forcing a chioce of financial priorities - saying that the source will be released "real soon now" may mean it's never released at all. Obviously, releasing well-formated source code with documentation is better than releasing poorly formated code with no documentation, but both are better than releasing nothing at all.
I mention DVD Decrypter in the subject of the post because it's a well-known (if you're into that kind of thing) DVD ripping software that was taken down from a number of (US-hosted) sites after threat of litigation and, since it was closed-source, no further developement was made. Now, I'm not trying to compare FreeDB to DVD Decrypter, either in terms of legality or morality. Just using DVD Decrypter as an example of software which, had it been open source, could still be under developement but because the source code wasn't being released is now "lost forver." (Of course, in actually, it's not that hard to find a download of the final released version of DVD Decrypter, but it would have been nice if the code was out there for other people to continue improving.)
Again, I'm not trying to compare FreeDB to DVD Decrypter. Just providing an example for the parent's point that you never know how some court ruling or sue-happy lawfirm is going to affect what's out there. I'm not even trying to say FreeDB *should* post every line of code currently written - I can understand why the author wouldn't want that. At the same time, I can understand why the GP has an attitude of "all-or-nothing" in terms of calling something 'open source.'
-Trillian
In the meantime, I invite you to enjoy http://freedb2.org/ and browse as much of the source code as I have had time to document
The GPL does not allow you to wait until the code is polished and documented to distribute it. If there are users, they must have access to the code, in whatever state it's in. Post a tarball now, and post a revision when you're done documenting it. Anything else is criminal.
Give me Classic Slashdot or give me death!