Earlier quoted context omitted.
I know an Alexa. She hates it.
The only assistant not to be paired with another word as well.
Apple is reportedly planning to remove "hey" from their wake word
Username cannot contain 'clyde'
31–40 of 225 posts
Re: Username cannot contain 'clyde'
#32You can’t create a Gmail account containing the words support, gmail, google, and several other variations
Re: Username cannot contain 'clyde'
#33Why don't bots have some other distinction? Like a blue tick or or some screenreader function?
Why do their messages have to appear the same as humans?
If bots should all operate in a distinctive space, give it that space.
Mind you architectural foresight is hard so maybe they'll get there.
Re: Username cannot contain 'clyde'
#34Why is an internal system in the same namespace as users? I wonder whether there are constraints that made it difficult to implement this functionality in another way, or this is just a bad design decision.
It's probably a mix of both. Namespacing often seems to be an afterthought in many systems, and it can be hard to refactor in once an architecture has solidified. It's not always the wrong choice to mingle identifiers of different types, but I think often people err on the side of convenience (/ laziness) instead of thinking through all of the potential issues.
The discord username namespace is weird. You get to set a display name which doesn't have to be unique so you can have the name "Bob" and that's what shows up when you message people, but then you also have a unique version on your profile that looks something like "Bob#3922" I'm not sure what happens if 10,000 people pick the same name but as far as I know, there is no limitation to how many people can have the same username.
So it seems almost impossible that this is some technical limitation but rather Discord cracking down on a common deception tactic.
Re: Username cannot contain 'clyde'
#35This 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
Re: Username cannot contain 'clyde'
#36Earlier quoted context omitted.
I feel bad for all the Alexas and the few Siris out there that have had their names hijacked my a couple of the biggest companies on the planet.
Slightly different, but my friend's daughter Isis hasn't been too happy about what's happened since she was born.
Neither was AT&T, T-Mobile and Verizon when they named their mobile wallet solution ISIS shortly before the caliphate was formed. [1]
Re: Username cannot contain 'clyde'
#37This 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.
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.
Re: Username cannot contain 'clyde'
#38This 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.
Written like that Google suddenly looks like geniuses.
Re: Username cannot contain 'clyde'
#39Why don't bots have some other distinction? Like a blue tick or or some screenreader function? Why do their messages have to appear the same as humans? If bots should all operate in a distinctive space, give it that space. Mind you architectural foresight is hard so maybe they'll get there.
They do have the tick next to their names and yet they still have this nonsense in place anyway.
Re: Username cannot contain 'clyde'
#40Earlier quoted context omitted.
> This is a good case for why system bots/messages/etc. shouldn't be given regular names I disagree. The username can be clyde_discord/clyde_bot and the display name could just be "Clyde". Then the username Clyde wouldn't be taken, and the users would be able to still message the bot and not be confused. Though I personally really dislike simple human names for bots because it sounds cheesy and dumb.
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.
Which is funny when you take into account that people are still using special characters to get a Clyde name that mostly resembles it. I question the effectiveness.