- cross-posted to:
- fediverse@lemmy.ml
- cross-posted to:
- fediverse@lemmy.ml
Imagine a world without platform lock-in, where no ban or billionaire could take down your social network. That’s what ActivityPub has planned.
Imagine a world without platform lock-in, where no ban or billionaire could take down your social network. That’s what ActivityPub has planned.
I think without account karma the loyalty to the account would be less for the average person. The more annoying part is the communities you’ve subscribed to and finding them again. I think a simple download of a list that automates resubscribing on a new account would ease that issue for most people.
For an active user would be that you lose access to communities you created. That is a real logistical problem. I started on lemmy.ml and crelated a community then realized that lemmy.world ran a lot smoother (at the time) and moved. I luckily still have access to my original account so I was able to appoint my new account as a mod. So problem solved. If your instance splodes you lose that ability. But likely your sub went with it too anyway.
I guess the real problem I am identifying here is while the fediverse itself is decentralized, your account isn’t. It is locked onto one instance and the fediverse is volatile.
Maybe add an ability to attach your account on 2 or 3 instances and keep them synced? If one goes rogue then you have a backup that’s still on the fediverse? You can then defederate yourself from one if needed.
Idk.
I guess running a small private instance just for yourself is the best answer.
Thank you for your responses. It really makes me think about the meaning of portability:
Are you moving your identity? (e.g. implementing something like instance-agnostic user PGP keys)
Your data? The posts and comments you’ve contributed, which would only make sense with the context of the entire thread.
How would the contents of entire communities be migrated? I presume that’s where the valuable content is for potential buyers either to drive ad traffic or train models.
Mastodon’s export portability mostly focuses on the local social-graph aspects(follows, blocks, etc.) and while it has an archive function, people frequently lament losing their old posts and that graph relationship when they move.
Identity attestment is solvable in a legible fashion with any external mechanism that links back to report “yes, account at xyz.social is real”, and this is already being done by some Mastodon users - it could be through a corporate web site, a self-hosted server or something going across a distributed system(IPFS, Tor, blockchains…) There are many ways to describe identity beyond that, though, and for example, provide a kind of landing page service like linktree to ease browsing different facets of identity or describe “following” in more than local terms.
I would consider these all high-effort problems to work on since a lot of it has to do with interfaces, UX and privacy tradeoffs. If we aim to archive everything then we have to make an omniscient distributed system, which besides presenting a scaling issue, conflicts with privacy and control over one’s data - so that is probably not the goal. But asking everyone to just make a lot of backups, republish stuff by hand, and set up their own identity service is not right either.