Salta al contenuto principale


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/…

#FediDev #MoveAllPosts


Alright it's late and i need to go to bed, but here's a draft FEP to do full account migration with posts and whatever other kinda objects you want to bring with you. It's a trivial expansion of existing ActivityPub/streams systems and supports gradual migration as it's implemented and after an account migration. It should be possible to migrate pretty much everything this way, both private and public objects.

criticism, feedback, revisions, etc. welcome - i don't think this is a "final version" and there are certainly things i overlooked.

codeberg.org/sneakers-the-rat/…

codeberg.org/fediverse/fep/pul…

#MoveAllPosts #FediDev #FEP #FEP_1580 #FullMigration #AccountMigration


Questa voce è stata modificata (1 mese fa)
in reply to jonny (good kind)

despite receiving probably the most notifications of anyone on fedi, i have been told that this may be of interest to @pluralistic , having written extensively about the importance of the power of being able to leave re: preventing feudalism and lock-in
in reply to jonny (good kind)

Gonna try and negotiate an acceptable implementation with the masto devs (if u see this no pressure! Ik ur busy), will take a bit of background work like to implement an integrity proofs FEP, so may take a bit, but if you wanna write this with me I would love to work together on this. hopefully its implementable, it's my first spec document ive ever written so idk what I'm doing rly I just think I can write it and wanna move my posts around and break down the feudal fedi
in reply to jonny (good kind)

Also if anyone wants to write about the social/political/governance problems caused by not being able to move your stuff with you when you move for motivating context, I'd be glad to put it in, I haven't had the energy to write that yet
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 Move activity 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)

in reply to jonny (good kind)

also it theoretically allows you to do a chain of moves, including moves without changing actor URI to rotate keys, so you can deal with repeated moves or old posts. idk it may help with key rotation but I know enough about cryptography to know that I don't know enough to say that confidently.
in reply to jonny (good kind)

Speaking of which, shoutout to @ansuz for taking the time to give input and info on some of the cryptography stuff (if there are places where I am super wrong about things that is all me though)
in reply to jonny (good kind)

thanks for putting in all the work to help make this happen! I know it will make the fediverse much more viable in many people's eyes and would love to see it get implemented
in reply to jonny (good kind)

how does this relate to the LOLA proposal from the SWICG? That has been in progress for quite some time and I’d like to see a comparison / how this integrates or handles the cases and issues identified.
in reply to Andy Piper

@andypiper
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
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.