Show Navigation
Notices tagged with ostatus, page 2
-
@taiganaut It is distinct because it is a completely separate project, an #OStatus and #ActivityPub implementation written from scratch.
-
@usbhump Evan P's Status\.Net startup lost its funding. Around the same time, he was trying to get the developers of the underlying protocols that compose #OStatus to agree to make changes to their protocols to enable enhanced privacy. Among the organizations he was trying to motivate was Google, which had recently introduced #GPlus and was no long interested in the open web.
In a hurry to cut costs, he developed the #Pump.io software and protocol to be simpler to develop and cheaper to operate, and to offer some additional privacy built into the protocol. And also to be independent of the progress some of these protocols.
Pump was built with the idea that most federated networks would switch protocols to be compatible. That did not happen. But the hope is that its descendant #ActivityPub will unite the disparate networks.
@gargron Don't oversell AP. If you start to sound like a used car salesperson, people will become suspicious of your motives and the veracity of your claims.
-
@moonman @clacke That was where much of #OStatus came from. I'm not sure blogs ever implemented Salmon, but I remember reading about it: comments posted on one's own site would swim upstream to where the original article was posted.
-
@stitchxd @lohang At one point, #StatusNet was adding support for many such things. For example, blog posts (which were poorly done, but they were implemented in the code). I believe I've heard others discuss possibly implementing federated forums, but cannot recall whether they were going to be a separate site that just interops with #OStatus networks or an add-on to SN/GS.