Hacker News new | comments | show | ask | jobs | submit login

Yes, this could work. I like the idea of streams being an url with a path that might be a unique hash for you. The url's domain controller decides who is authorized to post on their streams. You decide which domains to trust.

Most social services we use today could be streams. Facebook, Twitter, even WhatApp, Instagram (I guess not snapchat). If they'd all implement some common stream spec. Unfortunately they won't, Twitter has demonstrated that they don't like alternative client implementations.

If it could replace e-mail is another big question. Nikita hilights the amount of cruft that's around e-mails, but the cruft is social protocol, and we humans love social protocol. Or perhaps that's just old fashion speaking.

The posting is quite old already (Oct 2014), so this isn't some big hype building and it doesn't look like anyone is working on a big implementation.

When you read the post, you know that XMPP has all the technical parts to fill the role here. There are some people who build things on top of XMPP, but I haven't seen something as advanced as buddycloud (http://buddycloud.com/) here. They have a concept of "channels" (https://xmpp.org/extensions/inbox/buddycloud-channels.html) which can have multiple types with multiple participants, each having a definite role. All of the use cases in the article are (theoretically) possible with buddycloud.

Technically, the standard XMPP PubSub protocol with its PEP companion could get you very far already, unfortunately there's not many clients that handle them today.

jitsi does. who uses anything else for xmpp nowadays?

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact