Google: if you support Amazon Echo, you're cut off from Google Home and Chromecast
boingboing.net
boingboing.net
This was the highlight of the article for me.
Besides, many phones listen all the time too.
The only real difference is that the Echo has better microphones than your phone and is powered on all the time so you don't have to worry about battery life. On the other hand you probably say more sensitive things to your phone.
What is this boundless optimism? :-)
[1] https://www.ftc.gov/sites/default/files/attachments/competit...
Google is slowly building their brand position as 'invasion of privacy' despite their Kool-Aid colored logo.
Huge market opportunities for companies that can sell privacy by positioning themselves as the opposite of Google.
If it's search, I'd wager you're 100% correct. They've won that by all measures.
If it's voice assistants, maybe you're right. Even with Android devices everywhere, it would be hard to show how much share they have.
If the market is home automation, then the Nest thermostat is probably their biggest risk/penetration in the space, especially, if they can frame DropCams as monitoring and not automation. Odds are security companies and others we've never heard of have most of this market.
But if they can position the market as voice-based home automation, they are almost definitely safe. Amazon and Samsung probably have the majority of that market and Google is the "little guy" coming into the fight.
The big variable is that if search gives them an "unfair advantage" in the Court's eyes... which will be up to lawyers to argue.
That's a good point. Defining the relevant market is the name of the game in antitrust. Google could argue that they are a minor player in home appliances. If Samsung tried a lock-in contract, they'd probably be hammered in court. Google can argue they're a minor player in online retailing. If Amazon tried this, they'd probably lose.
Suffice to say, I've yet to see anything that indicates the FTC intends to do anything about Google yet. Until international cases and public opinion support action against Google so strongly that our government can no longer bury it, we're not going to see anything done here.
Alexa, Cortana, Siri, Samsung S Voice, wit.ai, Mycroft, ...
And their source is "multiple sources":
Google’s own negotiations with consumer electronics manufacturers could be
hampered by what multiple sources have described as overly aggressive
muscle-flexing. At the meeting in June, Google is said to have told home audio
vendors that they won’t be allowed to add any other digital assistants than
Google’s own to their hardware if they want to continue to use Google Cast.
Another source told Variety of similarly far-reaching demands made in
negotiations with another big consumer electronics manufacturer — demands that
ultimately led to talks breaking down.I previously read another take on that source on AndroidPolice[1] where it was framed more as "If you include Google Home you cannot include another Digital Assistant (e.g. Alexa)" which makes a lot more sense (obviously you can't have two assistants running at once) - though allowing it to be switchable would be nice.
It'll be interesting to see what the truth of the matter is.
"Hey Siri, change the music."
The last service requested should be able to take over the device.
Google's problem is that if tries to bully the audio makers, the audio makers will ignore Google Cast.
This is actually rather a stupid thing to do when Google is a minor player in a much bigger market. It's also going to make builders in other markets wonder if Google is good company to support.
The source website jumped around a lot, had a terrible full-page advert, and then for some reason completely blanked the page.
Disclaimer: work for Google, but so very far away from any of this stuff
The argument could be made (and I think Amazon technically claimed it) that Amazon blocked Chromecast from their store for incompatibility with their products, because Google won't allow forks of Android to have Google apps on them. Which is also anticompetitive.
So, if we want to suggest both companies are petty as all get out, it's plausible Google was anticompetitive, Amazon was anticompetitive in response, and then Google was anticompetitive again in reaction to that. What's next? Maybe Amazon will remove Chromebooks?
And as a result, Google will refuse to list amazon in search, their DNS servers won’t resolve it, and Chrome will refuse to open it, and their malware filters will mark it as fraudulent page.
It is funny but sad. I think we'll look back at the golden age of open Internet with fondness and nostalgia at some point
Well, we already have that, it's in your cellphone.
Indeed, we can confirm that they don't upload until woken.
Now, can we determine what they do upload at that point? Perhaps the previous two minutes of conversation, recorded for context to 'improve the consumer experience'? We just don't know.
Back in the early days of HTML forms on the Web, we were told to double-check the domain and SSL status before pressing 'submit'. Then JavaScript arrived and websites gained the ability to stream the data from text fields before the user had even submitted the form. I see a parallel with these in-house devices, they have a great deal of privacy-violating potential that runs contrary to people's expectations that a device only starts to perform a function when commanded to do so.
More processing power, everything centralized, I get it from a software engineering standpoint, but it's a privacy nightmare.
Next time I read someone claiming this I'll look or ask for a source. Do you have one that says they don't start sending until after the keyword?
> 1. How do Amazon Echo and Echo Dot recognize the wake word?
Amazon Echo and Echo Dot use on-device keyword spotting to detect the wake word. When these devices detect the wake word, they stream audio to the Cloud, including a fraction of a second of audio before the wake word.
Maybe the others are different, but Amazon has claimed that they detect the watch word locally and then start sending, but with a buffer that sends starting just before you said the watch word.
The article is a little light on evidence however, so I'm a little skeptical.
History always repeats itself for all these huge enterprises. Microsoft did all the same types of things, and their anti-competitive behavior was a significant part of the reason why Linux got that toehold that turned into a handhold... that turned into a...
The same thing is going to happen to Google in lots of other markets. They can only force people to use, I mean line extend, their brand to a certain point before they paint themselves into a corner.
It should be noted my issues with Google is really more of an issue with corporate surveillance - of which Google happens to be king.
I'm not criticising you, I'm looking for honest discussion. We can opt out of these things, until they become de-facto mandatory to education, jobs, etc.
Unfortunately for many of us, it's impossible to avoid dealing with at least one of these big behemoth companies. The best we can do is to keep dancing from one to one based on what the least worst option is at the time.
Right now, I'd trust Microsoft over both Google and Apple, but I also have no misconceptions about the reality that at some point, that will almost certainly change. When a company is on top, it looks for how to stay there. So the goal for the freedom-minded individual should probably be to constantly support the party currently losing the war.
[1] which I only use for the (proprietary) Spotify Connect
Buy a simple $8 3.5mm -> BT transmitter and plug it in. Done.
Actually cars are pretty far ahead in that sense, in any modern car BT "just works".
I'm hoping that either i'm reading it wrong, or variety has misinterpreted the sources, and google is actually attempting to block multiple voice assistants on a per-device level. Because to me, that makes perfect sense - products like amazon's echo or google home would get very confusing if they included multiple different voice-triggered assistants.