Ryan BarrettIt’s been a month since the last Bridgy Fed status update, so it’s time for a new one! I’ve spent a lot of time over the last month on user-visible improvements and bug fixes, notably more complex post types and links, as well as underlying infrastructure. Details below.
One area I need to spend more time on is cost. My attempts at optimization there have been slower than I’d originally hoped. I intentionally prioritized functionality over cost efficiency for a long time, and I’m still optimistic that I can get cost per user down to a reasonable level. If I do that, but user count itself gets too high…that will be a wonderful problem, and I’ll cross that bridge when I get to it. 😁
(Standard disclaimer: Bridgy Fed is non-commercial, free, open source, and ad-free, and I have no plans to change any of that or ask for donations any time soon! It’s one way I try to support and give back to the open social web.)
Beyond cost, I’m hoping to work on native replies and opt in prompts via DM, both directions, soon.
As usual, feel free to ping me with feedback, questions, and bug reports. You can follow the now label on GitHub to see what I’m currently focusing on. See you on the bridge!
- You can disable and delete your bridged account, on either side, by blocking the Bridgy Fed bot user (background). Note that right now this cannot be undone. Maybe eventually!
- Lots of improvements to rich post/profile content and text:
- quote posts
- videos and GIFs
- content warnings
- link previews
- hashtags
- @-mentions (more)
- profile bios
- full text of truncated posts and profile bios for third party Bluesky apps like Skythread and Skywalker
- …and other bug fixes
- Improved authorization/access control checks
- Infrastructural improvements:
- Cut new releases of arroba, lexrpc, and dag-json, three libraries of mine that are key building blocks for Bridgy Fed’s Bluesky (AT Protocol) support.
All GNU social JP content and data are available under the