RE: neuromatch.social/@jonny/11534…
Rumors that the fediverse can't do mobile identity have been greatly exaggerated: #FEP_1580 is now in draft status - codeberg.org/fediverse/fep/src…
This is a proposal for how to migrate all your stuff along with you when you move instances.
The gist:
- Send a request to move along with a set of stuff you'd like to bring with you. Moderators (optionally) can, approve, send back a change request, or deny. If the changes look ok, start the move, if not, hey you avoided incompatible moderation. Should be possible to layer in any kind of bulk actions you might want: "everything except my DMs," "strip attachments," "only my favorite posts," "nothing," etc.
- keep a public collection of move events signed by both the source and target for durable, portable proof that you are the same person as the old account
- the new instance crawls your old account and grabs whatever you specified, and then posts a mapping from old URIs to new URIs.
- other instances can then immediately remap the URIs so e.g. future interactions get sent to the right place, and then gradually update their local versions over time, spacing out traffic.
Just using existing ActivityPub mechanisms. There are 6 new terms.
Bonus: lays the next steps to migrate to content addressed URIs, decouple accounts from instances, and merge and split accounts.
It being a draft means that there is a 60 day (or longer) public comment period, and feedback/edits/etc. Are very much welcome.
Issue: codeberg.org/fediverse/fep/iss…
Discussion: socialhub.activitypub.rocks/t/…
Questa voce è stata modificata (1 mese fa)
reshared this
jonny (good kind)
in reply to jonny (good kind) • • •jonny (good kind)
in reply to jonny (good kind) • • •jonny (good kind)
in reply to jonny (good kind) • • •jonny (good kind)
in reply to jonny (good kind) • • •Also it treats post backups as posts (I mean they should anyway, importing a list of posts is the same as posting a list of posts, and backdating is not a crime), and if instances support exporting your private key with account backups, then you can create a
Moveactivity without needing the source instance, so account backups are just... your account in a file, so you can restore if your instance goes down or becomes hostile.CBOR and CAR files and Merkle Search Trees are cool, but so is a zip file of JSON.
(This is spec'd as a "should" BC there are some problems to work out incl. Key rotation and etc. but the mechanism for remapping is general and driven by the new instance)
jonny (good kind)
in reply to jonny (good kind) • • •jonny (good kind)
in reply to jonny (good kind) • • •ansuz / ऐरन
in reply to jonny (good kind) • • •Andy Piper
in reply to jonny (good kind) • • •jonny (good kind)
in reply to Andy Piper • • •I heard of the LOLA proposal after drafting this, and still havent found it but now knowing it comes from SWICG should be enough to. I'll take a look. I would defer to protocol experts, but lemme take a look
flere-imsaho 🇺🇦
in reply to jonny (good kind) • • •LOLA Portability for ActivityPub (0.2)
swicg.github.ioreshared this
just small circles 🕊 reshared this.
Ben Pate 🤘🏻
in reply to jonny (good kind) • • •Very cool. We absolutely need a full-fidelity move that’s supported by as many apps as possible, and you FEP looks very well written.
I’ll catch up on your work and share my thought on codeberg 😀
Could you compare/contrast this with the LOLA work going on under the W3C. It’s a solid plan, but it can be hard to decipher in places: swicg.github.io/activitypub-da…
I think it’s super important for us to define migration well, once. Competing specs could easily derail the whole thing.
LOLA Portability for ActivityPub (0.2)
swicg.github.ioSean Tilley likes this.
Andy Piper
Unknown parent • • •GitHub - swicg/activitypub-data-portability: Repository for data portability report and solutions for ActivityPub
GitHub