Earlier quoted context omitted.
That's interesting, I did some digging into Apple device communication and it turns out they have a protocol called CompanionLink that handles this exact circumstance - devices can communicate securely with each other and decide who is going to handle the Siri activation - HomePod's seem to get preference, then phones then laptops. I'm surprised Google hasn't done something similar.
They do. You also get occasional feedback notifications asking you to confirm that the device that answered is the one you expected. More than one should never answer. I wonder if location is misconfigured on individual devices, but I wouldn't bet against a bug.
Username cannot contain 'clyde'
201–210 of 225 posts
Re: Username cannot contain 'clyde'
#202Earlier quoted context omitted.
Written like that Google suddenly looks like geniuses.
At least in the naming, sure. Everything else, not so much. I had to switch my whole house over to Echos because you can't change the wake word on Google Home. Every time I said, say, "Hey Google, turn the bedroom lamp off", the Home in the bedroom would say ok and turn the lamp off, both phones in the room would activate and complain that they didn't have a device named lamp listed, and every other Home in the house…
Google should have done that too, but it seems you might not have had them all part of the same home (or something else was broken/buggy).
Re: Username cannot contain 'clyde'
#203Earlier quoted context omitted.
Yeah, sure. The very first comment in the Reddit thread says "I use Clydē and it works," and the third one is "CIyde. Use capital i instead of L," so nice try, but no.
All usernames on Discord have a four-digit number after them called a discriminator, separated from the rest of the name by a # symbol. In the Reddit post in question, that number is #6381. The problem isn't that the (fake) bot is in the same namespace as users; if there were any problem like that at all, it would be a shortage of discriminators. However, that's not what this message is saying. It's saying that the n…
Just as a random, poorly thought-out example, internal stuff could be namespaced with a different prefix like "&Clyde" instead of "@Clyde". As long as users know that official stuff is addressed with &, it matters less what people do with @-namespaced stuff because there's an easy way to tell whether it's actually official or not.
By putting official stuff in the same namespace as user-generated stuff, it's much harder to tell whether something is an official tool or not. @CIyde could be a real internal account.
Re: Username cannot contain 'clyde'
#204Earlier quoted context omitted.
Well, the verbification of the word google introduces its own difficulties there. The ideal would be for the voice assistant to have some completely unique word, ideally with sound combinations that are very rare in your native language. And if for some reason, that still doesn't work for you, have a way to change it. Or maybe just not have a default, and require users to pick their own keyword.
In English, there’s only one word in the entire language with a ts sound (pizza) that’s not at the end. They probably could have come up with a name utilizing that fact, making wake words super “easy” to recognize and hard to accidentally say.
Re: Username cannot contain 'clyde'
#205Earlier quoted context omitted.
It's not a meme in the same sense though. If this was a short punchy quote that implied that certain memes were bad, then yes.
All right, let me explicitly substitute for pronouns: your comment was aimed against specific, easily disliked subgroup, namely, "Karen" memes, and so it is unavoidably an attack on the entire group, namely, memes, by association. It is impossible to say "a "Karen" meme, which is a meme, bad" without implying "memes "Karen" memes, memes bad." Or if there is a way to disentangle them, it certainly won't fit in a comme…
It's amazing how everything is applicable to everything if you freely redefine the terms used.
edit: Sorry, that was a bit snarky. I think there's reasons why this applies to quick, punchy memes but not to longform comments: memes are antithetical to nuance.
Re: Username cannot contain 'clyde'
#206This is a good case for why system bots/messages/etc. shouldn't be given regular names (and perhaps distinguished through other means too); if the error was instead "Username cannot contain 'discord'", it'd be more obvious.
Amazon: Alexa Microsoft: Cortana Apple: Siri Discord: Clyde Google: Google Disclosure, I work at Google.
Re: Username cannot contain 'clyde'
#207Re: Username cannot contain 'clyde'
#208Earlier quoted context omitted.
You can't change the wake word because a separate, dedicated chip is listening for it and is not connected to the rest of the device except to wake up the main processor.
Then they could at least provide more than one option. Though while far from perfect, one of the things I like about Alexa/Echo more than the ability to change it, is that with multiple devices you will generally only trigger one (the others within earshot will listen and then ignore it once one of them has picked it up; works well in my house at least apart from one place where echo/reflection sometimes causes one i…
Re: Username cannot contain 'clyde'
#209Earlier quoted context omitted.
They didn't have to. Never ever cave to bully demands. That only teaches them they have power.
Mental health is more important than telling yourself that adapting makes you weak. And please stop with this bullshit along the lines of "just ignore it", that's not how bullying works.
Re: Username cannot contain 'clyde'
#210Earlier quoted context omitted.
We can put bounds on it. Here's an easy lower bound, for the context of avoiding collisions: The name has to have been used by at least two different humans. Or to get closer to a reasonable bound, 100 humans.
How would you know how much it has been used ? We don't even have a database for all the humans alive today, much less one for the last 400 000 years...
And people that are dead won't be inconvenienced, so you can ignore them.