Microca.st

Owen Shepherd at 2014-11-05T00:15:56Z

I've just submitted a first draft of my opinion on what a social protocol should look like to the W3C Social Working Group. We are at the stage where WG members bring candiates to the table, we discuss them, work out what we actually want from the protocol specs and then pick a base specification to work from and what we need to do to it to make it suit peoples' needs.

Anyone familiar with pump.io's API should find it reasonably familiar. I'm always open to commentary and critique from all angles, and here I'm basically opening it up to comment from pump client developers

If you are friends with the developers of the other federated social networks (GNU Social, Diaspora, Friendica, etc): Please try and get them involved in the SocialWG. Now is the time when we start to discuss the protocol specifications. 

If they care about us developing a common protocol for the federated social web, this is our best shot at it. 

I know various other members who have connections are reaching out. The more people trying to bring this to their attention, the better.

4slamK , Luis , uıɐɾ ʞ ʇɐɯɐs , James Dearing 🐲 and 12 others like this.

Doug Whitfield , uıɐɾ ʞ ʇɐɯɐs , mray , carl and 6 others shared this.

Show all 9 replies
I think it can just be a user-interface difference.

Evan Prodromou at 2014-11-05T19:15:52Z

There is a huge difference to regular posts with selected receivers and private messages.

The first one are simply regular posts. You post them. And if someone is looking on them, it is fine. if not, it is okay as well. For example: I'm receiving 1,000 to 2,000 messages a day. I cannot see them all.

Private messages are addressed in my inbox. I seem them separated from the other messages. They don't disappear that fast.

You can't do that with simple notifications either. For example: I'm getting about 40 or 50 notifications a day. If I simply got a notification for private messages that were addressed to me, I would get even more notifications and additionally I wouldn't had a chance to find them again, several days in the future.

We need an additional field, where we can separate these posts. Not every system may respect it - but systems who do, should be able to make the separation.

Michael at 2014-11-05T22:57:34Z

Claes Wallin (韋嘉誠) , [email protected] like this.

>> heluecht:

“Private messages are addressed in my inbox. I seem them separated from the other messages. They don't disappear that fast.”


But that already happens in Pump.io. Messages addressed to you (private or not) appear in the "Direct" (inbox/major) timeline, in addition to the "main" timeline, so you can easily find them.

JanKusanagi at 2014-11-06T01:05:46Z

Christopher Allan Webber likes this.

If this process is going to succeed, the W3C standard must be:
  • a superset of most socnets' functionality (that means not every feature will be supported by all socnets)
  • extensible (means socnets can add additional functionality that is not specified in the standard without breaking compatibility)
  • able to accommodate a variety of interaction, security, privacy models; each socnet's model is somewhat different from the others
It is far too early in the process to be inflexible.

[email protected] at 2014-11-07T20:20:44Z