- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Thu, 11 Oct 2012 19:54:06 +0200
- To: Sandeep Shetty <sandeep.shetty@gmail.com>
- Cc: Henry Story <henry.story@bblfish.net>, public-rww@w3.org
- Message-ID: <CAKaEYhKiRd=OXzPL57ekJvFiVnxyJwVKuQY6tiJL6F4512fGSQ@mail.gmail.com>
On 1 October 2012 21:22, Sandeep Shetty <sandeep.shetty@gmail.com> wrote: > Hey Henry, > > > How does it compare in your view to the pingback protocol we detailed > > here? > > > > http://bblfish.net/tmp/2011/05/09/ > > RESTful Pings is well thought out, espcially the HTML form and > webID/Oauth based authentication bits > (http://www.w3.org/community/rww/wiki/File:Client-Side_Pingback.png). > > One of my main goals with Activity Pingback, is developer experience > (DX) and keeping things as simple as possible (for implementors) with > a minimum surface area of concepts and options while being ready to be > implemented/deployed as of yesterday. Activity Pingback also tries to > retain familiarity with Pingback/Trackback for existing developers. > > The larger project that I'm working on (http://activityweb.org/) > borrows heavily from blogging and doesn't treat things like users in a > special way. Any URI addressable resource can be "followed" and > notified of activities related to it. Within that context, Activity > Pingback is singularly focused on sending activity related > notifications (in the form of JSON Activity Streams) to any URI > addressable resource with a good enough way to verify that the > notification originated from the said resource. > I might be quite interested to try out the "like" use case from any URI to any URI. I know that facebook and google have a like button that is used in many sites, does anyone have a button that we could use to test out the general case? > > -- > Sandeep Shetty > Founder, Simpthings > http://simpthings.com/ > http://sandeep.shetty.in/p/about.html > >
Received on Thursday, 11 October 2012 17:54:34 UTC