agreed! i had the same reaction to “move fast.” trendy and well intentioned, but misleading compared to, say, “enough iterations.”

this also reminds me of your great post on tiers of feedback loops. really refreshing perspective. it’s hard to step back from the urgency of the immediate tasks at hand, day in and day out, and think objectively about the big picture. i’m glad you did!

Re: this post

whoa! agreed, that is pretty damn cool.

silly question, since i definitely watch my fair share of TV…but what’s next weekend? maybe i’m too US-centric, is it an icelandic/european thing?

hell yes! me too…at least the plan, if not the exact date. :P

reading and other ecosystem-wide functionality are definitely still long poles for the indieweb. i’ve used twitter-atom (and facebook-atom, etc) for a long time to read my silo feeds, which work well. they let me cheat and still use the silo UXes to manage my (siloed) friend graphs, but consume the content in my feed reader. one step at a time!

on the replies side, i currently use salmon-unofficial to backfeed my own site, but it’s flaky and brittle. i’m working on making Bridgy 1) accept webmentioned replies against siloed posts (e.g. tweets) and POSSE them into the silos, and more importantly 2) generate webmentions for replies that originate inside silos and serve those replies as microformatted HTML so the recipient can close the loop. existing indieweb projects already support 1 to a degree, but 2 will be somewhat new, so i’m excited about that.

onward!

Also in reply to