@verbeeld @saki @dylanvanassche @argahsuknesib @hochstenbach interesting! Wouldn't have expected that 😅 Wonder how it works. Will dive deeper

@pietercolpaert @verbeeld @saki @argahsuknesib @hochstenbach When you move, the new server will contact the old one and transfer your followers. Your followers do not need to know you moved. Basically a temporarily sameAs.

@dylanvanassche @argahsuknesib Your main data always lives on the server of someone else (unless you host it yourself of course). I wonder if we can make the data live on your Solid storage first (L1), and on someone else’s server second (L2) to make all custom functionality of Mastodon work.

@pietercolpaert @argahsuknesib The server APIs are open of course. You can build different kind of servers... For example: GoToSocial is server which doesn't have a GUI like the original #Mastodon server. You could have a Solid Server plugin which handles the Server API and stores everything in your pod (L1). NextCloud is building something similar to interface their social solution with the #Fediverse. You could also have a server which accepts external Solid pods (L2)

@pietercolpaert @dylanvanassche @argahsuknesib
The first sensible add-on functionality could be a server independent message history on Solid that remains independent of your current server. Because messages are not transferred when migrating. But details are complicated as no one ever agreed that their interactions with you are stored elsewhere.

@pietercolpaert @saki Solid has been around long enough that there ought to be compelling demos of this sort of functionality by now, even if incomplete. What’s the best we have to show?

Has anyone tried implementing ActivityPub on top of Solid?