Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Roadmap to V1 #5
This issue is to track the stuff that still needs to get done before the library is ready for use. There are a few categories:
Core ActivityPub implementation
Every activity type that requires special handling needs a
Callers will probably want do ActivityPub stuff without having manually construct a
As discussed in #2, we need to implement an optional WebFinger API to make it easy for callers to participate in WebFinger discovery
The current implementation could thrash the database pretty hard if a bunch of requests come in for the same id in a short amount of time, which is pretty common due to AP's federation model. We should put in a pluggable caching layer over
Integration (end-to-end) testing
Once the rest of the API is complete, I want to write some end-to-end tests that pass in various
Once the above items are done and tested, I would consider the library ready for preliminary use. Longer term, I also want to think about implementing a builder-pattern API for constructing AP activities and objects to make things a little more type-safe and elegant. I don't want a strict type system though, as that would make it more difficult to extend ActivityPub in client applications, so these builders would probably still return arrays that get passed into the existing library functions.
Any thoughts or suggestions are welcome!