

By supporting Micropub, indie-config, and/or action URLs, current feed readers can make it far easier for people on the open web to not only read content the way they currently do on siloed social media services like Facebook, Twitter, Instagram, et al. Increased ease-of-use to allow these functionalities with beautiful user interface will help to move users out of walled-gardens where they’re trapped into the larger universe of the free and open internet. Individuals with their own websites can support the acceptance of these posts to save their interactions with what they’ve read, be they comments, likes, bookmarks, or other interactions. They can also close the loop by supporting Webmentions so that their comments can be sent to (and potentially displayed) on others’ websites. All of these pieces combined make for a more open and democratic web.
When this publication from Richard MacManus (the founder of ReadWriteWeb.com, one of my old favorite standbys) popped up a few weeks ago with the tagline “A non-profit tech blog about the open web”, I immediately bookmarked it and knew it would be at the top of my subscription list. When I read his founding manifesto for the blog, I was hooked and bumped it to the top of my list and tipped off others:
This looks like a must-read blog for #Indieweb proponents.https://t.co/pVvG1h34nb
— ChrisAldrich (@ChrisAldrich) May 31, 2017
There’s also some great articles up by Emre Sokullu, Brian Hendrickson, and Richard MacManus on a variety of other great topics. I hope you’ll take a look at what they’re doing and subscribe.
I’m pleased that they’ve taken something I was planning on posting here on my site and are giving it some wider exposure.
If you’re a journalist, blogger, or writer in the space, do feel free to connect with them to pitch ideas.



So the real question facing companies with stand alone traditional feed reader products–like Feedly, Digg Reader, The Old Reader, Inoreader, Reeder, NewsBlur, Netvibes, Tiny Tiny RSS, WordPress reader–and the cadre of others is:
In short the primary question is:
What should a modern RSS feed reader be capable of doing?
Let’s get this out of the way right at the start: Mastodon is not a Twitter killer. It’s more like Twitter crossed with Reddit, plus it’s open source. But while Mastodon is not going to take over the world, it does have promise as a community platform. Here’s why…
Continue reading 👓 The hunt for Twitter alternatives: Mastodon | AltPlatform
The ideas of being independent and signed are inherently contradictory, and this contradiction is what makes indie hard to define. Its ephemerality gives it both a mystique and a resistance to criticism ― after all, you can’t critique what you can’t define. And thus, using the term indie is often a great marketing move. But it’s a problematic critical move.
However, as someone who knows he’s certainly privileged, I view my definition of indie as something that is also open for others to come behind me and use for free or have the ability to reuse and remix in a way that corporate interests or non-indie work wouldn’t. In a large sense, to me this means that while I may be privileged (whether that be socio-economically or even the time-encumbered), I’m helping to lower the cost and the burden for the less privileged who may come behind me to be able to do more, go further, or go faster.
In some sense too, as described, indie has such a nebulous definition. Often when I see it in a technology related space I really read it as “Open Sourced”.
I vividly remember the Facebook post. It was my friend’s 5-year-old daughter “Kate,” (a pseudonym) standing outside of her house in a bright yellow...
A really interesting and well-executed portfolio site, utterly let down by the tone of this demeaning and insulting piece of copy: WARNING: Do not proceed if you suffer from vertigo or if you find experimental interfaces offensive. (Pssst: copy is also interface.)


This week, most of the educational technology group went to Oklahoma City for the Domains 2017 conference, jointly hosted by Reclaim Hosting and the University of Oklahoma.
We went because we are quite close to setting up a pilot instance of Trinity Domains, a Domain of One’s Own project (see also: A Domain of One’s Own in a Post-Ownership Society) that will give faculty, students, and staff the digital infrastructure to stake out their digital identity and develop new, exciting forms of scholarship. Since setup is imminent, the conference seemed like a good way to see what other schools were doing, and to make connections for when we inevitably need help.
We’re launching the project because we want to be able to support as much open, web-based teaching, learning, and scholarship as possible, in as many forms as possible, and we want to make it as easy as possible for people to experiment online.
I don’t think any of us at Trinity were well-positioned to do a proper “review” of #Domains17, as we don’t yet have access to the Domain of One’s Own setup, and so don’t have fingertip knowledge of what’s easy, what’s hard, or anything like that.
In lieu of that review, then, here’re a few thoughts:
- #Domains17 was a great short-conference experience, at an interesting venue and with lots of very friendly, collaboration-minded people. Lauren Brumfield, Adam Croom, Jim Groom, and everyone associated with the conference deserve a lot of credit. 13/10, would attend another event.
- Martha Burtis’s keynote, “Neither Locked Out Nor Locked In,” is a really great starting point for thinking tangibly about some of the reasons one might want to pursue a Domains project.
- It also primed me with a thought that held up very well throughout the conference: Her entire section on “WordPress as Symbol and Choice” decries the fact that WordPress often becomes the default way to inhabit a domain of one’s own, which is . . . problematic. Students and faculty need to be free to have domains with different technology options, even if we all have to stretch a bit in terms of what we support, and what people have to support on their own a little bit.
- Once you’d heard that talk from Martha, it was hard not to realize that the conference schedule was quite WordPress focused. There were more examples of “here’s how to do a cool thing in WordPress” than there were examples of “here’s a successful instructional use of Domains.” This is neither good nor bad as such, but it was just interesting to see the lay of the land. Since we have two multisite WordPress installations on campus, the temptation to default to WordPress will be something to both resist and work with.
- Switching gears a little: On a personal note it was neat to see Jon Udell talk about annotation. It’s probably not the thing he’d pick to be known for, but I’ve shown his screencast on Wikipedia & the heavy metal umlaut to thousands of people over the years.
There will be more thoughts on this over the summer—and I’d certainly invite Amy and Dave and Sue to chime in with their impressions—as we get started. Certainly it’s the case that I jotted down a ton of things to look into as soon as we’re up and running, which I hope to be able to report on soon!
Photo with all four of us by Tom Woodward, shared under a Creative Commons-BY-SA-2.0 license
Teachers, educators, researchers, technologists using open technologies in education #openEd, #edTech, #DoOO, #IndieWeb
Feel free to either subscribe to the list (useful when adding streams to things like Tweetdeck), or for quickly scanning down the list and following people on a particular topic en-masse. Hopefully it will help people to remain connected following the conference. I’ve written about some other ideas about staying in touch here.
If you or someone you know is conspicuously missing, please let me know and I’m happy to add them. Hopefully this list will free others from spending the inordinate amount of time to create similar bulk lists from the week.