Gregory's ServerI've been developing an #ActivityPub C2S-based (with extensions) API facade/proxy proof-of-concept for Mastodon. It runs as a separate process that supports proxying the Masto operations but also adds a postable C2S outbox with support for AP C2S activities. These activities are converted into upstream Mastodon API calls. This extended C2S API also supports search, streaming events, managing bookmark collections, and retrieving timeline collections. 1/2
|
4 posts total
I submitted a draft FEP describing the Mastodon and LitePub/Pleroma #ActivityPub relay protocols. Comments and corrections are welcome. https://codeberg.org/fediverse/fep/src/branch/main/fep/ae0c/fep-ae0c.md I see discussions sometimes about developing recipe applications for #ActivityPub/AS2. In that spirit, I wrote a blog post describing how to use the schema.org Recipe type in an AS2 conformant manner. It's mostly a thought exercise about possibilities since most AP implementations won't render an AS2 conformant recipe correctly, if at all. I wanted to be able to search and browse the #ActivityPub Fediverse Enhancement Proposals (FEPs) so I converted them to an Obsidian vault. As a nice side-benefit, I can now view the graph of FEP dependencies and their color-coded status (green=FINAL, yellow=DRAFT, red=WITHDRAWN). |
The code isn’t quite ready to be published yet and the purpose of this C2S PoC implementation (Python) is experimentation, not high-performance production use. However, it will be useful for prototyping C2S extensions that can be documented using the FEP process. The documented extensions could be implemented as native functionality instead of using a proxy. The benefit of the proxy is that the proxied Mastodon instance still supports both Masto clients and extended C2S clients. 2/2
@steve fantastic!