Notices by Dmitri | 🇺🇦 (dmitri@social.coop)

@hrefna I think it partly depends on what you mean by 'mastodon compatible'. if you’re running straight up mastodon, forget it. not possible. if you’re running an implementation of some of the recent data portability FEPs, all 3 are doable. The tricky part is - how much are you automatically porting over (identity, posts, social graphs, reactions, etc etc). And whether the old server is alive to provide support or not. But it's all doable.

@cwebber Hey, for what it's worth. @bengo and i are working on exactly that for the Fediverse! We've got the FEPs written, a content-addressed zCap powered storage backend MVPd, and are now working on fedi integrations!

@sun @silverpill my recommendation would be to look at did:tdw https://identity.foundation/trustdidweb/ (which may soon be renamed, heh). It's got some of the good features from Bluesky, and is on the way to be standardized.

@silverpill @mariusor wait, but that relay you're describing - that's an auxiliary service

@silverpill @mariusor what about cross-instance (opt in) Search? That kind of does need to be an external service, no?

@thisismissem I really do think AP could support did:web (and its successor, did:tdw). That was part of the motivation behind FEP-e3e9: Actor-Relative URLs https://codeberg.org/fediverse/fep/src/branch/main/fep/e3e9/fep-e3e9.md (basically, to provide a path for upgrade to DIDs). What's a DID? 1) Keys, and 2) service endpoints. For 1, there is https://codeberg.org/fediverse/fep/src/branch/main/fep/521a/fep-521a.md For 2, FEP-e3e9 and https://codeberg.org/fediverse/fep/src/branch/main/fep/9091/fep-9091.md show examples of how to do it. Taken together, they essentially turn an Actor into a did:web.

YESSS I desperately want that feature. Lets get a design together (& talk to Peertube and Funkwhale who seem to have this feature already, see what we can learn)!
https://mstdn.ca/@AmeliasBrain/113216003650977412

@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.

@evan @helge @silverpill Breathe... i'm just talking about export and portability...

@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.

Why is the char limit on profile description so short? Sigh, pinned posts it is.
Ok, things to know about me:

Until we sort out "multiple channels/feeds for a Fedi actor", this account is a mix of everything, srs bzns standards, and goofy memes and reposts. Meaning, please lower your expectations/bar for any sort of professionalism.

@kissane then we (the microblogging network) have failed!! :) Where ELSE do you put hot takes & shit posts & profound missives? :)

@evan 's ActivityPub book is coming soon from O'Reilly: https://www.oreilly.com/library/view/activitypub/9781098162733/ch01.html

Great discussion on DIDs and the Fediverse. Talked about DID<->AP Actor Profile<->ATP round-trip linking, migration from dead servers, migration across different protocols and domains, other stuff. And hey, resulted in this: https://github.com/snarfed/bridgy-fed/issues/1331

Last day of #FediForum 2024. Excellent sessions. More linkdump / bookmarks:

* Unconference in the UK coming up -> https://oggcamp.org (Andy Piper is one of the organisers and it is open source and free culture)

@snarfed.org Completely agree. The whole notion of Fediverse instances as tightly coupled bundles of identity, message storage, moderation, front-end UI, and community groups, has to go. And I agree that there's nothing about AP that dictates that (even the identity part), it was just a set of arbitrary easy choices done by early implementations.
And I think slowly, each of those aspects is getting specs/FEPs that allow separating and refactoring them out.

The first 2023 W3C SocialWeb Incubation Community Group (SWICG) call will be this coming Fri, May 19, at 9am EST. details over at https://socialhub.activitypub.rocks/t/first-2023-swicg-meeting-call-on-fri-may-19/3225
Reminder: these calls are open to everyone, you do not have to be a member of W3C or SWICG to attend.

Excellent design. The Fediverse needs more of this - general headless servers rather than platforms like Mastodon.

From: @Natureshadow
https://floss.social/@Natureshadow/110355574434610009

@panos @kainoa @syuilo @Gargron Hi Panos, would it makes sense for the Calckey devs to do a writeup on how they're implemented Quote Posts, on somewhere like the FEP repo (https://codeberg.org/fediverse/fep ), so that we can point implementers at it?

@silverpill Would you be interested in attending the first SWICG call?