On Discourse version v3.1.0.beta5 +233, if a new user chooses the name “adman,” “adman-b”, or “adman-c” that user’s profile is badly broken. Attempting to access the user’s public profile results in some extremely low-level failure that causes a never-ending page load (Firefox) or a simple hard error “ERR” (Chrome). This does not appear to be a trapped error.
I have verified that creating a user named “adman” results in the same problem at try dot discourse dot org. No other profile setup actions are necessary–for example, you don’t need to set a profile picture, or anything else–just using a name beginning in “adman” is enough to produce the error.
I have also verified that choosing “ad-man” as a username does not break the user’s profile. The username “adma” also does not result in a broken profile. I’m stumped.
Again, I’ve verified that this is true on both my own self-hosted Discourse, AND on try.discourse.org. I’m not sure how long the content on try.discourse.org remains before purging, but you can see this right now by trying to load the user profile there: httpx://try dot discourse dot org/u/adman/summary
Or you can see the effect by trying to look at the user “adman-c” on my self-hosted instance: httpx://discourse dot practicalzfs dot com/u/adman-c
Meanwhile, user “adma” on try.discourse works fine: httpx://try dot discourse dot org/u/adma/summary