LOLA: Account Portability Interop Spec
/2024-09/session/3-a/
Convener: Lisa Dusseault (@lisarue@mastodon.geekery.org)
Participants who chose to record their names here:
- Jeremiah Lee (@Jeremiah@alpaca.gold)
- Jennifer Moore (@jenniferplusplus@hachyderm.io)
- Andy Piper (@andypiper@macaw.social)
- BjornW (@bjornw@mastodon.social)
- Aaron Gray (@AaronNGray@fosstodon.org)
- Aaron Klemm (@aklemm@mastodon.social)
- bumblefudge.com
- Alexa Hyde (@an_alexa_k@instance.digital)
- Simon Blackstein (@sblackst@threads.net)
- Nigini Oliveira (@nigini@social.coop)
Notes
LOLA: https://swicg.github.io/activitypub-data-portability/lola.html (source: https://github.com/swicg/activitypub-data-portability)
FEP-e965: Move Activity for Migrations and Announce Activity for Tombstone Events: https://codeberg.org/fediverse/fep/src/branch/main/fep/e965/fep-e965.md
LOLA: Live, online portability (Linking OnLine Accounts?)
“Live” means that the source server is online and available for the data to be moved to a new place.
Lisa Dusseault is working on proposal for account and data portability as a job. Coming at ActivityPub as a data portability protocol for data and things other than might not be used for today like social media.
Data Transfer Initiative (founded by Apple, Meta, Google): https://dtinit.org/
- Get permission from live, online server to move the data.
- Destination server pulls the data over.
- Online server puts up “redirect sign” or “tombstone” to new home for the data.
- Previously property notes where the content was previously hosted so future access can find present location.
What about GDPR?
- Similar to email. For example, you have sent a reply to the server of someone. You can request they delete it formally. You can also delete it and their server should honor the request to delete it.
- Other servers should check if their “cache” of that is still present at some point if they were not the original recipient of that post.
Considerations:
- Association with activities (around the Fediverse) with the initial URL.
- Expectations of a server dealing with data that moved?
- Lisa: In the spec for the origin server to redirect all requests to the new server. https://swicg.github.io/activitypub-data-portability/lola.html#hosting-redirects-for-objects
Would be nice for a server to do that for at least a year.
- Case: what should a server do when posting a reply to a post? If the posting server SHOULD check if the initial post still exists, that would be a great opportunity to update the URLs (if posts moved).
- Sounds like a update-as-needed - based on the interactions on posts!
- Legal considerations around the URL “provider”.
- Validation of ownership of the two involved accounts.
- Replicability and Reliability of the data: users would lose data forever if their one-home-server goes down/away!
How to contribute:
- Join the SocialWeb CG email list: https://lists.w3.org/Archives/Public/public-swicg/
- Subscribe to FEP repo.
- https://socialhub.activitypub.rocks/
- Matrix channel: #fediverse-devs:matrix.org https://matrix.to/#/#fediverse-devs:matrix.org