Announcing Support for Bridgy Publish

Featured image for sharing metadata for article

As I was starting to get more involved in the IndieWeb, I started to own my RSVPs to events I was attending, most of which are hosted on This was partly to own the data itself and allow me to do things like create my own attending calendar, but also to make it easier for friends, colleagues, and family to see what I was attending.

However, this quest to own my data still had a little problem - I was RSVPing to my website, as well as RSVPing on I'm not a fan of manual work, so this was a bit painful, so I started to look at creating a simple client for the API that would perform the RSVPs on my behalf.

The API itself seemed fairly straightforward, so I then started looking at how to send the RSVPs automagically after my site deployed. While looking into the process, I found out about Bridgy, which is built to be the bridge between the Silo'd web, such as Twitter or, and the IndieWeb. This seemed like a great place to start, in a way that could benefit everyone on the IndieWeb, so I raised a feature request for

For several months, the issue lay silent, until at IndieWebCamp Amsterdam, I started the implementation of it on the Sunday hack day. I didn't manage to get much luck with it because I had some trouble reminding myself how Python and its dependency management tooling worked, but I'd started it, and over the coming months I would carry on with my implementation where I had time.

Now, 263 days later of on-and-off work, I'm very happy to announce that is now live on Bridgy! It's taken 14 Pull Requests, and a lot of back-and-forth collaboration with Ryan, Bridgy's author, to get this working, and I want to say a huge thank you to him for supporting it! He's mentioned that aside from him, only Kyle has contributed a Silo to Bridgy. I'd love for more folks to get involved and adding more functionality to Bridgy, but I'd also like to see more alternative approaches!

This Bridgy support also leads me to a great IndieWeb win - I can now own the discovery and attendance portion of attending events completely IndieWeb tooling, as well as publishing notes (that get converted to tweets by Bridgy) while I'm there to share my thoughts with others.

This is personally a huge win for me, and I'm really happy with getting it live.

Written by Jamie Tanna's profile image Jamie Tanna on , and last updated on .

Content for this article is shared under the terms of the Creative Commons Attribution Non Commercial Share Alike 4.0 International, and code is shared under the Apache License 2.0.

#bridgy #indieweb

Also on: IndieWebCamp logo logo logo

This post was filed under articles.

Interactions with this post

Interactions with this post

Below you can find the interactions that this page has had using WebMention.

Have you written a response to this post? Let me know the URL:

Do you not have a website set up with WebMention capabilities? You can use Comment Parade.