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.

6 reactions on “On Reading Feeds #Indieweb Style

  1. I’m a big fan of Monocle, which I’ve been slowly transitioning to in lieu of Feedly. I’ve found that once you *really* get used to a Social Reader, you don’t really want to go back to a traditional RSS reader. I run my own instance of the reader, but I haven’t gone so far as to setup my own MicroSub server yet – I’m still using the hosted Aperture service.
    The list of “actions” in Monocle is too small for my tastes as well. Thankfully, as it’s open-source, I can expand on those to my liking. I’m planning to work on that after I’ve finished adding the “mark all as read” button I’ve been missing!

    via mrkapowski.com

  2. Na een evenement is het altijd leuk om nog even na te genieten, terug te lezen wat er is gebeurd en wat je mogelijk zelf hebt gemist. Daarom ben ik zo blij met de drie blogposts van Ton. Als mede-organisator van IndieWebCamp Utrecht moest hij helaas om privé omstandigheden al na de eerste ochtend afhaken. Maar dat heeft hem niet weerhouden om uitgebreid te schrijven over de introducties van alle aanwezigen, zijn eigen plannen voor de hackday op dag 2 en hoe hij op afstand de demo’s van de hackday heeft ervaren.
    We zullen een deze dagen de video’s beschikbaar stellen via de wiki. Als er meer posts komen zal ik die zo snel mogelijk hier toevoegen.
    Nu is het wachten op de volgende IndieWebCamp in Nederland. Waar en wanneer zal deze plaatsvinden?

    Doorgeplaatst op:

Reading

  • Andy
  • daveymoloney
  • Chris Aldrich

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.