Hi everyone! Welcome to another Bridgy Fed status update. We’ve been hard at work on upcoming projects since last time, but we’ve also found time to work on smaller features and bug fixes. Here are a few we’ve shipped recently: * In DM notifications for unbridged replies, show the reply and who wrote it * Improve migrating and Bouncing to the Atmosphere, and update your bridged handle * Worked with Phil (thank you!) to serve ATProto repo downloads on the cheap * Fedi => Atmosphere: * Bug fix for posts with over four images * Fix duplicate posts * Atmosphere => Fedi: * Bug fix for unlinked/trailing hashtags * Fix duplicated quote post links * Web: * Fix author handle on some webmentions from the Atmosphere * Improve reliability of post edits 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!

Check out the A New Social community on Discord - hang out with 2 other members and enjoy free voice and text chat.

Today, we’re announcing a bunch of migration features and improvements across Bridgy Fed and Bounce. The main goal we had with these latest updates was to make it so people can migrate in every direct...

Centering social media around people, not platforms

Over the last few months, instead of adding new features to Bridgy Fed or Bounce, I’ve been focusing on cost cutting. It’s not fun, exactly. I’d rather be building new things! But we’re a non-profit, ...

Centering social media around people, not platforms

Hi everyone! Here’s your semi-regular Bridgy Fed status update. We’ve been busy since last time! Our main focus over the last couple months has been cost cutting. We have an entire blog post on this coming up, but suffice it to say that we’ve had to work hard to keep costs under control while growing users and adding lots of new functionality. Our two biggest projects on that front were migrating our datastore to a cheaper configuration, which cut datastore costs by half, and optimizing ATProto `getRepo` calls, which sped them up over 20x and brought down our frontend instance count ~3x. We also shipped some great new features: * Long-form articles to/from standard.site on the ATmosphere * Bot accounts are now labeled as bots on the ATmospherePub * Improved DM notifications: added structured data, fixed cases where notifs were missing and overly eager * Domain-based exemptions from the 2-week post backdating limit * Bridged web sites now show `[Unofficial]` in their display names to reduce confusion. Web site owners can remove this by verifying their sites. …and bug fixes: * Missing profile picture updates * Webmentions from home page fragment URLs not bridged * h-feed to Atom conversion lost entry tags * SSRF protection for outbound HTTP requests and websocket connections 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!

Up until now, Bridgy Fed has only supported the bridging of microblogging content. Even when we bridged articles from the web or from Article types in ActivityPub, ATProtocol-based microblogs would on...

Hi everyone! Here’s your semi-regular Bridgy Fed status update. We’ve been busy since last time! The two big new features we launched were domain blocklists (GitHub) and responding to unbridged users (GitHub). We’ve seen good feedback and usage on both, especially responding to unbridged users. Please keep the feedback coming! We also significantly improved bridging speed, especially to Bluesky. For a couple months, it slowed down to an average delay of 3-5 minutes, with outliers that took so long that we occasionally dropped them entirely. Not good. We worked hard to optimize and managed to cut that average delay down to just 5-10 seconds, which feels way better. We shipped a bunch of smaller stuff too: * Bluesky standard.site support (still rolling out) * Improve pinned posts, notably when they were pinned before a user enabled the bridge * Fediverse: use Article `preview` field * Web UI: add buttons to unblock domain blocklists in settings * Web UI: bug fix for raw HTML appearing in some warning messages * bug fix for linking @-mentions of unbridged fediverse users * bug fix for Webfinger XRD output * Misc reliability improvements to our ATProto firehose server and client * Unfollowed everyone from the @ap.brid.gy Bluesky bot account. Its large number of follows (65k+) had unintentionally landed it on a handful of “follows too many people” automated blocklists. 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!

Last year, we launched a feature for Bridgy Fed that sent a DM of an hourly digest of interactions that we couldn't bridge back to your native platform. While that gave you visibility into interaction...

In November last year, we began developing additional user-facing moderation features for Bridgy Fed users. While blocking users across the bridge was always possible via DMs, we knew it would be easi...

I’ve just released Bridgy, a little side project I’ve been working on. Got a blog? Share your blog posts on social networks? Wish comments on those shared posts also showed up on your b…

Bridgy Fed has always had a simple way to block users over the bridge, whether the other user is bridged or not. If the user is bridged, you can use your native platform’s blocking features. If the u...

Today, we're excited to roll out the second Bounce Beta we announced at FediForum earlier this month. With this new release, you'll be able to migrate from Mastodon to an existing Bluesky, Blacksky, o...

So far, Bridgy Fed has been doing a smooth job of connecting users between ecosystems, enabling cross-protocol communication over the bridge. That said, there are limitations when a user who isn't bri...

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!

One of the most common questions we get here is, “can you help me connect all my different accounts?” You’re on Bluesky, and Instagram, and Mastodon, you make a video series on YouTube, you have a blog, sometimes you post on Reddit, and a while back you set up

Centering social media around people, not platforms