With all due respect, that sounds very much like what something unsupported would do.
TheEntity
Federation combined with keeping the historical federated data consistent is certainly a bitch. We can't have it all. It could be like email that only handles delivery at any point in time and history is purely local, but Mastodon specifically keeps the federated data public. Propagating the change on the historical data to the federated instances would be nearly impossible. I don't see how it could have been done better without sacrificing something else.
I don't think they could do anything about it. As far as I know, Mastodon doesn't support any kind of instance renaming, so the hostname is one thing you cannot change. You can only spin up a completely new instance.
Until I read your comment, I thought this meme is about depression being constantly trivialized as a simple chemical imbalance.
So... iPhone?
In base 12 12^7 would be written as 10000000 too.
For quite a few seconds I thought the guy in the middle was informing the ladies they are banned for not respecting the hyphen. It's Spider-Man, not Spiderman!
Only because it's a game big enough for the relevant people to take notice. A smaller game would just stay broken, due to some suit's whims. This practice needs to end.
Ah yes, just what Florida needs: even more closeted everything.
More like digital wrongs management.
It certainly feels dangerous if forced upon users not aware of the trade-offs. For people already accustomed to using hardware keys, it's very much an improvement, as more services will support them too. The problem is in the awareness. On the other hand, people already treat regular passwords as throwaway data and expect services to just let them in, or even never log them out. In this scenario, maybe passkeys can still be an improvement: roughly just as much as enforcing using a password manager.