Nomadic identity for the fediverse?

ActivityPub
22

Turns out FEP-8b32 is not required for migrations, and FEP-c390 should be enough to implement them. Here’s an example of Move activity:

{
  "@context": [
    "https://www.w3.org/ns/activitystreams"
  ],
  "actor": "https://server2.com/users/alice",
  "id": "https://server2.com/activities/00000000-0000-0000-0000-000000000001",
  "object": "https://server1.com/users/alice",
  "target": "https://server2.com/users/alice",
  "to": [
    "https://example.com/users/bob"
  ],
  "type": "Move"
}
  • object is the old account
  • target is the new account (which initiates the migration)

This activity could be sent by the server even without FEP-8b32 integrity proof. Actors identified by object and target properties must have at least one FEP-c390 identity key in common to be considered aliases.

4 Likes