https://rhiaro.co.uk/2015/04/1430099340
type: Follow
object: aaronpk.com
published: 2015-04-27T01:49:00+0100
tag: esri
tag: indieweb
tag: loqi
tag: micropub
tag: socialwg
tag: w3c

blog-post-content
type: Article
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/584857465499623424/1583811
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/584857465499623424/17069499
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/584857465499623424/2149850018
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/584857465499623424/233185268
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/584857465499623424/25275776
has reply: https://twitter.com/digitalWestie/status/584858305295704064
has reply: https://twitter.com/elfpavlik/status/585113192969465856
has reply: https://twitter.com/LukasRosenstock/status/584995637877465089
has reply: https://twitter.com/rhiaro/status/584994928788426752
has reply: https://twitter.com/rhiaro/status/584995500308504576
has reply: https://twitter.com/rhiaro/status/584995555606147073
actor: me
content: Finally you can get my blog post content in a number of different formats. You'll notice alternative URLs (noted currently as 'Permalink') in the metadata section of a normal view of a post. Hit this up with no Accept header, and you'll get neat markdown (which is what I authored it in; the 'source', as it were). Browsers automatically send Accept: text/html, in which case they are redirected to the rendered HTML version of the post you're probably reading now. But here are some alternatives you can try: curl https://rhiaro.co.uk/llog/micropub-test -> plain markdown. curl -H "Accept: application/json" https://rhiaro.co.uk/llog/micropub-test because there's obviously not enough JSON in the world. Note this isn't correct JSON-LD yet. I'll sort that out another time. curl -H "Accept: text/turtle" https://rhiaro.co.uk/llog/micropub-test Ohemgee! RDF! It's what you've all been waiting for, I know. For those of you who like angular brackets, you could try: curl -H "Accept: rdf/xml" https://rhiaro.co.uk/llog/micropub-test Relevance to micropub Briefly discussed with Tantek, Aaron and Bret at IWC Cambridge and on IRC about how a micropub client could fetch post content for editing. Many people aren't editing raw HTML as it's presented on the page, but maybe markdown or some other syntax, so a client needs to be able to discover this (the 'source') to present it to be edited. Now if someone makes their client check a post for a rel="source" or shoots off a request with Accept: text/plain (less likely, since static sites can't do conneg) then they'll get my markdown directly (uh, when I actually put rel="source" in my HTML, which I haven't yet). As a related aside, I also return source="markdown" if a micropub client asks my endpoint q=source.
name: Blog post content types
published: 2015-04-06T00:11:00+0100
tag: doing
tag: Doing
tag: content+negotiation
tag: hacking
tag: htaccess
tag: indieweb
tag: linked+data
tag: micropub
tag: modrewrite
tag: php
tag: https://rhiaro.co.uk/tags/rdf
tag: slogd
tag: turtle
tag: uris

minimum-viable-micropub
type: Article
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/584703127598850049/15090636
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/584703127598850049/18331731
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/584703127598850049/2235095173
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/584703127598850049/235193328
has reply: https://twitter.com/BillSeitz/status/584914975271051265
has reply: https://twitter.com/jarofgreen/status/584705275254460416
has reply: https://twitter.com/jarofgreen/status/584712878760005632
has reply: https://twitter.com/kevinmarks/status/584828670390312960
has reply: https://twitter.com/mshook/status/584839522212564992
content: "Micropub is an open API standard that is used to create posts on one's own domain using third-party clients. Web apps and native apps (e.g. iPhone, Android) can use Micropub to post short notes, photos, events or other posts to your own site, similar to a Twitter client posting to Twitter.com." (Micropub on Indiewebcamp) This means I can now publish blog posts to my site using other peoples' posting clients, of which there are several. Previously, I was ftping markdown files to my server, then running a slightly unreliable PHP script to process the queue based on when the files were last updated. Which mostly worked, but when it didn't it was a pain to untangle. IndieAuth I wasn't expecting to have a micropub endpoint any time soon because it needs you to be able to sign into your site with IndieAuth. Fortunately, thanks to amazing work of aaronpk and others, most of the legwork has been done here, and you can delegate your IndieAuth; in your site : Micropub Then create a micropub script (eg. micropub.php) and make it discoverable in the same way: Initially I wanted my endpoint at https://rhiaro.co.uk/micropub and set an .htaccess rule to redirect to the PHP script. This doesn't work; POST requests can't follow redirects. Next, here's a bare minimum PHP script to store things posted to your site with a micropub client. This just dumps the POST request to a text file, which is where I started to see if it would work. What I actually do now is turn posts and metadata into triples and insert them into my triplestore, but you probably don't want to hear about that :) <? // Tell client where I can syndicate to if(isset($_GET['q']) && $_GET['q'] == "syndicate-to"){ header('Content-type: application/x-www-form-urlencoded'); echo "syndicate-to[]=twitter.com%2Frhiaro"; exit; } // Check for post if(!empty($_POST)){ $headers = apache_request_headers(); // Check token is valid $token = $headers['Authorization']; $ch = curl_init("https://tokens.indieauth.com/token"); curl_setop…
name: Minimum Viable Micropub
published: 2015-04-05T13:39:00+0100
tag: doing
tag: Doing
tag: hacking
tag: indieweb
tag: micropub
tag: php
tag: slogd

