Op 28 en 29 september vindt IndieWebCamp Amsterdam plaats. We hebben een locatie, maar die is nog niet helemaal rond. Maar rond genoeg om zeker te weten dat IndieWebCamp plaats gaat vinden!

Na IndieWebCamp Utrecht in mei, is dit de 2e IndieWebCamp in Nederland.
Zet het weekend van 28 en 29 september vast in je agenda, en zorg dat je er bij bent!

Neem het web in eigen hand! Het is de hoogste tijd te zorgen dat het web ons tot dienst is. Door meer van het web in eigen handen te nemen. Het onafhankelijk web (indieweb) is het oorspronkelijke web, waar jij bepaalt wat je deelt, wat zichtbaar is voor anderen, en waar jouw data van jou is omdat het op je eigen site staat.

IndieWebCamp Amsterdam heeft geen publiek, alleen deelnemers. Op de eerste dag kun je sessies voorstellen of aan sessies deelnemen over elk aspect van het onafhankelijk web dat je wilt. Op de tweede dag bouw je aan je eigen deelname of bijdrage aan het open web.

Jij bent iemand die een open web wil, al wel een eigen site heeft of nog niet, misschien ben je ook ontwerper of programmeur, ben je een denker of een doener. Jij bent degene die we zoeken om twee dagen met anderen om het onafhankelijke web te bespreken, te verkennen, en te bouwen.

Meer info over aanmelding volgt eind juli.

Björn Wijers demoing, with Dylan, Neil and Julia in the photo looking on

Most of yesterday’s participants returned today to get under the hood of their websites and build something. I didn’t attend in person, but participated remotely in the opening session this morning, and the demo’s this afternoon. The demo session has just concluded and some cool things were created, or at least started. Here are a few:

Frank Meeuwsen worked on an OPML importer for Aperture, a microsub server. This way it is possible to import the feeds from your existing RSS reader into your microsub server. Very useful to aid migrating to a new way of reading online content.

Jeremy Cherfas worked on displaying his gps tracks on his site, using Compass

Rosemary Orchard, extending on that, created the option of sharing her geo location on her site for a specified number of minutes.

Neil Mather installed a separate WordPress install to experiment with ActivityPub, and succeeded in sending messages from WordPress to Mastodon, and receive back replies.

Björn Wijers wrote a tool that grabs book descriptions from GoodReads for him to post to his blog when he finishes a book.

Martijn van der Ven picked up on Djoerd Hiemstra’s session yesterday on federated search, and created a search tool that searches within the weblogs of IndieWeb community members.

That concludes the first IndieWebCamp in Utrecht, with a shout-out to all who contributed.

It’s a wrap! The first #indiewebcamp in Utrecht was a lot of fun. Thank you to all participants, @frankmeeuwsen for doing the heavy lifting (I had to bail), and Johan Adriaans for providing the shoppagina.nl venue this weekend! #indieweb See you at #indiewebcamp Amsterdam in September?

This is a quick exploration of my current and preferred feed reading patterns. As part of my activities, for Day 2, the hack day, of IndieWebCamp Utrecht.

I currently use a stand alone RSS reader, which only consumes RSS feeds. I also experiment with TinyTinyRSS which is a self-hosted feed-grabber and reader. I am attracted to TinyTiny RSS beacue 1) it has a database I can access, 2) it can create RSS from any selection I make, and it publishes a ‘live’ OPML file of feeds I track, which I use as blogroll in the side bar.

What I miss is being able to follow ‘any’ feed, for instance JSON feeds which would allow tracking anything that has an API. Tracking #topics on Twitter, or people’s tweets. Or adding newsletters, so I can keep them out of my mail client, and add them to my reader. And there are things that I think don’t have feeds, but I might be able to create them. E.g. URLs mentioned in Slack channels, or conversation notes I take (currently in Evernote).

Using IndieWeb building blocks: the attraction of IndieWeb here is that it makes a distinction between collecting / grabbing feeds and reading them. A Microsub server grabs and stores feeds. A Microsub client then is the actual reader.
Combined with Micropub, the ability to post to your own site from a different client, allows directly sharing or responding from a reader. In the background Webmention then works its magic of pulling all that together so that the full interaction can be shown on my blog.

The sharing buttons in a (microsub client) reader like Monocle are ‘liking’, ‘repost’ and ‘reply’. This list is too short to my taste. Bookmarking, ‘repost with short remarks’ and ‘turn into a draft for long form’ are obvious additions. But there’s another range of things to add about sharing into channels that aren’t my website or not a website at all, and channels that aren’t fully public.

To get things under my own control, first I want to run my own microsub server, so I have the collected feeds somewhere I can access. And so I can start experimenting with collecting types of feeds that aren’t RSS.

#indiewebcamp Utrecht off to a good start with 9 ppl on site, and me remote. Day 2 is about building things for the #indieweb, with live streamed demo’s at 15:30. Topics range from opml importers, reader syncing, federated search, visualisations for discovery, and more.

I will try to clarify my own routines on reading feeds: what is my current process, what demands does it make of my tools? How well do building blocks like Microsub and -pub map on to that?

I may also take a look at the code of the Yarns WordPress plugins, how it stores feeds. I am interested in tagging feeds (not articles). Most of my feeds are people (Frank’s blog, Peter’s blog etc), and with tags I can make subsets across feeds like “show me what indieweb folks are up to today” or “I’m visiting Vienna, let’s catch up with the Viennese in my reader before contacting them for a meet-up”.

But first, coffee!