I too think it's possibly a software bug rather than a cache issue. We don't cache anything if you are signed in, and if it was a cache issue it would show both of the old names on the page rather than only one changing.
ticoombs
Hey! Sorry for the joke, I didn't expect it to be seen by a real user!
As we are one of the very few instances that has a no email policy there is very few ways in which we can determine if a person signing up is a bot or a regular user.
Recently a very very specific person or group of people have been abusing Reddthat to create accounts, then ask interesting questions (let's just say that), and then proceed to delete their account (which deletes all of their posts and comments). This makes it impossible to figure out what they have done unless someone quotes the reply or reports it before they delete it.
I'm sorry you got caught up in the little bit of fun us admins have with writing little anecdotes or fun catch phases!
You are welcome to come say hi on Reddthat any time!
Single user? We have 300+ users who actively call Reddthat home and we won't be going anywhere. We are nearly cash flow positive thanks to our amazing users and recurring donations.
I've seen your posts and as your mod on !aom i'd be happy to make you mod of our !rts community to help grow it!
Edit: I know @reddthat@reddthat.com would love the help
Looks easy : https://www.ifixit.com/Guide/Steam+Deck+SSD+Replacement/148989
Edit: Is it worth 30-60minutes of your time, the screwdrivers, maybe the spatchula, and reinstalling steamOS onto the drive?
Federation between Onion and Standard Domains that way tor users would not be isolated
This is the hardest part as you would need to be both have an onion and have a standard domain, or be a tor-only Federation.
You can easily create a server and allow tor users to use it, which unless a Lemmy server actively blocks tor, you'd be welcome to join via it. But federation from a clearnet to onion cannot happen. It's the same reason behind why email hasn't taken off in onionland. The only way email happens is when the providers actively re-map a cleanet domain to an onion domain.
This is what Lemmy would need to do. But then you would have people who could signup continuously over tor and reek havok on the fediverse with no real stopping them. You would then have onion users creating content that would be federated out to other instances. & User generated content from tor users also is ... Not portrayed in the best light.
I'm sure someone will eventually create an onion Lemmy instance, but it has it's own problems to deal with.
This is especially true for lack of moderation tools, automated processes, and spammers who already are getting through the cracks.
I can confirm the sections around downvotes as Reddthat has the stance exact what you are talking about (re your child comments)
A downvote disabled instance creates it's own algorithm/feed/ranking based purely on all other metrics, because as far as the data is concerned, it sees every post having 0 downvotes. It does not take into account external instances.
I can answer the first point.
We've already tackled part of that problem with the Parallel Sending feature that can be enabled on instances with a tremendous amount of traffic. Currently the only instance that makes sense to enable that is LemmyWorld and the only reason is so servers in geographical far away can get more than 3-4 activities/second.
With that feature, servers that eventually house and generate the biggest amounts of traffic will be able to successfully communicate all of those activities to everyone else who needs them.
I predict a 10x increase is well in our grasp of easily accessible by all of our current systems. 1000x? That's a different story which I don't have the answers too.
This might be another bug relating to federation, but might also be relating to caching on their end. Or because every Lemmy application keeps their own archive, it's possible the user display name doesn't federate on a change but only on a post that they can see? (Or not at all, or only on a timed refresh?)
Lets check after 24/48 hours on those links and we'll see what they say after that.