Happy New Year! Hope you all had a good holiday. It’s shaping up to be a great year on the open social web!

We’ve been busy working on new features, internal improvements, bug fixes, and exploring new networks over the last couple months. Here are the noticeable changes on the bridge since our last update:

• DM notifications for interactions from non-bridged users (more)
• Mastodon to Bluesky support in Bounce (more)
• Expand blocking to Bluesky blocklists, multiple at once, web UI, and more…
• Support setting Bluesky handle back to the default *.ap.brid.gy (more)
• More support for fediverse => Bluesky pinned posts
• Make images/videos on Bluesky more reliable:
  • Refresh them periodically
  • Handle the same file at multiple URLs
  • Upgraded to a paid CloudImage account for proxying Threads images/videos
• Customize Bluesky labels based on keywords in fediverse content warning (thanks @KDederichs!)
• Improve GoToSocial compatibility
• Bridge Web Monetization wallet addresses
• For Bluesky profiles bridged to the fediverse, make the link back to Bluesky “verified” (green check) in Mastodon
• Add support for new (invisible) website field in Bluesky profiles
• Web UI: improve handling of IDNs (domain names with emoji) and punycode
• RSS feeds: support application/rdf+xml
• Web UI: reload profile on login

Bug fixes:

• …for race condition on writing to Bluesky repos
• …for bridging Bluesky handle changes to fediverse Webfinger address
• …for bridging web posts, replies, etc after we’ve already seen them
• …for deleting bridged fediverse profiles on some servers
• …for bridging Bluesky profile pictures to the fediverse
• …for links in post text
• When there’s an unbridged dependency, only skip that one protocol, not all
• Add missing PropertyValue in AS2 @context
• …for duplicated images in posts bridged to Bluesky

Internal:

• Bluesky:
  • Reliability improvements for firehose server/client
  • Scale past ~10qps bottleneck in allocating sequence numbers (more)
  • implement listBlobs
• Expand continuous deploy flags
• Various cost optimizations added up to savings of 40-50%:

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!

Hi everyone! We’ve been working on a few big projects since our last status update, but we’ve also made progess on smaller improvements and bug fixes for Bounce and Bridgy Fed. Here are the noticeable Bridgy Fed changes since last time.

• When a bridged user receives a DM, reply and say “DMs aren’t bridged”
• Handle dependent activities that arrive in the wrong order, eg delete before create
• Rate limit activities per user. We still bridge everything, we just slow down users individually if they do too much too fast.
• Accept DIDs as well as handles in DM commands (thanks @tesaguri!)
• Revised “bridged by …” profile bio footer to say how to bridge yourself
• Interop fix for unfollows from Smithereen
• Interop fix for unusually shaped Delete activities from Mastodon
• Bug fix for sending webmentions for quote posts
• Bug fix for resolving handles and logging in with did:webs
• Bug fix for implied quote posts with unusual bsky.app links
• Bug fix for sending invite prompts to ineligible users
• Bug fix for unblocking users via DM when multiple block records exist for them
• Bug fix for deleting replies when their in-reply-to post is already deleted
• Bug fix for bridging profile updates from Bluesky
• Bug fix for posts with links to invalid URLs
• Fix rare bug that occasionally broke new web and Bluesky users signing up

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!

Hi everyone! It’s been a few months since last time, so let’s dive into another status update. The big new projects and features we’ve been working on are elsewhere or still baking, so it’s mostly smaller additions and bug fixes, but there’s still plenty of good stuff.

• On the fediverse, we now try to deliver replies to all upstream authors in the thread. This is complicated, and varies by ActivityPub implementation, but we now more closely match common inbox delivery and notification conventions, so fediverse users should now see and get notified of bridged replies more often.
• Hopefully fixed a persistent issue where replies, likes, reposts, and quotes sometimes wouldn’t get bridged to Bluesky if they post they depended on hadn’t finished bridging yet. Another complicated one, still keeping an eye on it for now.
• Web UI on fed.brid.gy:
  • Made login UX more forgiving
  • We now refresh profiles on login
  • Improved OAuth compatibility with more old versions of Mastodon
  • Fixed a bug in the activity logs on user pages
  • Fixed a bug with follower/following counts on networks where the user is no longer bridged
• Added support for fediverse admins to opt in users at the instance level, including automatic custom Bluesky handles. More details.
• For fediverse developers: added FEP-ffd proxy links to ActivityPub objects. More background.
• Made ATProto custom domain handles more case-insensitive
• ActivityPub: after Delete, Create or Update now undeletes
• Fixed Misskey and Sharkey interop for users with pinned posts
• Improved GoToSocial interop (thanks GtS!)
• Improved error messages for DM invitations

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!