Part of this is an opportunity to improve audio post presentation on my website, so you will see audio posts improve over time.
An Indieweb Podcast Episode 0
This is a test episode of An Indieweb Podcast(working title). In it, Chris Aldrich and I talk about a variety of Indieweb topics, with the theme of Considering the User, inspired by an article we were reading.
I’ve been listening to the inaugural episode of the currently unnamed IndieWeb podcast this evening. The episode offers some great context about the history of the IndieWeb, specifically the WordPress plugins. I haven’t finished listening to the episode yet, but am excited to continue listening…especially since the conversation is partially orbiting one of my recent posts!
I’ve got to go to sleep before I can finish listening, but I wanted to take a moment to send a quick thanks to Chris Aldrich and David Shanks for the great conversation, and to let them both know that I am 100% willing and excited to roll up my sleeves and help out with this! My professional background is mostly in front-end dev. and product design, so I can’t help but to think of the IndieWeb in those contexts. ?
🎧 Listened to “An Indieweb Podcast Episode 0” by David Shanske and Chris Aldrich.
I really enjoyed this pilot episode! I was particularly interested in some of the discussion around annotations for audio. I think I’ll spend some time noodling on using Jon Udell’s clipping tool to generate shareable snippet URLs, and updating my webmention handling to try and turn mentions with media fragment timestamps into pretty annotations.
https://david.shanske.com/2018/03/18/an-indieweb-podcast-episode-0/
If possible, click to play, otherwise your browser may be unable to play this audio file.I really enjoyed this David and Chris. It was a wonderful insight into the #IndieWeb community. A couple of take-aways:
The possibilities associated with Post-Kinds. I am wondering if instead of creating additional tags and categories that I need to craft my own kinds to differentiate between podcasts and music.
I feel that the future lies in the community. I concur with Chris that I do not think that my place is coding the future. Instead I think that my contribution is in testing and trialing different additions. A point that I made in response to Eli Mellen.
If theis were to become a semi-regular occurance, it would be good to have a basic summary of discussions, as well as links to support further investigations.
Oh, and in regards to ‘impact’ (something that we love in the education world), it encouraged me to add GitHub to Bridgy. Thank you for the support and community as always.
Also on:
# Eli Mellen wrote a great post about how the #indieweb needs to be more accessible to non-developers. It prompted some considered response including this post from Jeremy Cherfas in which he points to a response from Peter Molnar. And then there is “An Indieweb Podcast” from David Shanske and Chris Aldridge.
Eli linked to the indieweb generations page (the suggested adoption path) exclaiming that much of the current technology is rooted in generations 1 & 2 (the more technical users) but needs to be accessible to those in generations 3 & 4.
He espoused micro.blog as an example of pushing things towards the later generations suggesting it’s ‘time to update some of the tooling” to bridge the gap.
Having written previously about the need for easier implementation I didn’t want to just repeat myself, or Eli, so wasn’t sure how to respond or what extra I could add.
But then two posts cemented my thoughts.
Firstly, Manton Reece (creator of micro.blog) highlighted that the much sought after ownership of content doesn’t just mean owning the server and having direct control over the source code. Instead, it’s about “portable URLs and data. It’s about domain names” so that a site can outlive any platform.
Micro.blog as a service definitely straddles generations 3 & 4 as it works just as well with existing blogs as a blog hosted on the service itself. But If you opt for the latter then Manton has made things considerably simpler for you.
A CMS, webmentions, publishing by micropub, it’s all built in, nothing else required apart from a micropub client – of which the native iOS and Mac micro.blog apps are perfectly functional and more than adequate examples.
This is exactly what Eli alludes to when he says you can’t assume that users will care about the tech or the specs – they just want the tools.
Peter Molnar argues that “people should care, they should be at least be aware of what’s happening when they press a publish button” and that “providing the tools only is not a goal I can align with.”
I have to agree with Eli here.
People don’t have any idea how Twitter and Facebook work but are willing to throw themselves at it despite warnings. Merely a fraction of the population has ever heard of MX records, and wouldn’t know their POP3 from their IMAP, but billions still use email.
This is why ecosystems and adoption curves exist; some blaze the trails and develop solutions so others can use them without having to.
WordPress users, for example, load plugins to get the functionality they require with no idea of how that’s actually achieved. It’s taken on faith because the creators and the standards organisations have done their jobs.
And that is the generational gap
Next, Jason Kottke’s linked to Dan Cohen’s post “Back to the Blog” in which he talks about the importance of writing on one’s own domain but suggests many don’t because we are social animals and social networks provide “a powerful sense of ambient humanity.”
I’ve previously described micro.blog as a social layer or glue but I think “ambient humanity” sums it up perfectly – the feeling that “others are here” as Dan puts it. This is absolutely what micro.blog helps to achieve: that connection between people, between blogs, even if you have set up on your own.
You don’t have to be isolated.
The aim of the indieweb is that we can do our own thing, or join something like micro.blog, and that our sites and services are portable and interoperable because the technology is platform agnostic. For this to happen the ecosystem needs to be mature with tooling simple enough that anyone can plug and play, or have it built in to their platform of choice, without needing to know how it works.
It needs to be invisible.
I enjoyed listening to this podcast. Nice format, just informal chatting about a bunch of Indieweb related topics. I’d like to hear more of these.
This Article was mentioned on indieweb.org