Ja het voelt magisch aan, als ‘t ‘just works’. Zelf experimenteer ik met de WP-plugin Yarns ipv Aperture. Aperture staat (en dus ook je feeds) op de server van Aaron. Yarns op mijn eigen server. Met Monocle lees ik dan de feeds zoals jij ook beschrijft, Frank.

Yarns microsub plugin in WordPress

Frank’s posting lezen in Monocle

Mijn ideaal is dat gehele gedistribueerde conversaties goed te volgen zijn. Maar dat vergt nog iets meer dan alleen de like, report en reply buttons zoals nu in Monocle. Al is het al enorm vet dat je op die manieren rechtstreeks vanuit je feedreader kunt bloggen. Ik wil echter ook meteen vanuit iets wat ik lees door kunnen naar het schrijven van een heel artikel. Juist vanwege die gedistribueerde conversaties. Het gaat dan namelijk niet alleen om antwoord op een ander, zoals deze tekst, maar ook om ideeën en zijpaden die door een blogpost van een ander zijn getriggerd. Naast meer soorten postings kunnen maken vanuit een reader, wil ik ook graag feeds kunnen taggen. Ik volg mensen, geen bronnen, in mijn reader, en tagging maakt het mogelijk om dwarsdoorsnedes van mijn netwerk te bekijken.

Voor mij is het lezen/schrijven als deel van mijn blogproces een goede kandidaat voor de tweede dag van ons IndieWebCamp Utrecht, en ik hoop er ook op de eerste dag het een en ander over te kunnen bespreken. Waarbij ik me baseer op mijn 2006 noties van ‘people centered navigation‘, en networked agency (2016-nu).

(Ik schreef dit rechtstreeks in mijn reader, maar voegde later handmatig links en afbeeldingen toe. Dat soort dingen konden vroeger met mooie tools als Qumana, die onderdeel werden van je browser.)

Replied to Het kwartje valt met de Indieweb lees/schrijf bouwstenen by Frank Meeuwsen

Soms moet je bepaalde dingen maar gewoon live testen en zien wat er gebeurt. Zo gebeurde dat dus vanavond. Ik wilde weer eens zien hoe de RSS-apps werken in de Indieweb-community. Via protocollen genaamd Micropub en Microsub kan ik via specifieke RSS-readers een klein stukje magie bewerkstelligen.

Kilroy black edited

Social geolocation services over the years have been very useful for me. The value is in triggering serendipitous meetings: being in a city outside my normal patterns at the same time someone in (or peripheral to) my network is in the city too, outside their normal patterns. It happened infrequently, about once a year, but frequently enough to be useful and keep checking in. I was a heavy user of Plazes and Dopplr, both long since disappeared. As with other social platforms I and my data quickly became the marketable product, instead of the customer. So ultimately I stopped using Foursquare/Swarm much, only occasionally for international travel, and completely in 2016. Yet I still long for that serendipitous effect, so I am looking to make my location and/or travel plans available, for selected readers, through this site.

There are basically three ways in which I could do that.
1) The POSSE way. I post my location or travel plan on this blog, and it gets shared to platforms like Foursquare, and through RSS. I would need to be able to show these postings only to my followers/ readers, and have a password protected RSS feed and subscription workflow.
2) The PESOS way. I use an existing platform to create my check-ins, like Foursquare, and share that back to my blog. Where it is only accessible for followers/readers, and has a password protected rss feed.
3) The ‘just my’ way. I use only my blog to create check-ins and share them selectively with followers and readers, and have a password protected rss feed for it.

Option 3 is the one that provides the most control over my data, but likely limits the way in which I can allow others to follow me, and needs a flexible on-the-go way to add check-ins through mobile.
Option 2 is the one that comes with easy mobile apps, allows followers to use their own platform apps to do so, as well as through my site.
Option 1 is the one that is in between those two. It has the problems of option 3, but still allows others to use their own platforms like in option 2.

I decided to try and do both Option 2, and Option 3. If I can find a way to make Option 3 work well, getting to Option 1 is an extension of it.
Option 2 at first glance was the easiest to create. This because Aaron Parecki already created ‘Own Your Swarm‘ (OYS) which is a bridge between my existing Foursquare/Swarm account and Micropub, an open protocol for which my site has an endpoint. It means I can let OYS talk both to my Swarm account and my site, so that it posts something to this blog every time I check-in in Swarm on my mobile. OYS not just posts the check-ins but also keeps an eye on my Swarm check-ins, so that when there are comments or likes, they too get reflected to my blog.

My blog uses the Posts Kinds plugin, that has a posting type for check-ins, so they get their own presentation in the blog. OYS allows me to automatically tag what it posts, which gets matched to the existing categories and tags in my blog.

I from now on use a separate category for location related postings, called plazes. Plazes was the original geolocation app I started using in 2004, when co-founder Felix Petersen showed it to me on the very first BlogWalk I co-organised in the Netherlands. Plazes also was the first app to quickly show me the value of creating serendipitous meetings. So as an expression of geo-serendipic (serendipity-epic?) nostalgia, I named the postings category after it.

How does this work?

I posted those words just now from my phone using swentel‘s micropublishing app Indigenous for Android. I had tried that before, but I thought it could not use categories. That’s is a key functionality, as I use it to keep postings like these from the front page. This morning I learned during a session on micropublishing that what the micropub client sends is not determining anything on the micropub server side. It just sends the posting and then lets the other end decide what it does with it. I also learned that in microformats categories and tags are the same thing.

It made me realise that where micropub apps talk about categories and tags it doesn’t mean anything about how this WordPress install deals with that. So I tried adding the category name I want in WordPress as a tag to see how this site deals with that. Turns out it works, if you use the internal name of the category in WordPress. So for this posting to end up in the Day to Day category I used the internal name I gave it, which is ‘timeline’, as a tag.

A quick test of my blog’s micropub endpoint (there’s a WordPress micropub plugin) . Using Quill to post this. Quill doesn’t support categories, so this should initially end up on the front page. Ultimately want to be able to simply post on the go from mobile through micropub.


  • It submitted the blogpost ok
  • It made HTML appear as regular text, did not interpret the link I added
  • It added all the tags as one tag
  • It, as expected, did not use categories

Also tried to do the same using Micropublish, but that throws an ‘unauthorized’ error. If it worked, it would however support categories, as well as various microformats, such as replies, like and rsvps. Need to take a look at that error message.

I plan to dedicate some learning time in the coming 12 weeks to better understand the protocols that drive the independent web, or IndieWeb. During our STM18 birthday unconference Frank Meeuwsen presented his experiences on the IndieWeb. Frank, Peter and I have formed an impromptu triade to explore the IndieWeb in the past months. In one of his slides Frank conveniently listed the relevant protocols. I’ll plan for 24 hours to explore 6 protocols. Some of them I already understand better than others, so I’ll start with the ones I feel less knowledgeable about.

The ones I want to explore in more detail, in planned order, are:

  • ActivityPub / OStatus, a decentralized networking protocol (as this ties into my Mastodon experiments as well, this comes first)
  • Micropub, publish on your own domain with 3rd party tools
  • Microsub, own your feed-subscriptions (although I already run my own TinyTinyRss instance)
  • Microformats, markup for data, text, people, events (already used on my blog, but curious to see how I can extend that to more types of data)
  • Indieauth, federated login protocol to sign in with your own domain on other services (already active on my blog, but interested in where else I could use it)
  • Webmentions, respond to a blogpost through your own site (already active on my site, but strongly wish to better format and style it on my site)