For example, these changes mean you'll no longer be able to control the volume of a group of speakers. Instead, you'll have to change the volume on each individually. It also means you'll no longer be able to use the volume buttons on your phone to control a speaker group. Not here to defend Google, but how can something trivial like that even be patentable?
From my reading of the patent, it's not that the concept of speaker groupings was patented. Rather, a specific UI for showing and modifying the groupings and adjusting the volume. Unfortunately, there aren't many different ways to represent groupings in a UI.
Google doesn't want to pay Sonos for technology it copied
111–120 of 302 posts
Re: Google doesn't want to pay Sonos for technology it copied
#112Earlier quoted context omitted.
What if examining the thing you own endangers somebody (including yourself?) should you be allowed to change its behaviors (consider as an example altering your car in an unsafe way)? As computers are now everywhere and have to do with everything, it is becoming a real political issue to decide if people should be allowed to really modify their computers. Smartphones most certainly do not allow it. PCs do, but they'r…
> What if examining the thing you own endangers somebody (including yourself?) should you be allowed to change its behaviors (consider as an example altering your car in an unsafe way)? Distinguish "allowed" from "able". It's unsafe to drive around with the brake light bulbs removed, but this doesn't mean that auto manufacturers shouldn't let you change your own brake lights.
But I'm actually thinking about digital computer techonology. In computers the difference between able and allowed works very differently. Specially in software-only contexts (hardware will likely remain hackable).
I'm trying to draw attention to the software-only case (which is also what the article's about).
My nightmare scenario is that by some means, things like web-inpsector tools cease to work, or require a licensed regulated permission to be opened or something.
A technology like WASM, it seems to me, accomplishes a similar goal without trying to do it. The goal of WASM is completely unrelated to restricting inspect-ability, which in turn reduces the ability to modify, yet it manages to do this, it raises the bar for changing webpages.
Re: Google doesn't want to pay Sonos for technology it copied
#113Sonos thought they just got a sweet revenue stream on a BS patent. Such a mediocre company (Sonos). I'm not saying they are a patent troll company but they aren't too far. As a user with lots of their tech in my house I'm very unimpressed with their offering - this patent defense seems inline with their mediocre tech. Far from a Google Booster here but just funny to watch their revenue stream go up in flames - probab…
Re: Google doesn't want to pay Sonos for technology it copied
#114For example, these changes mean you'll no longer be able to control the volume of a group of speakers. Instead, you'll have to change the volume on each individually. It also means you'll no longer be able to use the volume buttons on your phone to control a speaker group. Not here to defend Google, but how can something trivial like that even be patentable?
Re: Google doesn't want to pay Sonos for technology it copied
#115For example, these changes mean you'll no longer be able to control the volume of a group of speakers. Instead, you'll have to change the volume on each individually. It also means you'll no longer be able to use the volume buttons on your phone to control a speaker group. Not here to defend Google, but how can something trivial like that even be patentable?
The system has not been able to define a solid test for "non-obviousness" which is one of the criteria for patentability. As a result, in my experience, approvals are based most notably on "novelty" -- If no one has seemingly done in the past, it tends to get approved. In my opinion, that's what has gone wrong with the system, i.e., not the theoretical criteria for patentability but its execution.
Re: Google doesn't want to pay Sonos for technology it copied
#116Sonos thought they just got a sweet revenue stream on a BS patent. Such a mediocre company (Sonos). I'm not saying they are a patent troll company but they aren't too far. As a user with lots of their tech in my house I'm very unimpressed with their offering - this patent defense seems inline with their mediocre tech. Far from a Google Booster here but just funny to watch their revenue stream go up in flames - probab…
Re: Google doesn't want to pay Sonos for technology it copied
#117Re: Google doesn't want to pay Sonos for technology it copied
#118For example, these changes mean you'll no longer be able to control the volume of a group of speakers. Instead, you'll have to change the volume on each individually. It also means you'll no longer be able to use the volume buttons on your phone to control a speaker group. Not here to defend Google, but how can something trivial like that even be patentable?
The system has not been able to define a solid test for "non-obviousness" which is one of the criteria for patentability. As a result, in my experience, approvals are based most notably on "novelty" -- If no one has seemingly done in the past, it tends to get approved. In my opinion, that's what has gone wrong with the system, i.e., not the theoretical criteria for patentability but its execution.
Thus defining "non-obviousness" is super hard to do -- because it is all context dependent and humans are like a million monkeys inventing everything that can possibly be invented in aggregate.
Re: Google doesn't want to pay Sonos for technology it copied
#119For example, these changes mean you'll no longer be able to control the volume of a group of speakers. Instead, you'll have to change the volume on each individually. It also means you'll no longer be able to use the volume buttons on your phone to control a speaker group. Not here to defend Google, but how can something trivial like that even be patentable?
From my reading of the patent, it's not that the concept of speaker groupings was patented. Rather, a specific UI for showing and modifying the groupings and adjusting the volume. Unfortunately, there aren't many different ways to represent groupings in a UI.
Re: Google doesn't want to pay Sonos for technology it copied
#120Earlier quoted context omitted.
Kinda crappy but i'm sure google has tons of patents on things we would find trivial as well, as far as i'm concerned, let shitty mega corps duke it out.
That's also a feedback loop though, that exists in part specifically because of how easy and common patent trolling has been. They have to have patents over stupid trivial things because if they don't register these someone else will , and then suddenly it's an even bigger waste of time and money for everyone involved. There's a reason orgs like the Alliance for Open Media -- a Google-led initiative -- use licensing…
It also works as a way to keep incumbents in power. Say Google has 100 important mobile OS patents and Apple has 100 important mobile OS patents. It makes sense for them to cross-license. But a new mobile OS entrant has nothing of interest to Google or Apple and so no way to get access to those important patents.