Slashdot Mirror


Open Source Music Fingerprinter Gets Patent Nastygram

Nushio writes "The code wasn't even released, and yet Roy van Rijn, a Music & Free Software enthusiast received a C&D from Landmark Digital Services, owners of Shazam, a music service that allows you to find a song, by listening to a part of it. And if that wasn't enough, they want him to take down his blog post (Google Cache) explaining how he did it because it 'may be viewed internationally. As a result, [it] may contribute to someone infringing our patents in any part of the world.'" Update: 07/09 00:31 GMT by T :Story updated to reflect that Shazam is multiplatform, not Android-only, as implied by the original phrasing.

60 of 487 comments (clear)

  1. android hate by Anonymous Coward · · Score: 4, Informative

    it was an iphone app long before it was an android app

    1. Re:android hate by Nushio · · Score: 5, Informative

      And there's a Windows Mobile, Nokia / Symbian, Blackberry app too. It's my fault for not Googling them up before hand..

      --
      Check out Unsealed: Whispers of Wisdom! http://unsealed.k3rnel.net It's an action-RPG about Open Sourcerers.
    2. Re:android hate by Nushio · · Score: 4, Insightful

      Yes, I am. As a non-native english writer, who has difficulties dealing with grammar nazism, I find commas useful to explain stuff. =P

      --
      Check out Unsealed: Whispers of Wisdom! http://unsealed.k3rnel.net It's an action-RPG about Open Sourcerers.
    3. Re:android hate by nitehawk214 · · Score: 3, Funny

      Commas, will be misplaced.

      --
      I'm a good cook. I'm a fantastic eater. - Steven Brust
    4. Re:android hate by nmb3000 · · Score: 5, Insightful

      it was an iphone app long before it was an android app

      What does it matter that it was on the iPhone before Android? It's hardly surprising, considering the iPhone was released years before the Droid. I admit there hasn't been the usual heavy complement of Apple stories today, but that doesn't mean you have to start looking for ways to create them from unrelated articles. In any case, this has almost nothing to do with any platform, except that the author wrote the code in Java so as to run it on Android.

      Back on-topic, the author has posted an update which talks about the alleged patent infringment and includes the notices sent by the company. Classically, they hesitate to give actual patent numbers, but what it really comes down to is this: As the author says,

      I've written some code (100% my own) and implemented my own methods for matching music. [...] I'm just a programmer who likes to work on technical, mathematical algorithms in his spare time. And if enough people ask for the source code, I'd be happy to give it to them. Who would have thought that creating something at home in a weekend could result in a possible patent infringement!?

      But oh, no! Landmark claims

      Landmark Digital Services owns the patents that cover the algorithm used as the basis for your recently posted "Creating Shazam In Java".

      Well butter my biscuit and call me Daisy! Case closed! After all, they have a patent on "the algorithm". To be fair, the biggest instigator of this entire fiasco is probably his choice of using the commercial software's name in the article title. Going just by "Creating Shazam In Java", you might at first think he's attempting to completely re-create the software (for who knows what purpose). Of course, if you bother to read even the first few paragraphs it painfully clear that it's nothing of the sort. But because of this,

      The code isn't published yet, but I was planning on releasing it under Apache License to the open source community soon. [...] Since I don't want to end up like Dmitry Sklyarov, with the possibility of a lawsuit, I'm not going to publish the code anymore...

      If crap like this continues, independent software development in general (including a large chunk of FOSS) is doomed.

      --
      "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
      /)
    5. Re:android hate by commodore64_love · · Score: 4, Interesting

      >>>As a non-native english writer, who has difficulties dealing with grammar nazism, I find commas useful to explain stuff.

      Let me help - "The code wasn't even released, and yet Roy van Rijn, a Music & Free Software enthusiast[,] received a C&D from Landmark Digital Services, owners of Shazam, a music service that allows you to find a song [] by listening to a part of it. And if that wasn't enough, they want him to take down his blog post explaining how he did it[,] because it 'may be viewed internationally. As a result, it may contribute to someone infringing our patents in any part of the world.'"

      Fixed that for you. [] are deletions/additions. Basically I only found three errors. Grammarwise I'd recommend fewer interruptions. Simplify; simplify. As for the cease-and-desist I'd respond like so:

      Dear Landmark:

      Go watch Penn & Teller's "Bullshit". The title of that show is what I think of your shitty letter you litigious motherfuckers. I live in ____ where you do not hold a patent, so you can go shove a dildo up you anus. My post is protected my this country's right of free speech and free press.

      Respectfully,
      Not Your Slave Nor Your Serf
      (middle finger)

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    6. Re:android hate by GigaplexNZ · · Score: 4, Insightful

      Yeah and you're supposed to put a comma in front of conjunctive words like "and, or, but, because" especially if they join two sentences.
      <snip>
      I rocked my English SATs (99th percentile) so I'm fairly certain I'm right.

      Shouldn't you have put a comma before "so" if you are going by that rule?

      - I rocked my English SATs (99th percentile). I'm fairly certain I'm right.
      - I rocked my English SATs (99th percentile), so I'm fairly certain I'm right.

    7. Re:android hate by c0lo · · Score: 4, Insightful

      independent software development in general (including a large chunk of FOSS) is doomed.

      Only in countries silly enough to allow software patents...

      And the ones stupid enough to accept the crap ACTA will feed on their throat... actually, for those will be even worse: no allowing their software developers to patent but preventing them to use methods already patented in US.

      --
      Questions raise, answers kill. Raise questions to stay alive.
    8. Re:android hate by chaboud · · Score: 3, Insightful

      That is such a beautiful example of Muphry's law.

      Though your post could have benefitted from a gaffe or two.

  2. Patent and disclosure... by nebaz · · Score: 5, Interesting

    IA (definitely) NAL, but I thought the whole purpose of patents (other than protection) was to disclose the invention in full (not behind trade secrets) in exchange for knowledge of how the invention is done/made. Have the patent owners given any implementation details about their application?

    --
    Rhymes that keep their secrets will unfold behind the clouds.There upon the rainbow is the answer to a neverending story
    1. Re:Patent and disclosure... by MadCow42 · · Score: 5, Insightful

      Yep - I bet he's hit on a Trade Secret of theirs in his blog post and/or development work, and they're just trying to scare him away from posting the details. Trade Secrets are only secrets as long as nobody else knows about them - there's no protection on them other than that.

      The patent holds NO ability to stop him from disclosing ANYTHING - anything covered by the patent is by definition publicly disclosed in the patent itself. If it's not there, it's not covered. Period. The "international viewing" holds no water either - there's nothing preventing someone from viewing the patent from another country.

      He can go tell them to fuck off. He can probably sue for SLAPP or something like that too. I would!

      In addition, my understanding is that this goes even further - there's nothing preventing him from developing his own implementation of their patent. The only issue arises when he distributes it beyond himself. IANAL, so this part I'm only 99.9% sure on. :)

      MadCow.

      --
      I used to have a sig, but I set it free and it never came back.
    2. Re:Patent and disclosure... by Daniel+Dvorkin · · Score: 4, Informative

      Bizarrely, the USPTO doesn't require code for software patents; I assume other patent offices worldwide, in those countries which allow software patents, follow the same practice. You can't patent a mechanical device without schematics (I think) but for software, a vague description of the algorithm -- too vague to be of any use in implementation -- is enough. This is yet another example of why the idea of patenting things that aren't physical objects is fundamentally broken, but don't expect the situation to change any time soon.

      --
      The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    3. Re:Patent and disclosure... by Wonko+the+Sane · · Score: 4, Insightful

      At least in the US you have absolutely no recourse against someone who independently (not an employee, etc) develops one of your trade secrets. They can even patent it themselves and force you to pay a license fee!

      That's the trade off between patents and trade secrets.

    4. Re:Patent and disclosure... by Nushio · · Score: 5, Insightful

      His implementation was different than their's, and if that's the case, they've got bigger issues, as one of their developers wrote a PDF on how Shazam Works..

      And this guy certainly wasn't the first to write an article about How Shazam Works either.

      They're afraid of the code.

      --
      Check out Unsealed: Whispers of Wisdom! http://unsealed.k3rnel.net It's an action-RPG about Open Sourcerers.
    5. Re:Patent and disclosure... by Grishnakh · · Score: 3, Informative

      Exactly. If it were copyrighted, it'd be different, but if his work falls under a patent, there's nothing they can do as long as he doesn't offer his software for sale or in any products, or make it available as a binary. It's just like LAME, and various open-source decoders for patented codecs. The source code can be distributed freely, it's only when someone uses it that the patent holders have to be paid. The patent holders can only sue people who use the final product, and of course that's pretty difficult to figure out since anyone can download the source code and compile it.

      The situation is more murky for anyone who distributes compiled binaries, though, which is why most US-based Linux distros don't include LAME or any MP3 decoders, but usually provide convenient ways for you to download these things and install them with one or two clicks.

      Fuck 'em.

    6. Re:Patent and disclosure... by Grond · · Score: 3, Informative

      In addition, my understanding is that this goes even further - there's nothing preventing him from developing his own implementation of their patent. The only issue arises when he distributes it beyond himself. IANAL, so this part I'm only 99.9% sure on. :)

      I'm afraid you're wrong here. In the US, a patent gives the patentee the right to exclude others from making, using, selling, offering to sell, or importing the claimed invention. 35 USC 271. Now, of course, the patentee must actually sue for patent infringement, and that's unlikely in the case of garage tinkerers (those that don't post everything online, that is), but there is no exception to patent infringement for 'developing your own implementation.' There is a research exemption related to preparing data that will be presented to the FDA, but that's not relevant here.

    7. Re:Patent and disclosure... by ascari · · Score: 3, Informative

      As far as Trade Secret goes: Shazam's own Avery Wang published the ins and outs of the Shazam algorithm in Proceedings of the ACM back in 2006. The paper also mentions similar systems by Phillips and others that go back to 2001 and beyond. There's also a reference to a talk by Shazam's Avery Wang at an international conference in Baltimore in 2003. They've plastered their secret sauce for all the world to see for years, and now they fuck with this poor guy!

      Ironically, the example in the ACM article was the Beatles song "Let it be". That's precisely what I would suggest Shazam does.

    8. Re:Patent and disclosure... by thesolo · · Score: 3, Interesting

      Weirdly, Shazam have published a fairly thorough paper on how their search algorithm works. While devoid of any actual code, it doesn't seem as though the blog in question has given away any trade secrets that aren't easily derived from this paper and other bodies of work online.

      Of course, by threatening the guy Shazam & LDS have created their very own Streisand Effect; this is front page on /., Digg, Reddit, YCombinator, etc., which means millions of people have now seen the "infringing" code, with many saving it or tweaking it. I'm certain someone will mirror it in a country that doesn't validate software patents as well. One also wonders if they're going to sue Google or demand they clear the cache.

      As for me, I won't be using their software, and I will be contacting them to register my disgust, though it probably will make no difference in their attitude.

    9. Re:Patent and disclosure... by kanto · · Score: 5, Insightful

      The whole point of software patent wording has become to ensure maximum ambiguity; the more ground you cover the less there is room for your competition to lay it's own claims or to avoid patent extortion. Who you gonna call when an industry monster sends it's goons around? Probably some nonprofit organization that'll tell you to cave cause it might get rough out there.

    10. Re:Patent and disclosure... by radtea · · Score: 3, Interesting

      If I patent a gizmo, and you make your own, it doesn't matter if you distributed it, you are liable for patent infringement.

      But a software patent is nothing but a description of an algorithm. Full disclosure: the reason I know this is because I am a co-inventor on a software patent (I was evil once, but I got better.)

      So apparently the First Rule of Software Patents is you do not talk about software patents, because by doing so you are actually in violation of the patent.

      And don't kid yourself: code is how developers communicate with each other, and the distinction between pseudo-code and the real thing is utterly moot these days. Most of us write in sufficiently high level languages that our pseudo-code is indistinguishable from Python. So whenver a couple of developers talk about a patented algorithm they are almost certain to be violating the patent.

      --
      Blasphemy is a human right. Blasphemophobia kills.
  3. What the? by Barrinmw · · Score: 3, Insightful

    Patents are open for viewing aren't they (with the exception of the NSA)? So if they have a patent for something, then how can they order someone to take down information that a supposed patent covers?

    1. Re:What the? by h4rr4r · · Score: 3, Interesting

      Even then, code is speech until you run it. Are we now to limit free speech by government order to protect their patents?

      If the hardware store sells me a CNC mill and I make patented widgets with it will they sue the hardware store?

    2. Re:What the? by NNKK · · Score: 4, Insightful

      By that logic you could freely distribute an infringing program as long as you don't run it.

      Yes, exactly. In the same way that a description or schematic of a patented invention does not infringe a patent, simple source code does not infringe a patent. How is this difficult to understand?

    3. Re:What the? by russotto · · Score: 3, Insightful

      Yes, exactly. In the same way that a description or schematic of a patented invention does not infringe a patent, simple source code does not infringe a patent. How is this difficult to understand?

      This case outlines one of the many major problems with software patents, one being that a split between implementation and description does not exist. The source code -- or even the object code -- to a program implementing a patented method is a description of that method.

  4. What's that song? by UndyingShadow · · Score: 5, Funny

    Is that a Barbra Streisand song I hear?

    1. Re:What's that song? by bit9 · · Score: 5, Funny

      Indeed. I've found that one of the best ways to discover cool new open source projects is to go to Slashdot and search for "C&D".

  5. Re:Shazam... by Anonymous Coward · · Score: 5, Funny

    Because iPhones suck.

  6. Re:Shazam... by Nushio · · Score: 5, Informative

    Because I didn't Google it up properly. And Slashdot doesn't let me edit the story submission after I hit send. Its my fault.

    --
    Check out Unsealed: Whispers of Wisdom! http://unsealed.k3rnel.net It's an action-RPG about Open Sourcerers.
  7. I call bullshit. by seeker_1us · · Score: 5, Insightful
    One: you cannot patent code. Period. There's plenty of cases where people have written (and released) code that some patent covered (ffmpeg anyone). The code itself is free speech.

    Two: you cannot use a patent as a method to censor free speech.

    Three: any US patent can be viewed internationally. A patent is by definition NOT a trade secret. Even if this guy's software DID use a patent-encumbered algorithm, his post cannot "contribute to someone infringing ... patents in any part of the world."

    Four: a patent is not valid for the entire world.

    1. Re:I call bullshit. by Theaetetus · · Score: 3, Informative

      One: you cannot patent code. Period. There's plenty of cases where people have written (and released) code that some patent covered (ffmpeg anyone). The code itself is free speech.

      They didn't patent code. They patented the method and system. And you can certainly patent those. In fact, the fact that it's not the code, but the method, that's patented is why he was infringing even though he did it in Java and they did it in C#. Patents are not copyright.

      Two: you cannot use a patent as a method to censor free speech.

      Nope, but you can use a patent to prevent someone from using your invention without your consent.

      Three: any US patent can be viewed internationally. A patent is by definition NOT a trade secret. Even if this guy's software DID use a patent-encumbered algorithm, his post cannot "contribute to someone infringing ... patents in any part of the world."

      Yes, because if someone takes his code and runs it, then they're infringing. Therefore, he's contributing to the infringement.

      Four: a patent is not valid for the entire world.

      Nope, but his post is viewable by the entire world. And someone could infringe in the US, where the patent is, by using his code.

    2. Re:I call bullshit. by h4rr4r · · Score: 4, Interesting

      The code is speech, compiling and running it is the infringement. Is patent protection now more valued than free speech?

  8. Re:Well, really... by bhlowe · · Score: 3, Interesting

    Why Mr. van Rijn use their proprietary name in his blog post? (Creating Shazam In Java) Of course they are going to respond exactly as they did. And much sooner had he not used it. Seems like this is a no brainer cause for a C&D letter to help protect their investment.

  9. Re:Well, really... by swabeui · · Score: 5, Insightful

    Injustice is always newsworthy.

  10. Re:Shazam... by e4g4 · · Score: 4, Insightful

    A story submitter, on Slashdot, humbly and openly admitting a mistake. My hat is off to you, sir. Here's hoping some of the people responsible for the more absurdly sensationalist summaries (your submission is certainly _not_ one of those, just to be clear) that creep onto the front page take your precedent as an example. I won't be holding my breath, though.

    --
    The secret to creativity is knowing how to hide your sources. - Albert Einstein
  11. Re:Well, really... by cgenman · · Score: 5, Informative

    In the US at least a patent application is public record, and is intended to explain to the world how the object functions. This is not just to enforce the patent, but also to reward spreading the knowlege about how a patent works.

    Asking someone to take down a blog post that describes the workings of a patented process is foolish. If the patent is written like it is supposed to be, anyone should be able to understand the patented process. You are no longer protected under trade secrets if you patent (which is why some choose not to). It is by definition at that point public knowledge.

    Whether or not they have a patent case against him, they have no case against his blog.

  12. Use pHash by b1ng0 · · Score: 4, Interesting

    Use pHash instead, my open source perceptual hashing library that can detect similar audio, video, images and text files. It does not use Shazam's patented algorithm, which isn't all that great anyhow.

  13. Re:Well, really... by IgnitusBoyone · · Score: 4, Insightful

    Well patents are pretty damn public knowledge, so I don't see how an open-source project that does the same thing can be infringing on a patent. Now, the people who use the source code might infringe on it, but drawing a schematic of a door latch doesn't infringe on the door latch, but building one does. It might not work this way at all, but the above is why I think its fairly unfair to ask someone to remove a post about how to do it.

    --
    Momento Mori
  14. They're actually being fairly reasonable by Rogerborg · · Score: 3, Funny

    I mean, on the spectrum of software patent insanity, they're being relatively restrained and civil. They seem genuinely to be trying to head off competition for an invention that they are implementing and selling - which is the point of patents - rather than acting like patent trolls and trying to gouge money for something that they never implemented.

    Of course, it sucks, software patents doubleplus bad, Fight The Man, counter sue them for a hundred beelyon Euros, Attica! Attica! Attica! and so on, but comparing a couple of polite "please don't make us do anything you'd regret" emails to Adobe's assraping of Dmitry Sklyarov is rather hyperbolic. And yes, I have a "Free Dmitry Sklyarov" t-shirt, thanks for asking.

    --
    If you were blocking sigs, you wouldn't have to read this.
  15. Re:Well, really... by Anonymous Coward · · Score: 5, Insightful

    What is far more scary is that using a sliding window to calculate DFTs and then hashing these values, and storing there offsets is somehow patented. To say that this is "obvious" to someone with any understanding of waves and Fourier transforms is an understatement.

  16. Re:Well, really... by RichardJenkins · · Score: 5, Interesting

    BoingBoing has a good write up (http://www.boingboing.net/2010/07/08/patent-holders-legal.html). Most interesting was the fact that Landmark Digital Services took exception to the technical details of a patent being discussed. I think most people (myself included!) believe that reading a patent should tell you precisely how to replicate something, but there's a subtext to this story implying that is not the case here. I think a situation where a patent holder treats someone discussing a means to replicate patented technology as though they where handing out trade secrets is pretty interesting, certainly ./ worthy.

  17. Re:Well, really... by FlyMysticalDJ · · Score: 4, Interesting

    He's not employed by them is he? Because if he's not, I don't think their trade secrets mean squat to him. If I mess around and discover coke's trade secret recipe, they're not going to come knocking on my door. And they wouldn't have any legal precedent to do so in the first place. If you discover someone else's trade secret, it's fair game. You can even sell a product using that trade secret as long as you didn't work for them and take it, or buy it from someone who did.

  18. Re:Well, really... by Anonymous Coward · · Score: 5, Insightful

    "What is far more scary..."

    Yes. As others said, unjustice must always be news, no matter how (sadly) common it becomes.

    1) It's an obvious application of a Fourier transform so it shouldn't have been accepted for patent on first place.
    2) Even if it wasn't obvious, this guy did not have access to the original code so chances are by big margin that this a different method to achive the same result so even after the patent is granted is very dificult to believe he could violate it.
    3) Even if it wasn't obvious and it was the very same patented method, patents are, well, patent, so it's ludicrous to say "you shouldn't make public this" when the very patent system is built around the fact that the patented method is meant to be made public.

    All in all this is a news about a disfunctional and criminally stupid patent system abused by a disfunctional and criminally stupid company.

    Yes: this needs to be aired.

  19. Re:Well, really... by Blackbrain · · Score: 4, Insightful

    Don't get me wrong, this really sucks for the guy and is completely unfair. But this sort of thing happens all the time. If this were a rare occurrence, then yeah, I'd be up in arms. It's sort of not newsworthy anymore.

    The only reason that these things happen is that every time these things happen everybody looks around and says "Well, these things happen..." and THAT'S why they happen!

    If you see something, say something...peace out.

    --
    Where would we be if Wheel had hid her round rock in a cave instead of showing everyone how it rolls?
  20. Re:Well, really... by ClickOnThis · · Score: 3, Interesting

    > Why Mr. van Rijn use their proprietary name in his blog post?

    Because it damn well pleases him to do so, and in the USA, at least, he is free to do so with impunity as long as he does not use it in a way that might mislead the public into believing that they are getting said product when they are not. A trademark is not a copyright.

    [Emphasis mine.]

    Look, I'm on van Rijn's side. However, I can appreciate that a blog post entitled Creating Shazam in Java could "mislead the public" even though it might not mislead the technically savvy. If I wrote a blog post entitled Creating Microsoft Office in Java you'd better believe I'd get a message from the folks in Redmond.

    IMHO, if Landmark has any beef here at all, it's that their trademark is threatened, and feebly at that.

    --
    If it weren't for deadlines, nothing would be late.
  21. The code was released in the original blog post by Anonymous Coward · · Score: 4, Informative

    I RTFA, and he posts pretty much the entire source code of his implementation in the original blog post. That is what they were upset about: implementing the patent *and* distributing it. Had he merely discussed the methods Shazam used, it probably wouldn't have been a problem. However, I can go to his blog, cut-and-paste the code into a text editor, and have a working clone of Shazam. That is fairly cut-and-dry patent infringement, minus commercial gain and sidestepping the issue of software patents.

    It's not like he was just talking about the process.

    1. Re:The code was released in the original blog post by DavidTC · · Score: 3, Interesting

      Generally, the courts have held that source code is akin to a 'diagram', not the device itself.

      It's perfectly legal to distribute diagrams of devices that implement patented methods. The patent holder can demand you make a note that it uses such a method, and is illegal to operate without a license, but can't actually stop you from distributing the diagrams.

      Yes, it's weird a normal person can spend five minutes turning a diagram into a device.

      OTOH, plenty of patents use already existing devices in novel ways, like 'entertain a cat with a laser pointer', which, now that I've described it, a good fraction of the people out there can implement with even less work then compiling. That's a silly, but real example, but there are real, serious patents on the use of medicines, for example, in novel ways, or adding tiny impurities to a well known process to make it better. Those are just as easy to implement.

      Describing ways for people to make devices that implement patented methods, no matter how simple it is to turn it from 'diagram' to 'device', is legal. And source code has consistently been held to be 'diagram'.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  22. Re:Why take down his blog? by Qzukk · · Score: 5, Informative

    they have to defend their patent or risk losing it.

    That's trademarks.

    --
    If I have been able to see further than others, it is because I bought a pair of binoculars.
  23. Posible prior art by Anonymous Coward · · Score: 5, Interesting

    The name of this proyect that seems to be prior art is Tararira (music retrival by sung query). It's from Uruguay, and does recognition of music just humming at a microphone. Proyect was created in 2004 and have code published.

    http://iie.fing.edu.uy/investigacion/grupos/gmm/proyectos/tararira/ingles.php3
    http://iie.fing.edu.uy/investigacion/grupos/gmm/proyectos/tararira/descargas/tarariraEN-src-0.1.tar.gz
    http://iie.fing.edu.uy/investigacion/grupos/gmm/proyectos/tararira/descargas/tarariraEN.tar.gz
    http://iie.fing.edu.uy/investigacion/grupos/gmm/proyectos/tararira/descargas/tararira.pdf

    Tararira is a query by singing system. The problem of music retrieval by sung query (QBH, query by humming) consist of building a machine capable of simulating the cognitive process of identifying a musical piece from a few sung notes of its melody.

    A melody is described by a sequence of notes, so it is natural to compare melodies by means of the similarity of their constituent notes. For this reason, the problem can be divided in two stages: the transcription of the voice signal into a sequence of notes and the search of this pattern in a MIDI melody database.

    Tararira originates in July 2004 as the graduation project of Ernesto López, Martín Rocamora and Gonzalo Sosa at the IIE of the Facultad de Ingeniería, Universidad de la República.

  24. Re:Why take down his blog? by nameer · · Score: 3, Insightful

    Patents are selectably enforceable. I can choose to never sue you for infringing. What laches is supposed to prevent is me waiting until you are very profitable before suing you. However, even if I choose to never sue you, I can still sue Joe once I find out he is infringing.

    --
    "Uh... yeah, Brain, but where are we going to find rubber pants our size?" --Pinky
  25. Re:Well, really... by Altrag · · Score: 4, Informative

    Don't even have to RTFA, or even the summary.. Just the tagline says specifically that its a patent claim. Whether or not the claim would actually stand up in court is up to a judge should it get that far (never mind international concerns), but everything I've seen so far tells me that Shazam has all the right in the world to at least make the claim.

    As far as I know, neither "easy after someone else has thought of it" nor "it didn't take me very long" are terribly good defenses in a patent case. The one you're looking for is "figured it out before someone else has thought of it", which this guy obviously didn't do given that he specifically set out to duplicate the abilities of an existing product. At this point his only defense is to show that his algorithm is sufficiently improved over (or at least different from) Shazam's that it would warrant being called 'innovative' (at least in the US.. I don't know about the EU's rules). Also, being his own code isn't a defense in a patent case (whereas it would be a defense in a copyright case if it could be proven).

  26. Re:I think someone fails to comprehend... by DavidTC · · Score: 3, Informative

    but profiting from the idea is patent infringement

    No it is not. At all. There is absolutely no manner in what you just said is true. If I, as an example of 'making money off a patent', pick a patent and charge people money to have me explain exactly how the patented process works, step by step, and sell them photocopies of the patent, it's entirely legal.

    In fact, industry engineering books, books telling you how to, for example, design a printing press, will often do just that. They'll explain all the processes to do something, including patented ones, and then will tell you 'this is covered by patent #num until this date, so contact Blah Blah Inc to get a license if you want to do it that way.'.

    Patents are public information. It is entirely legal to get paid to do anything with that information. Anything.

    The only thing that is patent infringement is a) using the methods described in patents, or b) building a device that uses those methods and giving it to other people for them to use. (And using the device yourself is, duh, (a). Technically, you can build a device, keep it, and never use it, though.)

    Anything else WRT to the patent is legal. Like I said, you can even make copies and sell them, as patent descriptions can't be copyrighted.

    The question is whether or not this source code is a device, which makes it illegal to give away, or if it's more akin to a diagram of that device, which is entirely legal to give away. Sadly for Shazam, the courts have always sided with the 'diagram' analogy of source code.

    --
    If corporations are people, aren't stockholders guilty of slavery?
  27. Re:Well, really... by PopeRatzo · · Score: 5, Insightful

    everything I've seen so far tells me that Shazam has all the right in the world to at least make the claim.

    The claim being that in software, once you do something, nobody else can do anything similar, even if it doesn't use any of their code or procedures. If the end result is the same, then whoever the most money to spend on legal fees is the winner. It's a fucked up way to run a railroad.

    So, once someone made a word processor, nobody else should be able to make a word processor. And once somebody made a program that can play music files, nobody else should be able to write a program that can play music files.

    "Innovative" has become such a cheap word. It really doesn't mean anything any more. When a word like "innovative" becomes a legal term of art, innovation ceases.

    --
    You are welcome on my lawn.
  28. Re:Well, really... by jmorris42 · · Score: 5, Interesting

    > I think a situation where a patent holder treats someone discussing a means to replicate patented
    > technology as though they where handing out trade secrets is pretty interesting, certainly ./ worthy.

    In a sane world making such an admission in a legal filing would be grounds for voiding the patent since patent law requires dislosure of everything a person skilled in that field would need to know to implement the patented tech. The idea of patents is to trade full disclosure for a limited monopoly on commercial exploitation of the idea. However as soon as a patent is filed others may begin using your patented tech as a base to build their own innovations on. Of course they will need to license your original tech to sell theirs and you will have to license theirs if you want to incorporate it, etc. Of this are vast portfolios built of cross licensed codependent patents.

    But we live in bizarro world. Sucks don't it.

    --
    Democrat delenda est
  29. Re:Well, really... by PopeRatzo · · Score: 4, Insightful

    before unscrupulous scum litigated our society from one built on morality into one built on greed.

    Not just any scum, but unscrupulous corporate scum, which means that it's not even a person making the decision, but legally fictive golem that exists only to reward those that have bought shares, even at the expense of society as a whole. If it was a person, at least a case could be made for going up to him and calling him a piece of shit who should be ashamed of himself, to tell his neighbors that he's a piece of shit, and to remind his wife and kids that they're related to a piece of shit.

    But what is a "Shazam"? It has no neighbors, no family, no community, no responsibility to do anything but eat and shit money in the pockets of its shareholders. It doesn't respond to shame, to peer pressure, to moral outrage. It doesn't even respond to the "marketplace" because they assert another legal fiction (patent) in order to pervert the marketplace, to ensure that it is immune to market forces.

    And that is ultimately what this "Intellectual Property" baloney is all about: making sure that the marketplace can not work.

    --
    You are welcome on my lawn.
  30. Did anyone happen to look up *who* LDS is? by bferrell · · Score: 5, Interesting

    It's a wholly owned subsidary of BMI... As in BMI/ASCAP?

    It's the record companies again.

  31. Now hold on there by Anonymous Coward · · Score: 3, Insightful

    Do you understand the basic concept of a patent? To earn the monopoly you have to publish your idea. The idea becomes part of the public domain. If someone else republishes your idea the the system works as intended. A patent is not a copyright. This sounds to me like the patent holder really doesn't want to honor the bargain he agreed to. The monopoly is on implementation. We can publish code examples to our hearts content as long as we don't run them.

  32. Re:Well, really... by TheSpoom · · Score: 3, Interesting
    --
    It's better to vote for what you want and not get it than to vote for what you don't want and get it.
    - E. Debs
  33. Similarity application by electrostatic · · Score: 5, Informative
    There's a free app that recognizes similar content in MP3 and other audio files.

    Similarity is a useful program that helps you to find and remove similar, duplicate musical files (MP3, WMA, OGG, WAV, FLAC, APE, WV, MPC) with the same or similar sound content, music tags (ID3,WMF,Vorbis). This is the best program where similarity of a sound part is checked, not just music tags or file content (byte to byte comparision). In addition the program analyzes the artist, title, album information from the music tags contained in the audio files and compare these with the appropriate entries in other files.

    You can adjust sensivity of searching criteria to find exact or similar files. In this way it is possible to identify similarly titles with smaller differences. Duplicate files can be deleted or browsed. The list of duplicate files can be sorted, exported to playlist, and acted upon.

    More at http://www.music-similarity.com/ I wonder if it uses the purported patented technology.

    BTW, the assertion of a potential harm being caused by "...explaining how he did it because it 'may be viewed internationally. As a result, [it] may contribute to someone infringing our patents in any part of the world'" is certified bullshit.

    All patents are public documents -- they must be public in order to inform the world just exactly what it is that the patent owner actually owns. It's detailed in the Claims section. "If you don't claim it, you don't own it."

    Furthermore, a patent must "teach the invention," meaning that anyone "familiar with the art" shall be able to implement the invention with only the descriptions provided. If there actually is a patent for this technology, the cat is out of the bag.

    Patent courts in the US are very favorably disposed to inventors -- assuming the technology is actually protected. It sounds like maybe not, and so the bluster and shrill threats.

    1. Re:Similarity application by Chowderbags · · Score: 3, Informative

      You must be talking about a reasonable patent system. Here in the US we don't bother with human readable patents or silly things like being limited to things you can actually explain. It's enough to say "and any similar techniques" and your patent goes to a narrow definition of a subset of an obscure problem to suddenly encompassing damn near everything even remotely related to it. Half the time you can just state the problem itself and that's good enough. No need to actually solve anything, as if anyone would want to get their hands dirty to actually invent anything anymore.

  34. Re:Well, really... by Mindcontrolled · · Score: 3, Informative

    Unfortunately, you are dead wrong. Patents are strictly territorial and are only enforceable in the country where they are issued. If a US patent holder wants protection in, say, France, he has to file for a French patent in addition to the US one - a process which is simplified by the Patent Cooperation Treaty. Until he does that, he has no legal power over anyone producing his protected product in France - unless they import it to the US. In the case of software, you of course can assume that simply by putting it on the internet, he makes it available to the US market and therefor infringes locally.

    --
    Ubi solitudinem faciunt, pacem appellant.