Earlier quoted context omitted.
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…
The developers of these things need to stop treating people swearing at them as a time to lecture them and instead realize that if someone is swearing at it then they’re probably not satisfied with how it’s functioning in the attempts before that.
Username cannot contain 'clyde'
141–150 of 225 posts
Re: Username cannot contain 'clyde'
#142Earlier quoted context omitted.
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.
Just off the top of my head, depending on accent or dialect: "spritzer", "waltzer", "Mitsubishi", "matzos", "mitzvah".
PIZZA P IY1 T S AH0
Looks like I can search for " T S " to find the "ts sound that's not at the end" % grep " T S " cmudict-0.7b | wc -l
991
Some of the non-proper nouns include ACCOUNTANCY, ANTSY, and ARTSY. I'll assume this is too close to the end to count, so require two sounds after the " T S ": % grep -E " T S [A-Z0-9]+ [A-Z0-9]+" cmudict-0.7b | wc -l
853
These include: bestseller, blitzkrieg, boatswain, bootstrap, chutzpah, craftsman, draftsmanship, footstep, hotspot, itself, jetstream, outscore, outsell, outside, postscript, shirtsleeve, shortstop, sportsmanship, statesmen, tsar, tsunami, whatsoever, yachtsman, and zeitgeist.(It doesn't have "spritzer" in the list, and uses the spelling "matzoh" instead of "matzo". I didn't look for a more complete list of word pronunciations.)
Finally, two words with two occurrences of the "ts" sound, neither at the end:
% grep -E " T S .*T S " cmudict-0.7b
ITSY-BITSY IH2 T S IY0 B IH1 T S IY0
TSETSE T S IY1 T S IY0Re: Username cannot contain 'clyde'
#143Earlier 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…
Re: Username cannot contain 'clyde'
#144Earlier quoted context omitted.
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…
I have no idea how things work under the hood, but this doesn't match my experience as a user. If I'm in the bedroom and ask to turn the lamp off, and phones are around, the phone screens sometimes lit up as they are listening to the command, but then only the bedroom Google Home actually executes it, while the phones turn their screen back off without saying anything.
We have to whisper to the Hub Max in the kitchen, from 3 inches away, and the Minis in the dining room and living room often still hear. If I don't whisper, even the ones upstairs hear. Sometimes I get 2 timers for my cooking, sometimes I get one on the wrong speaker. Then I try to cancel the timer, and the Hub Max hears instead and tells me I have no timers set.
The Hub Max asks on the screen if the wrong device responded. It clearly ignores your response, as the wrong device also responds the next time. I have pressed that button easily over 50x before I gave up and stopped.
Something clearly changed ~6mo-1yr ago because they never used to be this bad. It used to be that they would all listen, then only the closest one (that heard the command the loudest) would respond. Problem is, when I'm cooking the Hub Max is 1ft away and the rest are through (often multiple) walls metres away from me.
Re: Username cannot contain 'clyde'
#145Earlier quoted context omitted.
This of course rests on the assumption that there is such a thing as a 'regular name'. I'm obliged to link you to 'falsehoods programmers believe about names' now. I'm not happy about it, but those are the rules. https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
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.
We don't even have a database for all the humans alive today, much less one for the last 400 000 years...
Re: Username cannot contain 'clyde'
#146Earlier quoted context omitted.
It's not about the username being taken, it's all about what people appear as in the client; bots and scammers might impersonate Clyde to steal credentials, social engineer, etc, so you cannot be "Clyde_help" nor "Clyde_Official" nor any variation that would make people think the bot/user is speaking on behalf of Discord.
Why not just put a special logo or symbol or something on that profile to mark it as special/official, or have some sort of "user type" displayed that says "human" or "official bot" or "third party bot"? I feel like making it look like a regular username makes it _more_ likely people will be scammed by "other" regular users rather than less likely.
Re: Username cannot contain 'clyde'
#147Earlier quoted context omitted.
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…
The developers of these things need to stop treating people swearing at them as a time to lecture them and instead realize that if someone is swearing at it then they’re probably not satisfied with how it’s functioning in the attempts before that.
Re: Username cannot contain 'clyde'
#148Re: Username cannot contain 'clyde'
#149Earlier quoted context omitted.
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.
That fact seems dubious, does tzatziki not count?
Re: Username cannot contain 'clyde'
#150Earlier quoted context omitted.
Just off the top of my head, depending on accent or dialect: "spritzer", "waltzer", "Mitsubishi", "matzos", "mitzvah".
A fun code challenge! I started with https://github.com/Alexir/CMUdict/blob/master/cmudict-0.7b as a list of words with pronunciation. It has: PIZZA P IY1 T S AH0 Looks like I can search for " T S " to find the "ts sound that's not at the end" % grep " T S " cmudict-0.7b | wc -l 991 Some of the non-proper nouns include ACCOUNTANCY, ANTSY, and ARTSY. I'll assume this is too close to the end to count, so require two so…