found-micropub-bug
type: Note
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/600306165113815040/1583811
tmpcontent: Found a micropub bug, turned my back for 5 minutes and they'd taken the coffee away and started the next conference session. Indieweb problems.
actor: me
content: Found a micropub bug, turned my back for 5 minutes and they'd taken the coffee away and started the next conference session. Indieweb problems.
latitude: 43.78184
longitude: 11.24936
published: 2015-05-18T15:19:38+0100
summary: Amy wrote about www2015, micropub, & indiewebproblems
tag: indiewebproblems
tag: micropub
tag: www2015

micropubbing-with
type: Article
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/602591522383646720/1111871
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/602591522383646720/1583811
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/602591522383646720/7726162
has reply: https://brid-gy.appspot.com/like/twitter/rhiaro/602591522383646720/961661
has reply: https://twitter.com/CaptSolo/status/605133212252315649
has reply: https://twitter.com/elfpavlik/status/603273389319581698
has reply: https://twitter.com/kevinmarks/status/602605164109762560
tmpcontent: # Micropubbing with json If micropub used JSON instead of (/as well as) form encoding, what might submissions look like? Aaaron Parecki brainstormed about this on our [Social APIs brainstorming doc](https://github.com/w3c-social/Social-APIs-Brainstorming/blob/master/README.md). I'm going to repeat his examples for create/update/delete here, compare them with equivalent AS2.0 json, then explore other post 'types'. Note: I've left out `@context` from all AS examples because we agreed when missing, this is implied to be "https://www.w3.org/ns/activitystreams". ## Create a new post ``` { "object": { "content": "hello world", "category": ["indieweb"], "published": "2015-05-15T13:06:00+02:00", "author": "https://rhiaro.co.uk/about#me" } } ``` No URL is given so it's implied that a new post is being created. Most of this is Aaron's example but I added the explicit published date and author, but these could also be added automatically by the micropub endpoint as the current time and the authenticated user who is sending the request. **ISSUE:** `actor` vs `author` may never get agreed upon. I think `actor` is too abstract and `author` is too specific. I'm a fan of `agent` to mean 'whatever caused this to happen' (be it human, group, process or bot) but I know that's not an easy sell either. I think one side is going to have to suck it up, and I don't know who this is going to be. AS also has `attributedTo` which may be a reasonable compromise but seems a bit clunky. Response per micropub spec: `201 Created` and the URL of the post in the `Location` header. An AS2.0 Activity for creating a new post would look like: ``` { "@type": "Post", "published": "2015-05-15T13:06:00+02:00", "actor": "https://rhiaro.co.uk/about#me", "object": { "content": "hello world", "category": ["indieweb"] } } ``` Response per ActivityPump spec: "This has the side effect that of the object that they are posting is being created." - either I missed something more specific in the spec or this remains t…
updated: 25th May 2015, 00:08 Europe/Berlin
content: If micropub used JSON instead of (/as well as) form encoding, what might submissions look like? Aaaron Parecki brainstormed about this on our Social APIs brainstorming doc. I'm going to repeat his examples for create/update/delete here, compare them with equivalent AS2.0 json, then explore other post 'types'. Note: I've left out @context from all AS examples because we agreed when missing, this is implied to be "https://www.w3.org/ns/activitystreams". Create a new post { "object": { "content": "hello world", "category": ["indieweb"], "published": "2015-05-15T13:06:00+02:00", "author": "https://rhiaro.co.uk/about#me" } } No URL is given so it's implied that a new post is being created. Most of this is Aaron's example but I added the explicit published date and author, but these could also be added automatically by the micropub endpoint as the current time and the authenticated user who is sending the request. ISSUE: actor vs author may never get agreed upon. I think actor is too abstract and author is too specific. I'm a fan of agent to mean 'whatever caused this to happen' (be it human, group, process or bot) but I know that's not an easy sell either. I think one side is going to have to suck it up, and I don't know who this is going to be. AS also has attributedTo which may be a reasonable compromise but seems a bit clunky. Response per micropub spec: 201 Created and the URL of the post in the Location header. An AS2.0 Activity for creating a new post would look like: { "@type": "Post", "published": "2015-05-15T13:06:00+02:00", "actor": "https://rhiaro.co.uk/about#me", "object": { "content": "hello world", "category": ["indieweb"] } } Response per ActivityPump spec: "This has the side effect that of the object that they are posting is being created." - either I missed something more specific in the spec or this remains to be clarified (I'm not criticising, AP is very much under-development!). I prefer the first one. Key differences: Explicit type on the activity (w…
latitude: 43.51198
longitude: 16.43697
name: Micropubbing with json
published: 2015-05-24T22:40:00+0100
tag: doing
tag: Doing
tag: activitystreams
tag: as2
tag: brainstorming
tag: hacking
tag: idea
tag: indieweb
tag: https://rhiaro.co.uk/tags/json
tag: microformats2
tag: micropub
tag: slogd
tag: social+web
tag: socialwg

https://rhiaro.co.uk/2015/12/1451604240
type: Add
actor: me
object: burrow
published: 2015-12-31T23:24:00+0000
summary: Amy added https://apps.rhiaro.co.uk/burrow/ to https://rhiaro.co.uk/bookmarks/
tag: activitypub
tag: activitypump
tag: activitystreams
tag: apps
tag: burrow
tag: checkins
tag: indieweb
tag: micropub
tag: slogd
target: bookmarks

socialwg4-summary
type: Article
tmpcontent: # Social Web WG 4th face-to-face summary *This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG!* See also [day 1 minutes](https://www.w3.org/wiki/Socialwg/2015-12-01-minutes) and [day 2 minutes](https://www.w3.org/wiki/Socialwg/2015-12-02-minutes). What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. ## tl;dr ## * Most AS2 issues are closed! CR-blocking issues are now due by 15th December. * We took a bunch of things to Editor's Draft and are pushing for FPWDs as soon as is viable. * Some of the drafts overlap but there's a general feeling that since there are keen editors we should work on everything and iron out issues and redundancies as we go, rather than holding out and waiting for clarity. * Go check out the specs and build bits of them and give the editors feedback! ## ActivityStreams 2 We steamrollared through AS2 issues, which included core simplifications, vocabulary changes and reductions and editorial clarifications. James made most edits during the meeting, so there's [a much updated working draft](http://jasnell.github.io/w3c-socialwg-activitystreams/activitystreams-core/index.html) available now. You should read it and post any issues you see to be CR-blocking by the 15th of December. JSON-LD related stuff has been moved to its own section; since it is optional, having references sprinkled throughout was confusing for people who don't necessarily want to deal with it. [Chris](https://dustycloud.org) pointed out that even for extensions, if you know the extension you want to handle you can still do that in plain JSON. Still some consternation about which alternative syntax examples should be in the spec. Since they're non-normative/editorial anyway they're not a CR-blocker so left alone for the time being. We don't need a verison number in the URL because any future widely-deployed extensions that want to make it into the cor…
content: This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG! See also day 1 minutes and day 2 minutes. What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. tl;dr Most AS2 issues are closed! CR-blocking issues are now due by 15th December. We took a bunch of things to Editor's Draft and are pushing for FPWDs as soon as is viable. Some of the drafts overlap but there's a general feeling that since there are keen editors we should work on everything and iron out issues and redundancies as we go, rather than holding out and waiting for clarity. Go check out the specs and build bits of them and give the editors feedback! ActivityStreams 2 We steamrollared through AS2 issues, which included core simplifications, vocabulary changes and reductions and editorial clarifications. James made most edits during the meeting, so there's a much updated working draft available now. You should read it and post any issues you see to be CR-blocking by the 15th of December. JSON-LD related stuff has been moved to its own section; since it is optional, having references sprinkled throughout was confusing for people who don't necessarily want to deal with it. Chris pointed out that even for extensions, if you know the extension you want to handle you can still do that in plain JSON. Still some consternation about which alternative syntax examples should be in the spec. Since they're non-normative/editorial anyway they're not a CR-blocker so left alone for the time being. We don't need a verison number in the URL because any future widely-deployed extensions that want to make it into the core will likely be incorporated as part of a full new version (ie. AS3). At some point we should start a registry for extensions; James is keeping track himself on github, we could move this to a wiki page and ultimately a CG when the WG wraps up. Lots of discussion about testing framew…
name: Social Web WG 4th face-to-face summary
published: 2015-12-07T23:59:00+0000
tag: activitypump
tag: activitystreams
tag: as2
tag: federation
tag: indieweb
tag: jf2
tag: meeting
tag: mf2
tag: microformats
tag: micropub
tag: phd
tag: social+protocols
tag: social+web
tag: socialapi
tag: socialwg
tag: standards
tag: w3c
tag: webmention

today-broke
type: Note
content: Today I broke my website completely and fixed it again. Rewrote lots of code in the process. I gained some functionality and lost some functionality. I may have lost more than I gained. Now I can do what I was planning to do tod.. oh. It's tomorrow.
published: 2016-01-02T06:56:58+00:00
summary: Amy wrote about hacking, indieweb, slogd, micropub, activitypub, & activitypump
tag: activitypub
tag: activitypump
tag: hacking
tag: indieweb
tag: micropub
tag: slogd

socialwg5-summary
type: Article
content: This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG! See also day 1 minutes and day 2 minutes. We met in Boston on 16 and 17 March. What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. ActivityStreams2 AS2 is inching closer to CR. Evan has made a validator at as2.rocks and done a lot of work on conformance criteria which we went through as a group and updated a little; mostly changing SHOULDs to MUSTs. Discussed and not necessarily resolved a few new open issues, including: considering dropping the Relationship object and reviving it as an extension if necessary; a proposal for a new property to say when something was deleted; weakening the SHOULD requirement on name; clarifying scope and context. Stay tuned for a new working draft sometime soon. SocialPub The most exciting thing I thought was agreeing on the potential for convergence between the create, update and delete parts of Activitypub and Micropub. Micropub started life as a super small and simple way for clients and servers to agree how to create content on a website by POSTing form encoded parameters to an endpoint. As a result of this simplicity, there are dozens of client and server implementations, allowing people to use each others posting clients to add posts to their site, from simple text-only posts to photos, events, RSVPs, likes, bookmarks, reposts. When Micropub needed update and delete, it grew beyond what form-encoded parameters could sensibly handle, and added in a JSON syntax which I think to date only the editor has implemented. Activitypub uses a JSON syntax (ActivityStreams2) from the outset for create, update and delete, and when you compare this with the Micropub JSON they look remarkably similar. My posting endpoint implements create the AP way, and endpoint discovery the MP way. It also catches Micropub form-encoded requests and translates them to AS2 JSON b…
name: 5th Social WG F2F Summary
published: 2016-03-29T10:43:39+01:00
tag: activitypub
tag: activitystreams
tag: as2
tag: meeting
tag: micropub
tag: phd
tag: social+web+protocols
tag: social+web
tag: socialpub
tag: socialwg
tag: standards
tag: w3c
tag: webmention

socialwg6-summary
type: Article
content: This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG! See also day 1 minutes and day 2 minutes. We met in Portland on 6th and 7th June. What follows is more detail on my perspective of the main conversations we had over the two days. Clarifications and corrections welcome. This doesn't cover everything we talked about in detail; as well as the following, we resolved (or at least discussed) issues on all of the specs, and took a few to new Working Draft status. Demos I demoed my ActivityPub implementations; clients Burrow for checkins, Obtainium for consumption/purchase logging, Replicator for food logging and Seeulator for journeys and events. These all do create only by sending either appropriate activities (including some extensions) to my activitypub endpoint (aka outbox, but not discoverable as such yet). Seeulator creates the right kind of activity based on what attributes are filled in or left blank, essentially doing post-type discovery - albeit my own algorithm rather than tantek's spec from the user input to generate the right as:Activity. The newer thing I worked on was a client that only does updates of existing AS2 data. I wanted this so I could add captions to all my photos at img.amy.gy, so Morph does just that. This also means it has to be able to read/consume the AS2 data published at img.amy.gy about as:Collections of photos. Aaron demoed the Webmention test suite at webmention.rocks and notes that there are Webmention Rocks stickers available for people submitting implementation reports.. Aaron also demoed a new feature in the Micropub spec which is the media endpoint. After some discussion recently it was established that all mainstream social APIs seem to post media (like images) that have been embedded in a post to a separate endpoint, then embed the returned URL in the post content, and MediaGoblin does this too. Aaron's implementation in Quill is really swish looking, uploading the file to the discov…
name: 6th Social WG F2F Summary
published: 2016-06-25T17:39:36+01:00
tag: activitypub
tag: activitystreams
tag: as2
tag: meeting
tag: micropub
tag: phd
tag: posttypediscovery
tag: protocols
tag: social
tag: socialwg
tag: standards
tag: w3c
tag: web
tag: webmention

updated-working
type: Note
content: Updated working draft of Social Web Protocols published ahead of the Social Web WG face-to-face next week: https://www.w3.org/TR/social-web-protocols/ This describes and explains the various specs the WG is working on. Far from done, but we're making progress..
published: 2016-06-03T08:34:57+01:00
summary: Amy wrote about phd, socialwg, resume, cv, solid, social, web, micropub, webmention, decentralised, activitypub, swwg, & protocols
tag: activitypub
tag: cv
tag: decentralised
tag: micropub
tag: phd
tag: protocols
tag: resume
tag: social
tag: socialwg
tag: solid
tag: swwg
tag: web
tag: webmention

published-big
type: Note
content: Published a big update to Social Web Protocols. Read if you want to understand what the W3C Social Web WG is up to.
published: 2016-08-24T14:50:30+01:00
summary: Amy wrote about web, phd, activitypub, socialwg, social, solid, decentralised, micropub, protocols, swwg, & webmention
tag: activitypub
tag: decentralised
tag: micropub
tag: phd
tag: protocols
tag: social
tag: socialwg
tag: solid
tag: swwg
tag: web
tag: webmention

socialweb-demos
type: Article
content: The demos at today's decentralised social web breakout session went suspiciously well. Some things weren't pretty, but everything basically worked, and none of us had done any special coordinating before hand. We just showed the stuff we worked on, and it fit together fairly coherantly. Aaron demoed posting a reply with Micropub and behind-the-scenes Webmention sending. I showed my site feeds and individual posts as ActivityStreams 2.0, plus a screenshot of Chris's emacs-based reader displaying it: Chris... Just live demo'ed ActivityPub client-to-server stuff and server-to-server stuff at TPAC and it worked. Yay for live demos not blowing up! - @dustyweb on twitter demonstrated Pubstrate posting via ActivityPub to his local site, and peer to peer to another. - @t</> on twitter</> Sarven showed LDN, Solid, Web Annotations in dokieli, notifications sent to me displayed in OnScreen, and the LDN spec self-dogfooding with its own annotations on the side. We had some good questions/discussion about abuse prevention, and uptake. Hopefully this energy can be sustained through the next two days of WG meetings!
name: Decentralised Social Web Demos at TPAC2016
published: 2016-09-21T13:12:00+01:00
tag: activitypub
tag: ldn
tag: micropub
tag: social+web
tag: socialwg
tag: tpac2016
tag: w3c
tag: webmention

socialwg7-summary
type: Article
content: This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG! We met in Lisbon, Portugal, during the last two days of the W3C's annual TPAC conference on the 22nd and 23rd of September. See also day 1 minutes and day 2 minutes. tl;dr It's crunch time, but we're on track. We have a selection of specifications which essentially cover creating content and then pinging people about it in various different ways. Many people in the group are using one or more of these specs to power their own personal online social stuff. There are so many more Social Web problems to solve, and we're just trying to dig some foundations and plant some posts in the ground to get everyone else started. Wednesday demos The first time the Social WG gathered last week was for an hour on Wednesday, to demo the products of all of our specs to the broader audience of TPAC attendees. We had a full house. Everything went smoothly, and our demos were fairly coherent. Aaron showed Micropub and Webmention working together in the context of posting a reply to his site (with Micropub), which automatically sent a Webmention to post he was replying to, and after a few seconds his reply showed up there (on the site of someone who isn't a WG member, and had implemented Webmention receiving independently). My site returns ActivityStreams 2.0 for everything when you request application/activity+json or application/ld+json, so I showed collections and individual objects at the commandline. Dumping a blob of JSON on the screen isn't a particularly compelling demo, but Chris was able to furnish me with a screenshot of his AS2 consumer, emacs-based, rendering one of my posts. Maybe you want to make an AS2 reader so you can design your own reading experience for my posts? Chris showed how he is able to create notes on his site using an emacs-based posting client, which prompts his server to send the message on to the inbox of anyone addressed, all using ActivityPub. Sarven showed…
name: 7th Social WG F2F Summary
published: 2016-10-15T18:41:00-07:00
tag: https://rhiaro.co.uk/tags/as2
tag: http://csarven.ca/#i
tag: tantek.com
tag: aaronpk.com
tag: dustycloud.org
tag: activitypub
tag: activitystreams
tag: indieweb
tag: ldn
tag: micropub
tag: post+type+discovery
tag: pubsub
tag: social+web+protocols
tag: socialwg
tag: w3c
tag: webmention
tag: work

socialwg8-summary
type: Article
content: This post is my own opinion, and does not necessarily represent the opinion of the Social Web WG! We met at MIT in Cambridge, MA, on the 17th and 18th of November. See also day 1 minutes and day 2 minutes. tl;dr Everything is progressing. Naming things is hard. We need your implementations please or features may be dropped from some specs. We hope to extend by 6 months, not so we all make more work to do, but just so that the newest spec has time to make it to rec given process timing requirements. We're transitioning any other work into a CG. Community Group The Social Web Incubator Community Group, should be pronounced swi-kig, but by the end of the meeting everyone had taken to calling it swish. I think it was Evan's fault. Anyway it's live, and is where we'll continue to develop on top of the things we started in the WG, as well as think about how to tackle things we haven't got to yet. Aaron and Chris are chairing it, and plan for discussion to take place primarily on github and IRC, with mailing lists for broadcast only. You should join. The spec formally known as PubSubHubbub At the last face-to-face we renamed PubSubHubbub to PubSub. We subsequently realised this is too generic a term for quite a specific spec, and as a result is hard to search the Web for, and hard to find/name libraries and packages for. Renaming it again took the better part of a month. Heh. A few weeks ago we developed a fairly long shortlist on the wiki, listing pros and cons, and a few people voted and left their rationale. On day one of this face-to-face, we ruled out every single one of those suggestions, and came up with three new ones (WebSub, WebFollow and WebSubscribe). We slept on it, and just before lunch of day 2, voted between these three. WebSub won. I like it for its closeness to PubSub; WebFollow is a good name for a user-facing feature that implements the WebSub protocol. Then we proceeded to brainstorm more names in the google doc, progressively making the font smaller a…
generator: sloph
name: 8th Social WG F2F Summary
published: 2016-11-24T20:49:00-05:00
tag: http://csarven.ca/#i
tag: aaronpk.com
tag: dustycloud.org
tag: aaronpk
tag: activitypub
tag: activitystreams
tag: as2
tag: csarven
tag: cwebber
tag: evanpro
tag: julien
tag: ldn
tag: micropub
tag: phd
tag: pubsub
tag: pubsubhubbub
tag: sandro
tag: social+web+protocols
tag: social+web
tag: socialwg
tag: standards
tag: swicg
tag: tantek
tag: w3c
tag: websub

week-in-review-3
type: Article
content: Started running again. Helped with getting WebSub to CR and AS2 and Micropub to PR. Had a couple of days of mini-meltdown thesis-panic low productivity and oversleeping. Did my US federal taxes. Finished integrating Social Web Protocols into a draft of chapter 5. Finished a fairly large overhaul of Social Web Protocols.
name: Week in review: 10 - 16 April
published: 2017-04-16T23:30:00+08:00
tag: activitystreams
tag: micropub
tag: phd
tag: running
tag: social-web-protocols
tag: socialwg
tag: thesis
tag: w3c
tag: websub
tag: week-in-review

micropub
type: Collection
total items: 18

https://rhiaro.co.uk/tags/micropub
type: CollectionPage
items: week-in-review-3
items: socialwg8-summary
items: socialwg7-summary
items: socialweb-demos
items: published-big
items: socialwg6-summary
items: updated-working
items: socialwg5-summary
items: today-broke
items: https://rhiaro.co.uk/2015/12/1451604240
items: socialwg4-summary
items: micropubbing-with
items: found-micropub-bug
items: https://rhiaro.co.uk/2015/04/1430099340
items: blog-post-content
items: minimum-viable-micropub
name: micropub
part of: micropub
prev: https://rhiaro.co.uk/tags/micropub