sazius

Why I think pump.io should join the Federation

sazius at

I just wrote a blog post with my thoughts from FSCONS 2014. Summary: I think pump.io should join the Federation: we should build interoperability with GNU Social and Diaspora right now.

JanKusanagi @i, Digital Roffey, gryps75, Adrián Perales and 17 others likes this.

gryps75, Cuenta cancelada. Estoy en https://hubzilla.nl/channel/manuel-jf, Stephen Sekula, ostfriesenmärz and 4 others shared this.

Show all 56 replies

>> heluecht:

“When calling https://hotpump.net/api/user/heluecht/inbox before, there was no comment from you at all. I would have to poll the "proxyURL" from time to time, since there is no notification at all.”

No, you're not supposed to get activities done by people you don't follow (this is a point that needs enhancement, and it's actually addressed, I think, in Owen's 'demo' spec).


But if you query a public post's replies, you'll see every reply, no matter who you follow.

JanKusanagi @i at 2014-11-06T23:04:52Z

Querying replies would mean regular polling of all posts in a specific time frame.

Michael at 2014-11-06T23:14:29Z

@heluecht I agree that is a problem, and one that I've had with Pumpa as well. But @JanKusanagi is right, @Owen's demo spec does indeed propose to solve this problem. I just read it through this morning, and it has the concept of notifications propagating back. It should cause the replies to appear as new actions for everyone that got the original post.

sazius at 2014-11-07T12:39:39Z

while something like a firehose would do what I'm wanting, it's far more centralized and less federated than I would like for this sort of thing. so I was thinking that some sort of peer to peer discovery protocol or mechanism would be able to accomplish what I'm thinking. I was stuck on how nodes/hosts would find each other without some sort of centralized list, but i figured perhaps something like how i imagine discovery to work on decentralized ptp sharing networks. if each host had a list of what nodes it knew about and where the public posts go for said node (either itself or a firehouse node), my host or even client could propagate to me posts out there for public consumption on any federated host/network by bouncing around to all the known nodes a host knows about when it lands there. and a given node could decide to not respond to requests from outside or non-whitelisted nodes if the admin doesn't want to join the public network. this would also help solve the problem of finding people on different nodes or even networks as the search could go through the network and ask each host to search for whatever.

David "Judah's Shadow" Blue at 2014-11-07T14:46:04Z