this is definitely worthwhile! I need to get much better with the practicalities of activitypub myself. like David pointed out, it’s an underspecified protocol so understanding it involves digging into more than one implementation
over morning coffee, while looking through the source investigating this avenue, figured i'll need to get some idea of what the activities in AP may be, and what they influence/offer
reading:
The "Understanding activitypub" blog posts link to a test instance of mastodon that has an activitypub explorer. You can point it at your own servers to see what happens. This has been immensely useful for me.
probably the first thing to learn is:
activitypub is underspecified and the implementations are idiosyncratic.
this means that you can only get interoperability that works by trying pairs of software against each other and seeing what works. following the spec is only the first step.
I'm working on a single user node that can talk to Lemmy and mastodon. The idea of having my own homegrown "ship" (stealing that from urbit, sorry guys) for interacting with the fediverse is tantalizing for me. Progress so far, however, has been minimal.
there are various tiny nodes, like goto social. Or even a personal Akkoma isn't unmanageable. Does Akkoma interoperate with Lemmy? (If it doesn't, that's definitely something for philthy to get on the case for!)
this is FreeAssembly, a non-toxic design, programming, and art collective. post your share-alike (CC SA, GPL, BSD, or similar) projects here! collaboration is welcome, and mutual education is too.
in brief, this community is the awful.systems answer to Hacker News. read this article for a solid summary of why having a less toxic collaborative community is important from a technical standpoint in addition to a social one.
some posting guidelines apply in addition to the typical awful.systems stuff:
(logo credit, with modifications by @dgerard@awful.systems)