@forgefed Hi ForgeFed team!
A few folks and I are also getting our hands into this field, and we realized we should not do repetitive work in parellel, especially not *two* specs or protocols. I'm really curious about your work, and how you got ActivityPub, a social network-oriented protocol, to suit your needs.
@fakefred Hi Fred! I'm happy to hear about new effort and motivated people working on decentralizing project hosting :) Like @cj said, AS2 allows extensions, it's just a vocabulary in JSON-LD format, allowing any RDF data to be expressed. But we do try to reuse standard ActivityPub properties and only add custom ones as necessary. Here's an example of what it may look like: https://forge.angeley.es/s/fr33/p/sandbox/t/11?prettyjson=true
The spec is still evolving, but if you look at the spec in the git repo, and the issues, and the forum (links in @forgefed profile), you can get an idea of what's going on. I'd love to collaborate! Come to #peers channel on Freenode and/or the forum :) and I'd love to join wherever you/team is, if I'm invited ;)
@fr33domlover I'm reading through ForgeFed's specs, and wondering if this all is too much work for any FOSS git platform, and how you decided to make repos Actors. 🤔
@fakefred it's the same amount of work as for any federated web app, the actor model stuff and its implementation isn't specific to forges. The difference is the activity and objects types having forge specific details :)
As to why repos are actors, and more generally which things should be actors and which not, after discussions I came up with the following guideline: https://dev.angeley.es/s/fr33domlover/r/vervis/s/FEDERATION.md#actors
Btw the page I linked has more spec related stuff, I document stuff there when it's not ready for the spec but already implemented experimentally in Vervis. Take a brief look to get an idea how some stuff is going to work :)
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! We adhere to an adapted version of the TootCat Code of Conduct and have documented a list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!