In general, this means that you should make posts on your own site, then copy the post to silos like Twitter, Facebook, etc., to reach the folks in those communities. To complete the process, include links on your site from the original post out to the syndicated copies.
One fun reason to do this is that tools like brid.gy use syndication links in order to backfeed comments and reactions from silos like Facebook and Twitter to your own site.
I'd been collecting these links for a while and displaying them in a "hidden" way - so tools like bridgy could see them, but a human reading the page would not.
Yesterday I added a "See also:" section that includes links out to any syndicated copies of my posts on other sites.
Episode 5 of Lawful & Orderly: Special Visions Unit is now available for watching on YouTube! L&O:SVU is a weekly live-streaming police procedural set in a fantasy universe played (loosely) with D&D 5th Edition rules.
Jeremy raises some great points here that mirror some of my own worries about trying to summarize the discussions happening on the IndieWeb wiki and the many #indieweb chat channels.
When I had the initial idea to do an “audio edition” of This Week in the IndieWeb, the question of “who is the audience” seemed to have an obvious answer: folks who would read the newsletter but preferred an audio edition.
However, it quickly became clear that doing a “direct read” of the newsletter — where much of the content is names and links to changes on wiki pages — wouldn’t make a lot of sense when spoken aloud. So, my first crack at the format evolved into answering a slightly broader question: “how can I explain these updates to someone who might not already be familiar with the wiki?”
My short (and unhelpful) answer is: this is hard. The discussions on the wiki tend to be very technical, jargon-heavy, and touch on an extremely wide set of topics. In the first episode, I attempted to give some structure with groupings like “IndieWeb Events”, “Software and Services”, “Silo Updates”, “Silo Issues”, etc., but I agree with Jeremy that it is still very fast and dense. While I want to keep the podcast short (less than 10 minutes), I think a next positive step would be to give topics more time to breathe with some explanatory commas that give context.
It is my hope that projects like this podcast will help find new ways to phrase and frame the things that the IndieWeb community are doing and talking about, helping to reach new folks. I have a feeling it is going to be a lot of work. :}
Thanks for the write-up! I would absolutely love to see multiple folks posting IndieWeb audio content, including interviews and deeper discussions. Maybe aggregated at IndieNews and converted to podcast format there?
First up, I added support for "tag aggregations" - essentially, pages that list all posts with a certain tag. So, any future editions of this audio newsletter that I post can be tagged with "this-week-indieweb-podcast" and will then show up on the "This Week in the IndieWeb Podcast" page. It should soon be possible to feed that page to a tool like Granary to convert the feed on that page, with its audio entries, into an RSS feed suitable for subscribing with a podcast app.
Next up, I added support for "Media Fragments", a W3C recommendation that allows linking to a specific timestamp to start (and even stop!) playback of video and audio. Aaron Parecki's recently implemented this on his own site and was kind enough to share the implementation! Now, you can create links that jump to a specific time of any audio or video post on my site.
For example, if you want to quickly jump to the part of the This Week in the IndieWeb audio edition that contains info about the next upcoming Homebrew Website Club meetings, it looks like this: https://martymcgui.re/2017/02/18/151503/#t=54
Media fragments could enable some fun things, such as a list of links that index directly to particular sections of a long recording.
martymcgui.re - reworked his micropub server to support the media endpoint he was working on last time. also added venue pages to his site for event locations. made progress on event-posting micropub client (eventually will be released publicly). also added support for deleted posts with dt-deleted and meta http-equiv status 410 gone.
jonathanprozzi.net - refactoring site templates. spent a lot of time debugging some simple problems, h-cards. wants to figure out a way to track incremental work on website when other work things are crazy so threads don't get lost. wants to keep segmenting his Hugo template while maintaining mf2 stuff. goal is to get to working on appearance of his site theme.
jjuran.org - currently working on a CV on his site. first use of img srcset to feed high-res images to clients that want them. uses his own Perl-based static site generator that is "showing its age". working on his own programming language so he can spend most of his time writing code in a high-level language.
We discussed the challenges of building your own tools for fun vs. starting from the goal of posting more (e.g. via Wordpress).
We hope that you'll join us for the next HWC Baltimore on March 22nd back here at the Digital Harbor Foundation Tech Center.