Manually reconstructed Bridgy URLs redirect to silos

Filed an Issue snarfed/bridgy (GitHub)
Bridgy pulls comments and likes from social networks back to your web site. You can also use it to publish your posts to those networks.
It’s mentioned in the documentation that one can reconstruct URLs to allow manually resending webmentions for missed backfeed. However, it appears this may no longer work(?) as these reconstructed URLs, which used to be static are now automatically redirecting to their siloed instances.

Example: https://brid.gy/post/twitter/schnarfed/476408043819659264
redirects to https://twitter.com/schnarfed/status/476408043819659264

Separately, though related, the example in the documentation for Instagram no longer seems to exist and could be replaced and the example for Google+ could be removed as the service no longer exists.

Published by

Chris Aldrich

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, IndieWeb, theoretical mathematics, and big history. I'm also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.

2 thoughts on “Manually reconstructed Bridgy URLs redirect to silos”

  1. bridgy’s mf2 URLs redirect with HTML meta refresh. webmentions with them as sources should still work fine! (afaik webmention receivers don’t/shouldn’t follow meta refresh redirects, right?)

Leave a Reply

Your email address will not be published. Required fields are marked *