X-Git-Url: https://git.mxchange.org/?a=blobdiff_plain;f=doc%2Fopenmicroblogging.txt;h=a0df04035e6c82a873192ef846bc1ca51750e772;hb=9c29b9ad629b573b6f09b681a0673805fc61ef6a;hp=77c52a10fedf99b29fae4d12a9e84d277ff8379f;hpb=eecd611f678febabe1d62d5cf9b0bc152caf7596;p=quix0rs-gnu-social.git diff --git a/doc/openmicroblogging.txt b/doc/openmicroblogging.txt index 77c52a10fe..a0df04035e 100644 --- a/doc/openmicroblogging.txt +++ b/doc/openmicroblogging.txt @@ -2,7 +2,14 @@ OpenMicroBlogging specification =============================== -Version 0.1 +:Author: Evan Prodromou (Control Yourself, Inc.) +:Contact: evan@controlezvous.ca +:Revision: 0.1.1 +:Date: 2008-07-07 +:Copyright: To the extent possible under law, Control Yourself, Inc + has waived all copyright, moral rights, database rights, + and any other rights that might be asserted over + The OpenMicroBlogging specification. Purpose ======= @@ -13,7 +20,7 @@ users of another service, given the other users' permission. Enabling technologies ===================== -Depends on OAuth 1.0, YADIS 1.0. +Depends on OAuth 1.0, OAuth Discovery 1.0, YADIS 1.0. We piggy-back additional information onto these protocols to pass microblogging information back and forth. @@ -33,9 +40,9 @@ listener listenee the user sending notices. remote service - the listenee's service. + the listenee's microblogging service. local service - the listener's service. + the listener's microblogging service. profile URL "home" URL for the listener, typically their profile page on a microblogging site. @@ -60,25 +67,26 @@ notice URI Initiation ========== -The user submits their profile URL to the remote service somehow -- +The user submits their profile URL [*]_ to the remote service somehow -- for example, with an HTML form on the remote service's Web site. +.. [*] For OAuth Discovery, this is the "protected resource". It may + be more correct that the protected resource is the postNotice URL + (see below), but the listener will be more familiar with their own + profile URL. So there will have to be discovery of the postNotice + URL anyways, and it might as well all be done in one step. + Discovery ========= The remote service recovers a YADIS document from the profile URL, as -described in YADIS 1.0. +described in OAuth Discovery. -The remote service looks for the URIs of Service of these types: +The request token service must have a LocalID associated with it, +containing the identifier URI for the listener. -http://openmicroblogging.org/protocol/0.1/requestToken - Request Token URL, as in OAuth 1.0 - -http://openmicroblogging.org/protocol/0.1/userAuthorization - User Authorization URL, as in OAuth 1.0 - -http://openmicroblogging.org/protocol/0.1/accessToken - Access Token URL, as in OAuth 1.0 +The following two extra services must be included in the YADIS +document, with accompanying URIs. http://openmicroblogging.org/protocol/0.1/postNotice Post Notice URL, as defined below. @@ -86,9 +94,6 @@ http://openmicroblogging.org/protocol/0.1/postNotice http://openmicroblogging.org/protocol/0.1/updateProfile Update Profile URL, as defined below. -http://openmicroblogging.org/protocol/0.1/identifier - identifier URI for the user with this profile URL. - If any of the URIs is unavailable, the remote service MUST stop processing. @@ -98,11 +103,12 @@ Authorization The remote service must go through the OAuth 1.0 dance to get authorization to post notices and update profiles. -In all OAuth, the consumer key should be blank (''), unless the remote -server and local service have negotiated another key. Such negotiation -is out-of-scope for this document, and we assume an "open" network of -microblogging services. But if you want to have that kind of network, -do it with this key. +In all OAuth, the consumer key should be the root URL for the +microblogging service, if available. The secret should be the blank +string (''), unless the remote server and local service have negotiated +another key. Such negotiation is out-of-scope for this document, and we +assume an "open" network of microblogging services. But if you want to +have that kind of network, do it with this key. The remote service MUST do OAuth for every new listener, regardless of whether they've already received authorization for posting to the @@ -202,6 +208,12 @@ omb_listener_avatar This will allow the remote service to display information about the listener in the listenee's "listeners" or "subscribers" list. +Access token +------------ + +The access token step of the OAuth protocol requires no additional +parameters. + Posting a Notice ================ @@ -249,17 +261,17 @@ The local service makes no guarantees about the delivery of the notice to anyone. The remote service SHOULD NOT send a message with the same notice URL -to the same postNotice URL more than once. [2]_ If the request returns +to the same postNotice URL more than once. [*]_ If the request returns a 403 Unauthorized message, the remote service SHOULD NOT post messages to the same URL again with the same listenee, until another -listener has gone through the OAuth dance. [3]_ +listener has gone through the OAuth dance. [*]_ -.. [2] A half-assed optimization. A local service may have a lot of +.. [*] A half-assed optimization. A local service may have a lot of listeners listening to the same listenee. It would be pointless to have the remote service post the same notice 100 times to the same service. However, if the local service wants fine-grained control, it can have a different postNotice URL for each listener. -.. [3] If there's one postNotice URL per listener, the 403 message +.. [*] If there's one postNotice URL per listener, the 403 message means the listener has told the local service not to allow posting any more ("unsubscribed"). If there's one postNotice URL per local service, it means that the count of listeners has dropped to 0. @@ -289,18 +301,25 @@ omb_listenee_license The default license URL for the listenee's stream. A change in the default license only applies to future notices; notices previous to the update SHOULD be treated as under the old license. -omb_listener_fullname - The full name of the listener. Up to 255 chars. -omb_listener_homepage - The home page of the listener. -omb_listener_bio - A brief biography of the listener; less than 140 chars. -omb_listener_location - Physical location of the listener; less that 255 chars. -omb_listener_avatar +omb_listenee_fullname + The full name of the listenee. Up to 255 chars. +omb_listenee_homepage + The home page of the listenee. +omb_listenee_bio + A brief biography of the listenee; less than 140 chars. +omb_listenee_location + Physical location of the listenee; less that 255 chars. +omb_listenee_avatar URL of a 96px by 96px image in PNG, GIF or JPEG format representing - the listener. + the listenee. Missing parameters should not be construed to mean that the profile field has been blanked. The remote service MUST set the parameter to an empty string to show that the field is blank. + +References +========== + +* OAuth: http://oauth.net/ +* OAuth Discovery: http://oauth.net/discovery/1.0 +* XRDS Simple: http://xrds-simple.net/core/1.0/ \ No newline at end of file