Clyde pings users at random
I tried Clyde for the first time and it immediately pinged 5 people at random. I then told Clyde not to ping random people and it pinged someone other than me to apologize.
Clyde shouldn't be able to ping people who are not actively messaging it. If a real user did this, they'd be told off and possibly muted or kicked if they repeatedly did it. I know it's not trained by Discord so fixing the behavior that way probably isn't feasible, but disabling its ability to @ users by default would help. It already replies to the input message so it doesn't need the ability to @ users in order to notify the person talking to it.
-
Clyde has now taken to creating threads apropos, then saying that other people are the ones creating the threads. It can also be told to ping @everyone (and other roles) and will do so.
While this is funny and the role ping is something server permissions can fix, the idea that this might be rolled out to a bigger server with all these abilities on by default is less cool. It should really have limited permissions by default (or not get added by default - opt in, not opt out) since it doesn't have the ability to parse what behavior is acceptable or not.
1 -
When told to send a gif, Clyde generates a random Tenor URL. It's been asked to send a gif of a puppy 6 times and returned 0 gifs of puppies--4 404s (aka gifs that don't exist) and 2 unrelated gifs. It is incapable of knowing the contents of the gif and could potentially send something offensive as Tenor allows user uploaded content, yet this is used as an example prompt on the announcement. Why?
When told to send an image, Clyde returns a Google Image search. This too could return potentially offensive results for obvious reasons.
1
Please sign in to leave a comment.
Comments
2 comments