12 ms·
ActivityPub: decentralized social networking protocol
- douglaswlance 9y agoThe only way to prevent Facebook and Twitter from strangling Free Speech and manipulating the public is by using an open source protocol. This is true of search as well. We shouldn't allow Google to monopolize the flow of information. They've proven they cannot be trusted.
- freeduck 9y agoELI5 ActivityPub vs xmpp semantics
- eeZah7Ux 9y agoAFAIK XMPP is more geared towards IM than microblogging and it's very complex and difficult to get right due to many extensions.
- JepZ 9y agoActually, I never did any XMPP coding but from what I belief it is more difficult to get it 'complete' then to get it 'right'. I mean you get it 'right' even with a minimal/core implementation but 'complete' only with about the 50 most common extensions. Getting it 'right' seems to be a problem when the XEP definition is open to interpretation. Nevertheless, I agree that it would not fit the XMPP ecosystem to be used as a micro blogging service. It's like using e-mail for IM: Possible, but not recommended.
- jcbrand 9y agoIt's absolutely possible to use XMPP for microblogging, via the PubSub extension, which most servers support. Check out Movim for an example: https://movim.eu/ https://movim.eu/
- ppjet6 9y ago> I never did any XMPP coding but from what I belief it is more difficult to get it 'complete' then to get it 'right'. I don't think there is a point in getting it complete. You choose the XEPs you want by looking at what your client/server goals are. Also if you need help in choosing, there are pointer XEPs, like the Compliance Suites, or the mailing list, or the chatrooms. See https://xmpp.org/community/ https://xmpp.org/community/ > Getting it 'right' seems to be a problem when the XEP definition is open to interpretation. When in doubt, ask the author/council.
- JepZ 9y agoFair enough, 'complete' might be the wrong word here too (as you do not have to support all XEPs), but currently my biggest problem is, that Conversations (Android XMPP client) works pretty good (something I would consider 'complete' in terms of messaging), but I could not find any desktop client which works on a similar feature level. For example how many desktop clients support OMEMO, MAM and Carbon copies? Those are just 3 XEPs all related to secure multi device communication. Yes, they haven't reached the status recommended yet, but I think that is more a symptom than the root of the problem.
- SamWhited 9y agoDesktop client support is lacking, but I think Dino (a relative newcomer) does a pretty good job of being compatible with Conversations and being "modern" (for some handwavey value of "modern") messenger based on XMPP: https://dino.im/ https://dino.im/
- JepZ 9y agoLast time I tried Dino was 4th August, but I can't remember what made me stick with Pidgin. But hey, if Sam Whited suggests Dino I will try it again :-D I love the XMPP and Golang stuff you are doing. And far as I can see it Dino seems to have pretty good XEP collection nowadays: https://github.com/dino/dino/wiki/Supported-XEPs https://github.com/dino/dino/wiki/Supported-XEPs
- goffi 9y agoThat's not true. XMPP can do far more than instant messaging, and it's definitely not complicated (well for a decentralized network and for technical audience of course). For the record I'm the main developer of a XMPP based "social network" project (Salut à Toi), and we are able to communicate natively with others XMPP projects (e.g. Movim) for years (we can share comments like in the video, it's the basis of common standard). The "many extensions" thing is commonly misunderstood by non XMPP people thinking that it's making software more complicated or hard to maintain. But it's not true: extensions is a strength of XMPP allowing to concentrate on one feature at a time, evolve it, change it if needed, and there is a very good negotiation mechanism. Software are evolving, and it's normal that different clients/servers have different feature, but even with that they can still communicate together. The case is common actually: the websites on your browser can test for implemented features in javascript for instance before activating this or that. XMPP is not a single technology but a base to support many coherent technologies, for many different use cases. To go back to this ActivityPub, while I'm a bit annoyed that nobody tried to contact us to join our efforts on XMPP, resulting in yet another standard, at least if it's followed by some platforms, it may simplify the creation of gateways. I've looked at the specs, I don't think that putting "like", and "followers" as the main feature of a social network is a good idea. At first sight, it doesn't seem too difficult to translate to XMPP.
- mindB 9y agoThe problem I've always had with XMPP is that any time I try to do something with it, I get lost in an endless sea of RFCs with no idea of which are important for my use-case (most RFC titles seem fairly jargon-heavy to me). Then, when I go to read an actual RFC, because of the fact that each RFC has some interactions with all other RFCs, they're fairly impenetrable. Is there a document somewhere collecting the most essential XMPP stuff you need to be aware for different applications (e.g. chat client, XMPP server, XMPP social network client, bridge between XMPP and other protocols, etc.) and presenting it in a concise way that doesn't require navigating a vast sea of documents? Do you have some other recommendation for how to get into the XMPP world?
- goffi 9y ago
- jelv 9y agoPeerTube with Mastodon comments. Powered by ActivityPub. https://peertube.cpy.re/videos/watch/da2b08d4-a242-4170-b32a-4ec8cbdca701 https://peertube.cpy.re/videos/watch/da2b08d4-a242-4170-b32a...
- NetOpWibby 9y agoComments are disabled.
- kemenaran 9y agoThis protocol is a successor to OStatus (GNU Social), and mostly made by the same people. From what I remember, Mastodon switched from OStatus to ActivityPub a few releases ago. In the past they had to extend the OStatus protocol for private messages, which meant some clients may not honor the private status of theses posts. ActivityPub has private messages defined properly in the spec. It seems PeerTube (https://github.com/Chocobozzz/PeerTube https://github.com/Chocobozzz/PeerTube) will also use ActivityPub.
- carussell 9y agoLast summer I tried untangling the OStatus/pump.io/ActivityPub/ActivityStreams nest hoping to piece together a big picture mental image based mostly on what Wikipedia has to say, and found it mostly frustrating. For anyone who's similarly curious or confused, LWN published a pretty great overview last month—their "Federation in social networks" article: https://lwn.net/Articles/741218/ https://lwn.net/Articles/741218/
- coldacid 9y agoThanks for this. I was grinding my wheels much the same way, so hopefully this LWN article will clear things up for me.
- Xeoncross 9y agoThanks! After reading that article I'm curious where public key cryptography fits into this.
- rogerbraun 9y agoIn AP, messages are signed with http signatures (https://tools.ietf.org/html/draft-cavage-http-signatures-09 https://tools.ietf.org/html/draft-cavage-http-signatures-09). OStatus has a similar mechanism called salmons, which are signed XML payloads.
- Xeoncross 9y ago
- amelius 9y agoImho, any such document should start with a requirements-analysis. It's difficult to tell what requirements they have considered, and what they have forgotten without reading (and re-reading) the entire spec.
- jeswin 9y agoFrom my quick read of the spec, server-to-server federation assumes that servers can be trusted. That need not be the case; unless a message is signed it should not be assumed to have come from a specific user. I don't know if there's an easy way to share keys in a decentralized way, but that'd be an interesting problem to solve (some blockchain maybe). The other question is whether we want server-to-server federation at all instead of a P2P network like bittorrent. With the decreasing cost of compute, I am also optimistic of everyone being able to run a little sandbox on the cloud to exchange data with others, instead of routing it via FB/Twitter.
- Ajedi32 9y agoSeems to me that they _did_ consider those concerns to some extent, but the specification doesn't really address them: > Unfortunately at the time of standardization, there are no strongly agreed upon mechanisms for authentication. Some possible directions for authentication are laid out in the Social Web Community Group Authentication and Authorization best practices report. https://www.w3.org/TR/activitypub/#authorization https://www.w3.org/TR/activitypub/#authorization
- detaro 9y agoThat need not to be the case, but realistically it is the case for Mastodon & co for now. People are looking into various signature schemes, potentially as extensions of the protocol, but it would have moved the entire thing into very untested waters, which is bad for a new standard. Same with federation: It's what you need right now for "normal" users (e.g. compare user numbers of Mastodon etc to purely p2p alternatives). While I personally self-host a lot of stuff and would be willing to run a Mastodon instance for friends and family, I can't expect or even recommend they run something themselves individually. Thanks to federation, nothing is stopping those that can to run their own single-user software speaking the protocol, or for instances to only serve very small groups.
- jeswin 9y agoAs a counter example, there are millions of non-technical users using the bittorrent protocol. They are running a server on their machines and not aware of the technical complexity that lies underneath. I am not saying it's an easy UX problem to solve, but it can be done.
- yellowsir 9y agohow can anything be verifyed?
- NoGravitas 9y agoYou put a green checkmark emoji at the end of your display name. There, you're verified.
- epeus 9y agoBy using distributed verification with rel=me links in both directions: http://www.kevinmarks.com/distributed-verify.html http://www.kevinmarks.com/distributed-verify.html
- daveid 9y agoWith cryptography.
- yellowsir 9y agohow? in the example the data is not signed, what is stopping a other server from changing the content i posted?
- Shoothe 9y agoThe real world example as used by Mastodon uses signing to protect content but the process is kind of complicated (normalization of json to RDF triples etc.)
- daveid 9y agoThe exact methods of authentication are simply "out of scope" for the ActivityPub standard itself. As far as I understand simply for bureaucratic reasons. In reality there's already agreed upon mechanisms for doing this. Each actor has an RSA keypair. Server-to-server requests are authenticated using HTTP signatures (that's a different spec), so you know a delivery is legit and on behalf of which actor it is. For messages that are passed directly between origin and destination there is no reason to believe the sender has tampered with the message (SSL is a prerequisite anyway). For messages that are about other messages, such as reblogs, you would not trust the sender, you would look up the message by its ID on its origin server instead. This is always possible because ActivityPub prescribes IDs to be resolveable URIs. There's also another method to verify the authenticity of a passed message, called Linked-Data Signatures (that's a different spec). It's a way of signing JSON inside JSON, it's a bit of a bother to implement though (To make sure the signature works regardless of how the payload is re-formatted or re-ordered in transit, the JSON is "canonicalized" using RDF)
- simula67 9y agoSimilar earlier attempt by Google : https://en.wikipedia.org/wiki/OpenSocial https://en.wikipedia.org/wiki/OpenSocial
- EGreg 9y agoI have been in touch with Tim Berners-Lee and his Solid project since late 2016. Since then, I've run across many people who work at W3C and in the protocol space, and it's inspired me to open up and publish protocols derived from our platform (eg https://github.com/Qbix/auth https://github.com/Qbix/auth) But I believe that, in the end of the day, mass adoption can only be done when there is a popular platform. Whether it's closed source like Facebook or Twitter, or open source like Qbix, it needs to be actually used. That's how, for instance, oAuth came to be so widely adopted, and many others. Here is an overview of what I mean: https://vimeo.com/252105786 https://vimeo.com/252105786 Protocols like Scuttlebutt or ActivityPub can be bolted on after the actual infrastructure is there.
- deleted 9y ago[deleted]
- davexunit 9y agoMastodon is used by a million people across a lot of instances and supported ActivityPub before it was a W3C recommendation, so I'd say it is definitely being used.
- cookiecaper 9y agoAdoption and low friction is the most important thing. Unfortunately, copyright makes it illegal to parse web pages without the parent entity's consent, and the CFAA makes it illegal to download them. This means that a low-friction mechanism to break the corporate stranglehold on communication is extremely unlikely, since it can't do much to ease transition between providers. If we didn't have these restrictions, this would be a purely academic debate, because there are already many practical ways to extract information from a resource and transmit it to other computers. "Federation protocols" are a way of volunteering this information in a common language, but there's no real technical reason that's necessary to get "decentralized social media" or other such things. They're only considered potential solutions because effective scraping is not allowed. Decentralized / democratized information access is not an issue that can be solved technically. It needs to be solved socially (primarily because the necessary technical infrastructure already exists, and is just held back by legal anti-solutions).
- eximius 9y agoMisread as 'Decentralized Pub', am sad I was wrong. (although, that now just sounds like 'drinking alone')
- ytjohn 9y agoYou should check out Scuttlebutt https://staltz.com/an-off-grid-social-network.html https://staltz.com/an-off-grid-social-network.html https://www.scuttlebutt.nz/getting-started.html https://www.scuttlebutt.nz/getting-started.html https://scuttlebot.io/docs/basics/install-the-database.html https://scuttlebot.io/docs/basics/install-the-database.html
- snissn 9y agoCan I build a blockchain on top of it?
- jlarky2012 9y agomy thought exactly! At least add work of proof to fight with spam :)
- jordigh 9y agoThe FSF announcement about it: https://www.fsf.org/blogs/community/victory-for-libre-networks-activitypub-is-now-a-w3c-recommended-standard https://www.fsf.org/blogs/community/victory-for-libre-networ... Look in particular at that cool video in it. Someone posts a video to Peertube, which gets federated to Mastodon. People comment on Mastodon and the comment gets federated back into Peertube. People reply on Peertube, and the comment goes back to Mastodon. Kinda nifty: https://peertube.cpy.re/videos/watch/da2b08d4-a242-4170-b32a-4ec8cbdca701 https://peertube.cpy.re/videos/watch/da2b08d4-a242-4170-b32a... Btw, I have been greatly enjoying Mastodon. I'm @JordiGH@mathstodon.xyz in case anyone feels like chatting to me there.
- cuckcuckspruce 9y agoAll of these social networking protocols feel like we're just re-inventing UUCP at a higher level.
- NoGravitas 9y agoI've considered that, as well. I enjoy Mastodon, and am working on another ActivityPub project. But in a lot of ways it's not a significant advantage over Usenet.
- cuckcuckspruce 9y agoMail over UUCP and Usenet over UUCP are optimized for short(-ish) messages, and deal with packet loss, dynamic IP addresses on remote connections, partial transfers, and synchronization scheduling as part of their implementation. It would seem to be a good base to build something like ActivityPub on top of.
- omarforgotpwd 9y agoYeah, let's send my social media data to a bunch of servers automatically through a distributed protocol with no practical means to enforce compliance with privacy settings. But that's okay, nobody ever posts anything on social media that they end up regretting, right?
- Kequc 9y agoI'm reasonably secure in my feeling that centralisation isn't the problem. As much as people far too freely giving up information about themselves online. Decentralisation can work as an anti-censorship measure but I wouldn't expect something I send out over Bittorrent (for example) to remain my personal private info.
- Shoothe 9y agoActivityPub is like JWT. Simple on the outside but complex inside. For example I wanted to implement a simple server to connect to Mastodon. JSON via HTTP, what could be simpler? Actually it's JSON-LD not JSON. But it doesn't matter as JSON-LD is JSON, right? No, as the standard requires normalizing JSON-LD for purposes of signing that includes all of RDF canonicalization, of course the standard do not require it [0] but it's akin to unencrypted HTTP2, theoretically it exists but practically doesn't. What's interesting is that ActivityPub requires signing the data twice, first on a HTTP request level, then the JSON-LD itself. It seems like the designers tried to make it simple (let's use JSON-LD and HTTP) but after several edge cases the standard got out of control. [0]: "Linked Data Notifications also supports a number of RDF serializations which are not required for ActivityPub implementations. However, ActivityPub implementations which wish to be more broadly compatible with Linked Data Notifications implementations may wish to support other RDF representations." source: https://www.w3.org/TR/activitypub/ https://www.w3.org/TR/activitypub/
- daveid 9y agoHTTP signatures and LD-signatures serve different purposes. HTTP sigs authenticate server-to-server requests, while LD-signatures allow to forward verified messages in the network. The forwarding part is a good extra for UX purposes but it's not necessary for your implementation, you can just stick to HTTP sigs which are really simple. I agree that LD-signatures are very complicated to implement. If you avoid LD-signatures then you don't have to mess with JSON-LD canonicalization either, you can just treat the JSON as simple JSON (though it's still a bit fiddly because a value can often be either a URI string, an array of URI strings, an object, or an array of objects).
- Shoothe 9y agoI know what the signatures are for but I wonder if there's a simpler way to achieve these objectives. Server authentication: For example XMPP uses client certificates to authenticate servers to other servers (TLS server certificates usually can be used for client authentication too). Message authentication: maybe exchanging OpenPGP messages would be easier? They already are signed and the payload can be anything. Of course it's not as easy to list a collection of these messages as it is with JSON (just collect into an array). > If you avoid LD-signatures then you don't have to mess with JSON-LD canonicalization either, I want to be interoperable with existing software so avoiding it is not a practical option (although allowed by the ActivityPub spec). Just like having non encrypted HTTP2 is not a practical option (although allowed in the spec).
- rocky1138 9y agoDoes GNU Social support this? AFAIK ActivityPub is a successor to OStatus.
- Torgo 9y agoNo.
- hateful 9y agoMy only question is: Is this a Twitter or Facebook replacement? Because if it's only about someone status and you can't post something on someone's wall/timeline, then it will never truly complete with Facebook. It was the only thing missing from Google+ IMO.
- adamnemecek 9y agoIt would be a federated network. You can think of it as email.
- ytjohn 9y agoIt's much closer to Twitter but with federation, so different organizations can run their own servers, like with email.
- NoGravitas 9y agoIt actually contains sufficient primitives to implement either. Mastodon uses it in a Twitter like way, but there are projects being worked on that are more similar to Facebook.
- marknadal 9y agoWe need P2P not federated. Federated still requires trusting a server which is not good. We've tackled this problem and produced an insanely simple API for creating fully P2P apps, even the cliche Twitter/todo app can be built in 4min: https://scrimba.com/c/c2gBgt4 https://scrimba.com/c/c2gBgt4
- Xeoncross 9y agoDoes anyone have a reference to all the expected/discussed use-cases? https://github.com/jasnell/activitystrea.ms/blob/master/README.md#usage https://github.com/jasnell/activitystrea.ms/blob/master/READ... shows a number of activity types.
- Xeoncross 9y agoFound the https://www.w3.org/TR/activitystreams-vocabulary/ https://www.w3.org/TR/activitystreams-vocabulary/ and the older https://www.w3.org/wiki/Activity_Streams/Examples https://www.w3.org/wiki/Activity_Streams/Examples
- gizmogwai 9y agoIs it just me or does this recommendation reads more like a medium blog post from some developer advocate than like a formal specification ?
- grizzles 9y agoThe thought process behind ActivityPub seems fanciful to me. To paraphrase: Here is a spec for something no one currently uses, please take a risk and invest your time to understand ActivityPub, build an impl of ActivityPub, and then build your thing on top of it. Then, if many others also do this, it might have a chance at success. Heed the lesson of OStatus. Open source has killed RFC style development. If the backers of ActivityPub genuinely want people to use it then they should publish a reference grpc microservice porcelain on docker so people can use it from any language, without thinking about it. Otherwise the cost to implement ActivityPub is just too high.
- adamnemecek 9y agoIt really hasn’t. RFC is a part of all web standards and even some open source like Rust and React. RFCs are a sign of maturity of open source projects.
- gargron 9y agoDid you miss the part where a million people use ActivityPub via Mastodon? There are already numerous implementations, such as Mastodon, Hubzilla, Pleroma, PeerTube, Kroeg, and more.
- grizzles 9y agoPerhaps I should have said "that no one uses directly". I tried out Mastodon but didn't become a regular user. So I'm just curious, are you claiming a million monthly active users or a million accounts created since inception? A million a month is roughly what serverfault.com gets. If you have 1MAU/month, that's a nice achievement, though it's still 1/130th the market share of twitter. I hope Mastodon keeps growing to level out the playing field. That's why I suggested a way to make it easier for other sw engineers to support it.
- treve 9y agoBy that logic no one uses email directly either.
- 9y ago
- OriPekelman 9y agoand it only took 10 years to come up with the spec ! https://www.w3.org/2008/09/msnws/report.html https://www.w3.org/2008/09/msnws/report.html
- m3kw9 9y agoDoes anyone know if say you have Facebook level of activity, wouldn’t the block chain be in the orders of petabytes to download? I’m sure you may want to know your history all the way back, or does the protocol is smart to know how much you need to download?
- NoGravitas 9y agoActivityPub does not use a blockchain. SSB uses an append-only log similar to a blockchain, but it only contains things your identity knows about (you and your friends and channels).
- stevedekorte 9y agoFederated is not decentralized. If you feel this is a small point, please consider the centralization which has happened with email, jabber, and other federated systems.
- dpc_pw 9y agoAnything web-based is a dead end at this point. There is many, many reasons why any web-based solution will degenerate into centralized system. People behind Urbit got it right. I don't know if Urbit is going to succeed, but the they have pointed out the issue brilliantly.
- maufl 9y agoReminds me of my own attempt to design a decentralized networking protocol FOSP (https://github.com/maufl/fosp-specification https://github.com/maufl/fosp-specification). I now think that a peer to peer solution would be more user friendly, it's sometimes difficult to explain to some of my peers that there can be a difference between an app and an service.
- ivanceras 9y agoI'm looking for the specs of the message format used, but couldn't find it. Is it gonna be like email message format? html perhaps?