Username cannot contain 'clyde'

Post by vidarh » Mon, Nov 21, 2022, 7:34 AM UTC

bobsmooth wrote: post #73

causi wrote: post #47

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…

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.

Post by causi » Mon, Nov 21, 2022, 7:41 AM UTC

vidarh wrote: post #82

bobsmooth wrote: post #73

Earlier 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…

Post by saghm » Mon, Nov 21, 2022, 7:45 AM UTC

blowski wrote: post #67

userbinator wrote: post #5

This 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.

Gizmoduck back in the 80s had this worked out. His bot invocation was "Blathering Blathernsikes".

Post by saghm » Mon, Nov 21, 2022, 7:50 AM UTC

judge2020 wrote: post #21

hn92726819 wrote: post #18

Earlier 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.

Post by Eavolution » Mon, Nov 21, 2022, 7:58 AM UTC

Gigachad wrote: post #34

taberiand wrote: post #16

Earlier quoted context omitted.

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…