Reply to Tom Critchlow on feeds

Replied to a post by Tom CritchlowTom Critchlow (
This is a list of the feeds I'm reading. The page auto-updates every 10 minutes or so. Why? Because we need to resist the hyperfeeds and build our own small feeds in the open
I’m curious how you’re generating your particular feeds. For over a year now I’ve been using a simple bookmarklet system to post what I’m reading, listening to, and watching to my own website and providing it as various feeds (RSS, JSON, and a microformats-based hfeed/h-feed) for others as well as syndicating some of these to other sources. (For the RSS feeds just add /feed/ to the end of the links above. You can also chain them like so,listen,watch/ to get multiple feeds at once.)

I wish others were providing this type of data outside of the big silos as well, but it obviously needs to be much simpler.

Published by

Chris Aldrich

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, IndieWeb, theoretical mathematics, and big history. I'm also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.

7 thoughts on “Reply to Tom Critchlow on feeds”

    1. I record everything, but I only publicly publish the top 50% or so. The rest is hiding on my back end for the eventuality that I want to remember the source or some random bit three weeks later.

  1. Hey! Sorry just saw this.

    As Aaron says – this was indeed inspired by Dave Winer’s Radio 3. I wanted to build something so simple that anyone and everyone could build their own RSS aggregator in public.

    Unfortunately, RSS has lots of little edge cases and my coding knowledge is half-baked at best 🙂

    So I ended up stitching together a series of things.

    I put the feed URLs into a google doc
    I have a google script using to fetch each feed every 10 mins or so
    Those feeds are parsed back into the Google Doc
    Then I use tabletop js to display the google doc as a webpage.

    I did have a conversation with Dave about porting River 5 to Glitch which I think is a far more robust and better solution for most people but I haven’t had a chance to port my set up over yet:

    (Also, I know nothing about node and while my solution is all duct tape at least I know how each part works mostly….)

    1. Thanks Tom. It’s always interesting to hear how others are doing this, particularly when they’re using solutions to own all of their data in the long term. This is also the fifth or sixth reference I’ve seen lately to people coming up with solutions using Glitch as well. Perhaps I should be tinkering more with it?

      Syndicated copies:

      1. I’m loving glitch more and more. It’s a really interesting platform. I’d recommend playing around with it – once you get over the weird branding and the slightly odd workflow and UI around creation the core product is remarkably robust and full-featured. It’s making me want to learn node!

Leave a Reply

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