silverpill@silverpill@mitra.social: @gary ActivityPub data can be portable too, even distributed across multiple instances:<br><br><a class="link-in-note" href="https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md" target="_blank" rel="nofollow noopener">https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md</a><br><br>But popular Fediverse platforms don't support this feature.

Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Gary@gary@pottering.uk (2026-04-15 01:24:14)
My technical know-how falls short by a long way and I'm having a little trouble figuring out whether I get what I want from the Fediverse. By my limited understanding AT Protocol allows for a 'nomadic' id/datastore (PDS) but with ActivityPub, the nearest we get to that is by having your own instance of an app of your choice and plugging it in/out of other peoples, but your data can only really live in *your instance of *that app??

#Fediverse #atproto #ActivityPub #Data #Identity #PotteringAbout
---Reply---
silverpill@silverpill@mitra.social (2026-04-15 04:30:37)
@gary ActivityPub data can be portable too, even distributed across multiple instances:

https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md

But popular Fediverse platforms don't support this feature.