nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqxj8gey62fpwz57fn3j4jclejs5vf57vws0c0pvhar8wgwre9j6zs8fekds (nprofile…ekds)
I have a couple of comments regarding the spec https://codeberg.org/portafed/portafed/src/branch/main/portafed-spec/spec.md
It contains a comparison with FEP-ef61, but it is not quite correct:
- FEP-ef61 identity is not actor-rooted. The closest equivalent of FEP-ef61 identity in normal ActivityPub is a server with a domain name. A single FEP-ef61 authority can manage multiple actor documents.
- FEP-ef61 does not lack a migration flow. Strictly speaking, it doesn't need one, because data is not attached to a server and can be continuously synchronized between multiple servers. But a more familiar migration flow is also possible via outbox export-import.
nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqhtmuyyqqsv7um4suy7aqmp90xu29wc3hthdwsc95qfkwkg6xzx4q3xe40t (nprofile…e40t)
