Top-level
4 comments
@0x0 so all the posts are "hard coded" with the path of the username that posted it, so designing a mechanism that would let a user move to another server and bring their old posts with them is sort of impossible with most fedi software. There are solutions to this issue in places like 'streams' nomadic identity and other places like Nostr and maybe Bluesky (tho thats yet to be seen in practice) but this is a space where the fedi really needs to do some work... @liaizon @dev I've been also a bit on the fediverse for a while now (started using it like half a year before Mastodon first released; back then on GNU social). And I agree, seeing all the new projects and tooling around the fediverse is really great. Things like GoToSocial, Elk, etc. are really inspiring, and especially with Elk focussing on the UX, it a really big step towards more people adopting the fediverse |
@0x0 I noticed that usernames on Kitsune look like some sort of key or hash: https://dev.joinkitsune.org/users/01884a0f-78fb-73be-a3df-f92027ab39c7 and then are displayed as @dev to Mastodon. Do you have an outline of how you imagine names will work moving forward? and how that might work in the future when things like account migration start coming into play? One of the main issues with older software in the fedi is that they have not been designed with the ability to change usernames from the beginning