I've started putting together a list of #fediverse apps, focused on implementations of #ActivityPub, documenting their status and what tech stack they're (being) built with: https://ethercalc.org/fediverse-stacks
This is a publicly editable doc, so would appreciate corrections/additions, and feedback especially from fediverse devs, but also from instance admins and users:
- What app/implementation/stack did you try?
- Pros/cons you encountered
- What stack & libraries would you choose if starting today?
PS. We've been talking with @bhaugen and others about the need for a generic agent-centric #ActivityPub server, so that instead of signing up to a bunch of different servers, a user could have their indentity and data all in one place, and all the apps they use (clients, but if necessary server-side "plugins" as well) would interact with the activity/objects types that they support.
What do you think?
See here progress about feature set, what's implemented already and what's still missing:
@h That's definitely what I'd rather do. Have you played around with that library? Opinions?
@h @mayel I'm happy to answer any specific questions, including discussing limitations of the current library. I've tried to be honestly thorough in the GitHub issues, although please ignore the GitHub milestones, I need to redo those.
A basic tutorial and the library's documentation are also available at https://go-fed.org
I am very interested if/how the library supports extensions, as that's a key requirement for a couple projects for which I'm looking for the best implementation approach, and your docs say that "ActivityStreams vocabulary supports extensions beyond the Core and Extended types. However, this will be outside the scope of this tutorial"
1) In the tool used to auto-generate the ActivityStreams implementation.
2) The go-fed/activity/pub library also would need to pass-through any new Activities defined in this way.
I'm gonna go ahead and capture both in github issues.
What kinds of extensions are you looking at, specifically?
@mayel OK, I've given it some serious thought and have created two issues to track this work:
In all honesty the work is larger than my gut feel (isn't it always?!) so I've scheduled it as part of the next major version release. I don't have a great sense as to when that will be (on order of months given my current life schedule) so I understand if you eliminate go-fed as a choice because of that.
It always is! Thanks a lot for giving it thought and documentating the issues :)
This still will require hardcoding the extensions pre-compilation, right? That's fine for most use cases but wouldn't work for a "generic #ActivityPub server" that can support any activities/objects as in: https://social.coop/@mayel/100469525067581562
@mayel (Unless of course it is generic behavior desired: proxy-ing, etc. Then some partial deserialization into an ActivityStreams type could occur, if any deserialization is required at all. Go-fed currently does some form of partial deserialization by preserving unrecognized properties, but it's not exactly the same use case).
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!