[fire]

The key point here that was hard to find is that they and others had a username containing Clyde set already, and now can't update anything else about their profile because their username has come to be considered invalid.

That's pretty poor judgement to not even communicate this to affected users

[hn_throwaway_99]

> That's pretty poor judgement to not even communicate this to affected users

Thanks for the clarification, but imagining it's pretty easy that this could just be a bug, e.g. they knew they wanted to prevent future usernames from having "clyde", and maybe even realized some existing clydes would be grandfathered in, but didn't realize it would prevent existing clydes from updating anything else on their profile.

[fire]

yeah, it would be pretty simple to skip validation of the username if it didn't change

[oneeyedpigeon]

Sounds like they're doing a PUT when they should be doing a PATCH.

[plusminusplus]

If you use a + sign in your email, some services accept it at sign up but not later on, when users try to update it.

[fire]

yeah, I've had this happen a number of times because the service was treating the `+` as a space in either the signup or the update, and I've had some success forcing it by replacing `+` with `%2B`