Back

@helge Highly agree.

That's partly what we're working on with the portability FEPs and CG report (roadmap: https://codeberg.org/fediverse/fep/pulls/334, export API: https://codeberg.org/fediverse/fep/src/branch/main/fep/9091/fep-9091.md, export data model: https://codeberg.org/fediverse/fep/src/branch/main/fep/6fcd/fep-6fcd.md).

And what @silverpill is working on with https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md and related FEPs.

@dmitri @helge @silverpill really?! You "highly agree" with off-boarding people from ActivityPub?!

@dmitri @helge @silverpill Ah, that makes much more sense! Thanks for the clarification.

@evan @helge @silverpill Or to put it another way: when Fediverse achieves full data & identity portability, it'll be the first protocol/ecosystem to do so (and don't @ me, i'm well aware of previous and current portability work). And I genuinely think we're not far off! If we get import & export right, that'll also mean it's easier to migrate TO the Fediverse, not just from.

@dmitri @helge @evan Fediverse already achieved full portability, albeit on a small scale.

The very possibility of it is a proof that ActivityPub is a good protocol. Usually, if a major protocol feature wasn't considered at a design stage, it can't be added later in an organic way.