How does one read a protocol specification and write an implementation from scratch?
I'd love to see a Ruby #ActivityPub gem, but I have a very limited understanding of how to build one myself.
I guess part of this depends on just knowing where to start?
Like, creating a gem, mounting it in a Rails app, and then getting that app to leverage the gem for federation calls doesn't seem like a crazy hard amount of work.
The real question involves which parts to build out first. I guess the inbox / outbox? Predefined ActivityStreams objects? Creating a status and rendering it in a stream?
The other tricky bit involves adapting it to an existing system, like, uh, Diaspora.
@deadsuperhero hmm, step one is making a plan and working out the rough flow on 'paper' :)
@webmind Yeah, I think this makes the most sense. If I can untangle the abstractions and understand how the objects are supposed to connect to each other, I guess that's a step in the right direction. :)
It seems like the bulk of communication happens through a user's inbox/outbox? If so, that's probably a big clue about how things should be put together.
