I dunno. I see this Add a "tweetstorm" UI for chaining status updates with chained POSSE tweets and I think of something I wrote a while back: Or you could write a blog post. Does the #IndieWeb really need to make indie copies of everything the silos offer? Even the workarounds?

Maybe I misunderstand, and a feature like this is what weans people off the silo pap. All I know is, I don't think it would work for me.

Playing Lyle Lovett singing Texas River Song, even though I know it's a stretch, to celebrate having eaten a giant bowl of my own dogfood.

A couple of weeks ago I followed Chris Aldrich to reading.am, which is a neat little spot for just putting down a marker for something that you're reading. I wanted more. I wanted to be able to save links to the things I marked. And now, a little over two weeks later, I've done it.

I have a PHP file that fetches the RSS feeds of things I've marked in reading.am, looks for any that are new since the last time the program ran, and then POSTS the results to Known's micropub endpoint. #IndieWeb PESOS for my bookmarks!

There is no way I could have done it without amazing help from people on the IndieWeb IRC, and it isn't perfect by any means. There's more work to be done, for sure, before I even think about sharing the code.

But hey, it works.

And, as my main helper said, "Launch early and iterate often".

I'll be doing that.

We had a virtual meeting of the Homebrew Website Club yesterday evening, and as usual it was interesting and informative. We all forgot to take notes, but sketchess was prompted to do a brain dump, which I have added to and tightened up slightly to capture the main points.

• There was a lot of discussion of the confusion among people new to #IndieWeb caused by having so many different ways to achieve the same thing. Some people thought it would be good if there were, maybe, a recommended approach for specific circumstances. However, that does require the user to be clear what they are trying to achieve.
• sketchess suggested that directed tutorials to achieve a specific outcome would be helpful. There was some support for this but, as ever, the issue of time can be a constraint.
• We talked about the potential usefulness of different levels of wiki pages, or a special section, or something completely independent of the wiki.
• aaronpk reminded us that the difficulty with independent offerings is that there can be difficulties in maintaining momentum. The wiki, as a collective effort, is more likely to be managed by individuals.
• We noted that sometimes developers simply do not remember what it was like to start some activity, and also that a “getting started” for an experienced developer would be completely different from a “getting started” for someone who perhaps only knows silos. A beginner's guide written by recent beginners, with expert input from more experienced people, might be useful.
• We talked about self-dogfooding, and that this may be inhibiting Generation 2 and up. They are not necessarily interested in building things themselves, although they want to make use of IndieWeb principles and practices.
• Several people seem to be exploring the IndieWeb without making use of IRC or the wiki. Their efforts sometimes show up in IRC thanks to Loqi. Would it be useful to reach out directly and suggest they join and use the wiki?

Comments and edits welcome.