Here's a sneak peek at the architecture for how the #ActivityPub integration in #DistributedPress is going to work!
tl;dr:
- Publish static JSON+HTML for your posts/AP identity (on #IPFS and other #p2p protocols)
- In your AP JSON link to our inbox server
- AP servers use an HTTP gateway to load your AP data
- Users can send replies to your inbox server
- Inbox server has a moderation queue to put follower data and replies back into your site via static files / webhooks
Longer term I want to remove the need for the HTTP gateway and the AP server from the equation and have users talk directly to each other.
Even longer term it'd be good to remove the need for an inbox server and do something fully p2p.
Then we could focus on pure #ActivityStreams and #RDF data on the client side. (once we figure out indexing to make this stuff actually fast)
@mauve
That would be so cool.
How do you imagine dealing with the absence of an constantly online trusted node? I'm having a hard time imagining it without some serious tradeoffs.
Take replies to posts. Without an online trusted node, the reply could simply wait, which breaks some expectations at least, or gossip them, which eliminates a lot of moderation possibilities.
But I'm in no way knowledgeable about p2p protocols. Am I missing something?