Replied to
post from
Headed to DC to #marchforscience! ⚛️🌎

A wet, but great, walk through DC with some science-loving friends.

Headed to DC to #marchforscience! ⚛️🌎

This Week in the IndieWeb Audio Edition • April 15th - 21st, 2017

Audio edition for This Week in the IndieWeb for April 15th - 21st, 2017.

You can find all of my audio editions here.

You can subscribe with your favorite podcast app on huffduffer.

Music from Aaron Parecki’s 100DaysOfMusic project: Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11

Thanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you’d like to see for this audio edition!

Homebrew Website Club Baltimore May 10, 2017

Digital Harbor Foundation Tech Center 1045 Light St., BaltimoreMD, 21230

Join us for an evening of quiet writing, wiki editing, IndieWeb demos and discussions!

  • Create or update your personal web site!
  • Finish that blog post you’ve been writing, edit the wiki!
  • Demos of recent IndieWeb breakthroughs, share what you’ve gotten working!
  • Join a community with like-minded interests. Bring friends that want a personal site!

Any questions? Join the #indieweb chat!

Optional quiet writing hour starts at 6:30pm. Meetup begins at 7:30pm.

More information:

Facebook event:

HWC Baltimore 2017-04-19 Wrap-Up

Baltimore's April 2017 meetup for Homebrew Website Club met at the Digital Harbor Foundation Tech Center on April 19th.

Notes from the "broadcast" portion of the meetup. – Been working on some content based on personal notes, which he takes all the time, about things like stuff he's read, etc. Thought about turning ~5 of his notes at a time into monthly lists, but has been writing a lot. Might be more like each note becomes a paragraph-long post. He also manages a newsletter that usually covers one topic, but might automate these new "listy" posts into a collection for the newsletter. – Been working on a longer content post, part two of a series that started in March about creativity and code and his personal learning journey. Wants to keep up with post-a-week challenge. Started capturing ideas because he tends to forget topics if he doesn't get started on them. Doesn't want to have long spans of time between posts, so needs a system to keep track of posting as he gets too busy to take big chunks of time. – Been working on cleaning up cruft in his site implementation, not a lot of publicly visible stuff. Also been thinking a lot about things that stop him from posting, like not being able to easily syndicate posts while on mobile, and thinking of plans to make it easier. Tonight worked on the first part of supporting micropub edits for his site by working on source queries.

We also had a good discussion about how folks track their projects, keep ongoing notes, nudge themselves to make progress, and more. We talked about tools like Google Calendar and Tasks,, "GTD", and more that I forgot to write down.

Left-to-right:, mysterious air plant,,

We hope that you'll join us for the next HWC Baltimore on May 10th back here at the Digital Harbor Foundation Tech Center! It's an "Off-Week" for the usual HWC schedule. After that we're back on track with another "On-Week" HWC on May 31st!

Photo for tonight’s HWC Baltimore

Easier POSSE with Micropub Edits?

Update: thanks to Ryan Barrett for pointing me to his Keep Bridgy Publish dumb post, which explains why Bridgy doesn't include the features mentioned below!

Nerd alert: This post is me geeking out and will involve talk of protocols.

In keeping with the IndieWeb concept of POSSE (Publishing on my Own Site, Syndicating Elsewhere), I try to make social media posts on my own site first and then make similar (not always identical!) posts to my accounts on silos like Twitter and Facebook. I then add links to the posts on my site indicating that you can find the "syndicated copies" of that post on those silos.

My process for doing this is something like:

  • Make a new post, likely with a micropub client like Quill.
  • Log in to Twitter and make a similar post, making note of the URL to the new tweet.
  • Log in to Facebook and make a similar post, making note of the URL to the new FB post.
  • Edit the metadata to my post to indicate the new syndication links.
  • Re-publish the post on my site.

Because of the way my site is set up, this manual process requires the use of my laptop, so I can't do it on the go.

When thinking of ways to automate this process, I found myself drawn to another nice IndieWeb tool called Telegraph. Telegraph takes the URL for a post, finds links inside that post, and (if they support webmentions) allows me to notify those sites about that my post links to theirs with a single click.

Excerpt from Telegraph's UI with buttons to Send Webmention to supported URLs

I like the way Telegraph works for several reasons:

  • It's not purpose-built for a single website - it can be used for sending webmentions from any site that publishes their content with the right markup to any site that can receive them.
  • It puts the final decision to send a mention in my hands - I can choose to send mentions to any particular link mentioned in my post, or not.
  • With a bookmarklet, the process of sending webmentions becomes very simple. I visit the page for my post, click my Telegraph bookmark in my browser, and Telegraph shows me the links and send buttons for my post.

There already exists a great tool for copying content from my site to certain silos: While's primary use case is to use webmentions to syndicate comments and other activity from silos onto your own site, also has a Publish feature which accepts a URL from your site and attempts to create a similar post on the silo of your choice. Publish is a great feature, and I make good use of it. However, there are still a few pain points that I feel when using it:

  • While Publish gives a nice preview of what it will do, I can't tweak the content before publishing without editing my own post.
  • does not, as far as I can tell, support bookmarklet functionality. So, publishing takes multiple steps:
    1. Visit my profile page for a particular silo account.
    2. Enter the URL for the post on my site.
    3. Approve the post.
    4. Copy the URL for the new silo post from
  • Finally, while lets me know in its UI that my post succeeded, has no mechanism for informing my site that the new syndicated post is available. I still need to enter the syndication URLs into my post manually and re-publish my post.

With that groundwork of existing tools, here is what (I think) my ideal workflow would look like:

  1. Make a new post to my site, likely with a micropub client like Quill.
  2. While looking at my post, click a bookmarklet that takes me to a syndication tool.
  3. The syndication tool shows me previews of what my post would look like on each silo where I'd like to publish. I can tweak the content, if needed.
  4. A single "Publish" click for each silo would create the post on that silo, but would also update my website with the new syndication link.

This tool seems non-trivial to implement, but I think there are several building blocks which could be quite useful:

I am not currently aware of anyone who does POSSE with this particular flow. I would be interested to know other folks' thoughts on this! Feel free to let me know with a post on your own site that mentions this one, or hit me up in the #indieweb-dev IRC chat!

Further Reading:

Tonight! 6:30-8:30pm at Digital Harbor Foundation Tech Center, join us for Homebrew Website Club Baltimore. Work on your website and share knowledge with folks who are doing the same!

post from
Homebrew Website Club Baltimore Apr 19, 2017

Digital Harbor Foundation Tech Center BaltimoreMD

Thanks to our guest Kevin Permison for giving Baltimore the song it deserves in this week’s We Have to Ask Podcast!

post from
What's Good? • Ep 71 - Baltimore Joe
★ Favorited
post from
🔴 LIVE in 1-hour! CSI: Criminal Sorcery Investigation w/ @ThatOneGM @schmarty @geowtf & @alo_seda1 #dndsvu #dnd #twitch #livestream #improv