Maybe related to the Singapore data center currently under maintenance? But shouldn’t be significant slowdown, just routes somewhere else is all. 🤔
https://www.cloudflarestatus.com/incidents/x4j9jdzfftlk
If you log into the Cloudflare dashboard, go to R2 (it’s at account level, not zone level), then click the bucket and then go to Settings for the bucket, what’s the “Location” set to?
I’m going to disagree until the day I die on that. I see huge value in consistency. So presenting the username of user A differently than user B is never going to be a good option, imo. I mean unless you want to go back to the MySpace days and the cluster**** those profiles were. 😂
I'd say pick...
You could use something different to differentiate the username with edit to the same template. There’s really no limit when doing it via CSS… can have any prefix you want and/or any postfix you want. The @ is just what seemed logical to me… someone could prefix it with “Username: “ if they...
Yep, it’s super easy with a CSS entry. The @ addition is done with CSS, so could very easily override that with nothing or edit the template it’s coming from.
Maybe you are overthinking it? It works like this:
All usernames are prefixed with @
If a user has a display name set, show that as “primary name” with username as the secondary bit of data.
Nothing more, nothing less.
I knew in the back of my head people would have issue with the @ prefix...
Ya, I suspect it’s going to simply be an option. Going to be less time coding that than it is to explain the logic about why it ended up how it is. If someone wants to have nothing differentiating usernames and display names, go for it. 😂
I’m definitely not opposed to changing it, I do however think that whatever it is needs to be consistent for the site (all usernames treated the same and all display names treated the same). After a lot of trial and error, I landed on the @ for usernames (since that’s already how you address...