R: R: OStatus & SNEW (was R: Federation protocols)

Interesting indeed.
Trying to map it with our current solution based on opensocial, this would mean exposing also that endpoint to other servers (the OS /activitystreams endpoint seems quite similar to your /inbox, and we mandated AS json also). We also mandated support for the targeted audience and the replies extensions.
Webfinger is also referenced and we have some dedicated procedures for doing routing/discovery across telcos based as it is deployed now worldwide for mms as we use both user@domain and phone numbers as reference ids.

Your very last bullet also seems a novelty: can you clarify a bit more what do you use this for?

walter

Da: Evan Prodromou [mailto:evan@e14n.com]
Inviato: giovedì 6 giugno 2013 16.31
A: public-fedsocweb@w3.org
Oggetto: Re: R: OStatus & SNEW (was R: Federation protocols)

Sorry, I didn't answer your last question. It's not directly based on OStatus, but it extracts the good parts and starts from scratch with those. Delta is:

 *   Use Webfinger-based identities only.
 *   Add a simple client API.
 *   Replace PubSubHubbub and Salmon with a single "inbox" endpoint
 *   Use Activity Streams audience targeting for privacy control
 *   Replace Activity Streams Atom with Activity Streams JSON
 *   Use OAuth for authorization
 *   Add dynamic registration of OAuth client IDs with optional dialback authentication

-Evan

On 13-06-06 11:08 AM, Evan Prodromou wrote:
The very last part.

-Evan

On 13-06-06 11:07 AM, Goix Laurent Walter wrote:
Thanks evan, that’s promising.
SNEW actually relies on openSocial (rest/json flavor) for the client api: opensocial leverages AS for activities and poco for user profile representation, and oauth2 for authorization (pump.io seems to reference oauth1, do you plan to update also for opened connect support?)

Could you point me to the specific part of pump.io that addresses specifically federation and what are the changes wrt ostatus?

walter

Da: Evan Prodromou [mailto:evan@e14n.com]
Inviato: giovedì 6 giugno 2013 16.01
A: public-fedsocweb@w3.org<mailto:public-fedsocweb@w3.org>
Oggetto: Re: OStatus & SNEW (was R: Federation protocols)

The pump.io API implements most of the interesting parts of OStatus, and leaves off the parts that don't work.

https://github.com/e14n/pump.io/blob/master/API.md


It also has:

 *   A compatible client API
 *   Straightforward privacy controls
 *   JSON
I think of it as an evolution of OStatus; I think it's probably the best next step.

-Evan

On 13-06-06 10:56 AM, Goix Laurent Walter wrote:

[snip]



This group made a big bet on OStatus about 2-3 years ago, and arguably

it has not exceeded expectations.



True, but:

 - it gained some traction;

 - it has important flaws (privacy-wise) that have been opointed out.



Let's fix it. Let's choose a protocol that does not have these flaws and put

our weight behind it.



i actually would be happy to work with some volunteers to tackle these flaws from OStatus and improve the current SNEW spec from OMA that relies on it for the federation part. We'd also would be interested in some project implementing the spec to do some interop testing (we do have some prototypes already).



You can find the latest updated draft at [1] (see section 7.3 for ostatus-specific reference)



Cheers

Walter



[1] http://member.openmobilealliance.org/ftp/Public_documents/CD/Permanent_documents/OMA-ER-SNeW-V1_0-20130603-D.zip




Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.



This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.