GoActivityPub: the talk
-
Who are we:
- Library to make ActivityPub Go development easier
- Started as a link aggregator in Go
- Moved to ActivityPub backend/frontend microservices
- Extracted ActivityPub logic to a library
-
Moving parts:
- Vocabulary
- Custom HTTP client implementation
- State machine
- Custom storage backends
-
Where we are:
- Good documentation
- Idiomatic
- Close to tagging the v1 of the library
-
How we got here:
- Dogfooding
- Building both server and client applications
- Believing in the feasibility of client to server applications
- Almost ten years of iterating over the API
- It’s finally good
-
Where we’re heading:
- JSON-LD is not just an afterthought
- Code generation vocabulary types
- Compile time vocabulary
-
Thank yous:
- NLNet
- Andy
- Elle from Weathered Steel, and the Forgejo community