[evv]

Yes, but HTML+JS+CSS has helped turn HTTP into an application environment, and not the content transport protocol it once was.

REST is popular now, but it's not a real protocol. There's SOAP, but nobody really cares or wants to use it anymore.

The web is undoubtedly missing a social content protocol. I predict one will gain popularity in the next couple of years.

EDIT tldr: Until my blog has an open and commonly accepted way to 'friend' or 'follow' your blog, how can we possibly say that we are "done" with online social protocols?

[Someone]

"There's SOAP, but nobody really cares or wants to use it anymore."

Do you know why? What makes you think we won't end up at

"There's OneAPItoRuleThemAll, but nobody really cares or wants to use it anymore."

or even at

"There's OneAPItoRuleThemAll, but nobody really cares or wants to use it."

If you cannot answer that, I wouldn't bother working on something like this.

Also, who do you think will be interested in having a common protocol? I think the answer will be "those with little data of their own". Big players do not want you to build tools that work together with 'their' data (clear example: Twitter: open while small, but now closing down its API)

[evv]

> Also, who do you think will be interested in having a common protocol? I think the answer will be "those with little data of their own". Big players do not want you to build tools that work together with 'their' data (clear example: Twitter: open while small, but now closing down its API)

This is some scary logic. By that logic, why would great open protocols like HTTP or email have ever gained popularity over proprietary solutions? Do you really think those two protocols are the only perfect and final solutions which will win?

Couldn't you at least try to have a democratic mindset? This is the web, how do you think Twitter ever came to "own" all that data in the first place?

[Someone]

HTML? By having many small players, plus by virtue of the US department of Justice.

E-mail? By having many small players, or at least not one player able to call the shots.

Even today, many parties try to make carve out their own communication kingdoms. Examples: BlackBerry, MS Exchange, Apple's iMessage and FaceTime, GMail (doesn't do push email anymore via Exchange emulation)

And yes, HTTP is open, as is TCP/IP. That, IMO, is because of two things: lower layers get commoditized and network effects. Even disregarding the latter, there is too little money to make in such low-level stuff (that also is why Apple builds on BSD and Google on Linux, and both use OpenGL.)

And that democratic mindset? I tried to make an observation, not to tell you what I thought the world should look like.

[eclipxe]

Hmm. I'm not sure I agree that the web is missing a "social content protocol". What would such a protocol actually do?

REST+HTTP are not without their issues, but I'd argue they've been successful in allowing numerous heterogeneous applications to speak with each other, in a reliable and standard fashion for many years.

Compared to more complicated protocols such as SOAP, COBRA, DCOM, etc...REST+HTTP is as reliable and ubiquitous today because of its simplicity and generic nature. Adding features and utilities for a particular aspect (i.e. "social") would serve to weaken the protocol, not make it better.

The argument that the HTML+JS+CSS side of things has turned HTTP into an application environment is a bad thing is puzzling. Besides, what is the point of a content transport protocol if not to provide valuable services and use cases on top of it? We have TCP and UDP to push bits around...

[evv]

Don't get me wrong, I LOVE how HTML5/JS/CSS is now a full application environment. We desperately needed networked applications, but now we have them. It is a great way of creating an interface for users.

But we still need application protocols to allow our apps to communicate with each other, and protocols for such have withered as of late. There are a few patterns most APIs need to re-implement:

- Authentication for actions on behalf of users (user XYZ, who I represent, says this..)

- Rich content format

- Content posting (send a link to somebody)

- Simple feedback (like/follow/upvote/downvote)

For these common inter-application actions, HTTP+HTML falls short.