Hi everyone! Time for a Bridgy Fed status update. We have a lot of new features and bug fixes to announce since the last time, so here we go!

• Added a web-based UI for enabling and configuring the bridge for your accounts.
• Added support for fediverse split domain mode, ie when your webfinger address and server are on different domains
• We now fully support Bluesky custom handle changes and propagate them to bridged accounts
• Fediverse instance admins can now automatically enable the bridge for their users and automatically give them custom Bluesky handles
• Redesigned our Bluesky firehose server, which has significantly improved its reliability and reduced delays in both directions
• Implemented ATProto sync v1.1. This isn’t a user-visible change, but it’s an important part of reducing the cost of running an ATProto relay
• Implemented pinned posts for fediverse => Bluesky
• Detect videos that are too long for Bluesky and link to them instead of including them as broken video embeds (thank you @Daft-Freak!)
• Improved our compatibility with Mastodon profile updates
• Improved our handling of HTML in web link previews
• Made DMs smarter about understanding handle formats and encodings
• Started using an image proxy for Threads, to work around its image URLs expiring
• Bug fix for images that are reused across fediverse posts and drafts
• Link to audio attachments instead of ignoring them (thank you @Daft-Freak!)
• Improve fediverse instances’ hashtag handling so that they open inside the local instance
• Added “Open in Mastodon” support for user pages on fed.brid.gy
• Improved our nodeinfo support for Friendica
• Handle fediverse posts with over 8 hashtags
• Fediverse => Bluesky: fix text formatting for posts with < and > characters
• Bluesky => fediverse: add support for “out-of-line” hashtags
• Make our fediverse posts more translate-able
• When a user tries to enable the bridge but isn’t eligible, DM them an explanation
• Don’t apply spam filters to users who aren’t bridged and follow a bridged user
• Improved our deploy process so that it no longer causes delays temporarily

As usual, feel free to ping us with feedback, questions, and bug reports, and please support us on Patreon! You can follow the now label on GitHub to see what we’re currently focusing on. See you on the bridge!