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