Slashdot Mirror


CDDB Shutting Down Media Jukebox

shaun writes: "According to this thread on the Media Jukebox Talkback site, CDDB is refusing connections from Media Jukebox until the Media Jukebox guys sign an "exclusive agreement" to use CDDB's database. Taking a shared public resource private has destroyed their karma, but what can be done?" Are grip and xmcd next? How do you enforce exclusivity for an open source program? Everyone should use FreeDB instead anyway: It's everything that was once good about cddb, including that little free part that made cddb itself the defacto standard before it got too big for its britches.

14 of 156 comments (clear)

  1. Wasn't CDDB populated by people like us?? by erat · · Score: 4

    All annoyanced with CDDB aside, I question the ethics of taking information submitted by people around the globe and making it closed/proprietary.

    Did Network Solutions buy them when I wasn't looking? This sounds like something they would do...

  2. The other cool thing about FreeDB by Bwah · · Score: 4

    is that the source code and the database contents are available for FTP. This means I can setup a server on my local net to avoid slow disc IDs at work (due to overloaded links) and to avoid having to go online at home. (of course i guess this is only a problem for us poor schmucks who still only have dialup access ... :)

    dv

    --
    "There's no secret. You just press the accelerator to the floor and keep turning left." -- Bill Vukovich
  3. Re:Database Copyright Laws by happystink · · Score: 4
    Wrong. Absolutely wrong. Unless CDDB are threatening to sue anyone for making a similar database, this has nothing to do with copyright whatsoever. They just want to be paid to let mediajukebox use their service. I am saying this is right or wrong, but this has NOTHING to do with copyright.

    I guess anytime anyone does anything that could involve IP in any way whatsoever, Slashdot readers have been conditioned to start crying, shouting "this is evil!" and threaten to start 5 sourceforge projects copying whatever product they are currently angry at, so don't feel bad, it's not your fault for getting this wrong.

    sig:

    --

    sig:
    See the "..for smart people" banners Wired runs here? Look elsewhere guys.

  4. CDDB claims a protected algorithm by Karmageddon · · Score: 5
    Many posters here are talking about having entered songs into the CDDB and they wanted the info shared.

    Just to clarify, CDDB doesn't claim to own the song titles (the record companies do?), they claim to own the encoding that turns the length of all the tracks on a disc (the "uniqueness") into a code number to be looked up in the database. You are free to take the song titles from their database. What they'll try to stop is any use of that algorithm.

    I just thought I'd clarify because it makes a difference to how to circumvent their theft of everyone's hard work. The distributed.net idea would not suffer from this problem, BTW, not to mention it would be fun. SETI@CDDB! :) I'm sure d.net would never go for it, though, they'd rather bore us all to tears with a yet longer attempt to crack some obscure n-bit variant of a public key system. (d.net: we know that things can be cracked by brute [yawn] force. do something more interesting!]

    1. Re:CDDB claims a protected algorithm by rcw-work · · Score: 5
      Just to clarify, CDDB doesn't claim to own the song titles (the record companies do?), they claim to own the encoding that turns the length of all the tracks on a disc (the "uniqueness") into a code number to be looked up in the database. You are free to take the song titles from their database. What they'll try to stop is any use of that algorithm.

      Whether this is true or not, it's pathetic. FreeDB uses the same algorithm.

      Anyway, this is a description of the algorithm just so you can see how stupid it is:

      The discid looks like a 32 bit hex number, but in reality it's not - it's an 8 bit checksum, a 16 bit number representing the total length of the disc in seconds, and an 8 bit number representing the number of tracks on the disc.

      It's mind-warpingly simple. Ignoring MSF offsets for the sake of discussion, this is how it's done:

      Get the length of all the tracks in frames, like so:
      22047 44492 69957 85152 113637 129910 148045 165852 178462 200282 215427
      Divide them all by 75 so you have track lengths in seconds:
      293 593 932 1135 1515 1732 1973 2211 2379 2670 2872
      This is the really really brilliant part - Add all the decimal digits together like so:
      2+9+3+5+9+3+9+3+2+1+1+3+5+1+5+1+5+1+7+3+2+1+9+7+3+ 2+2+1+1+2+3+7+9+2+6+7+0+2+8+7+2
      It's 161 or 0xa1. Convert the length of the disc and number of tracks to hex too (0xc87 and 0xc) and put them together - 0xa10c870c. This is only a little bit off from the real discid (a30c850c), and only because of the MSF offsets I skipped over.

      Read the cd-discid source code for the full algorithm.

      I would be utterly amazed if they could protect this algorithm in court - it's literally just addition.

  5. The erosion continues by Goldberg's+Pants · · Score: 4
    The CDDB is a great concept, but poorly executed. Some of the information is woefully inaccurate, particularly on my obscure CD's. Typos abound in the listings as well.

    An "open source" (for want of a better word) replacement would need to have a verification step. Any data submitted, before being added, should be checked by someone. Maybe have a crew of volunteers (hell, I'd volunteer) who spend a few minutes a day verifiying entries. Maybe have the volunteers list their musical preferences so they would get music they know. With enough volunteers there would be a good chance that 95% of CD's would be already known. Failing that, a simple verification system to check spelling before admission would be good. (Okay, so some songs are spelt wrong deliberately...)

    I hope someone with the resources decides to run with this "open source" idea.

    It's too bad that a boycott wouldn't do anything. The only people with a clue as to what these corporate types are doing make up a real small percentage of the user base. *sigh*

    Mark my words. Google will be next.

    ---

  6. There is the other alternative... by sheldon · · Score: 4

    They could just shut off their servers and go home.

    Bandwidth costs money. The number of applications which support the CDDB concept has increased tremendously since it's initiation. Consider for instance Microsoft's media player which ships with Win98/Win2000 now includes CDDB access.

    We're talking millions of users out there. Do you seriously think someone's home DSL can handle this?

    There is no way that the service could ever be sustained without some sort of commercial venture.

    Although it's certainly a service which the RIAA could take up as a free value-add to the music community. Not sure why they don't do it on their own since they already have access to this information without having to deal with people hand entering it and getting it wrong.

  7. Re:A few things... by Golias · · Score: 4
    It seems to me that what we need is a new boiler-plate agreement for stuff like this... just like the GPL and BSD licenses are set up to easilly protect free software.

    An Open Database Contract would clearly what uses are allowed to the company or individual that maintains it, and protect the rights of those who contribute to it.

    We should perhaps get an FSF lawyer or somebody to help us draft such a document, and then refuse to contribute our efforts to anybody who does not use it (or something very much like it).

    If we don't come up with something like this, future publicly-contributed content will suffer, because nobody will be able to be sure that the product of their labor will not suddenly become unavailable to them.

    --

    Information wants to be anthropomorphized.

  8. CDDB mirror sites by mattdm · · Score: 4
    In the old days, when the original cddb was free, there were a few dozen CDDB mirror sites. A co-worker and I ran one for a few years. When the thing went proprietary, they of course closed down all of the mirrors. They promised to send us a gift in exchange for all of the work we'd done for them (and bandwidth we'd given them), and asked for our address, which we gave (along with a request to reconsider the decision). Never got anything.

    --

  9. Rape the cddb, make it ours again. by billcopc · · Score: 4

    Why not just start a mass backup of the CDDB into FreeDB and pick up where it left us off ? Just query every single possible disc-id and keep it somewhere warm. IANAL, but since this is information that was publicly submitted in the first place, I don't think they can sue anybody for copying what they copied in the first place. Although not every judge has a functional logic module in his/her brain.

    --
    -Billco, Fnarg.com
    1. Re:Rape the cddb, make it ours again. by nickol · · Score: 5

      No need to ' query every single disk-id '. Patch software to use FreeDB as primary source, CDDB as secondary and to COPY contents found in CDDB into FreeDB.
      Then just sit down and listen.

  10. CDDB took others' work and sold it. by alecto · · Score: 4

    CDDB is a perfect example of the disingenuous (but all too common) practice of taking work done (typing in track names) by many in a cooperative effort without permission (the work was given with the understanding that it would continue to be available free without condition), then closing it off for commercial gain. See also Deja (Usenet posts--older archive removed).

    Are there safeguards to prevent FreeDB from doing the same thing some day? Had CDDB been required to pay authors some sum ($1?) for each CD cataloged, they likely would never have dared to choke this stuff off.

    (As an aside, if I had written MediaJukebox, I'd randomize the client identifier or masquerade various "authorized" clients (just like changing the user agent field to avoid sites that discriminate based on browser (or block wget)) Then if cddb (now <puke&gtGracenote&lt/puke>) blocked MediaJukebox they'd have the people who paid (or tagreed to conditions or kowtowed in some way) them upset. Then they could sue, causing more publicity for FreeDB :>)

    BTW, where's the RIAA? Surprised their panties aren't in a knot about lists of album names, titles, and track times being available for download. Or has Gracenote paid them off?

  11. FreeDB needs help by Jamie+Zawinski · · Score: 5

    I agree with others who have said that all this whining about CDDB is pointless, since FreeDB exists, and has a huge amount of data in it already.

    However, FreeDB very much needs help. There are a number of bugs and horrible misfeatures in it, and the main developer seems to have close to zero time to work on it. Pretty much any time I've found a problem, his response has been, ``yeah, too bad I don't have any time.''

    Not that there's anything wrong with that: he's doing a big service to all of us by keeping it running at all. But, if any of you do have the time and ability, it seems to me that FreeDB desperately needs a co-developer.

  12. Interesting quote from freedb.org's site... by grunby · · Score: 5

    From: Freecddb's Why page
    "(Funny sidenote: One programmer told me, that his cd-player will be banned if he is refusing to display the CDDB-logo. His software is a console-based program (it does not produce any graphical output) for blind people...)."