everyone’s always donating their body to science when they die. I want to donate my body to art
[](image ) image
ah, that wonderful age-old Christmas tradition, the cardboard boat race
It’s time for a special holiday [Bridgy Fed]( ) status update! [Since last time]( ), we’ve been working mostly on getting [A New Social]( ) off the ground and on Bridgy Fed internals. Specifically, my development focus for a while now has been [cost cutting]( ). I fund Bridgy Fed myself right now, which I’m happy to do, but it costs more to run than it should, probably by 2-3x or so. (We do plan to fundraise for A New Social eventually and fund Bridgy Fed there instead! Including individual donations, among other sources. [Stay tuned for more news when we have it.]( )) In the meantime, I’ve been pushing the optimization boulder uphill, making slow progress. I’m currently struggling with one big issue: getting caching working in [ndb]( ), our ORM. ndb can cache both [in memory]( ) and [in memcache]( ). We configure it to do both, but [it doesn’t seem to be using memcache in production]( ), and I’m not even sure it’s caching in memory there either. If you have experience with ndb, [Google Cloud Datastore]( ), [Memorystore]( ), or related tools, please [take a look]( ) and let me know if you see anything obviously wrong! This also means that I haven’t had much time to spend on features, bug fixes, or other user-visible updates. I’m the only developer on Bridgy Fed right now, and I’m only part time. I’d love help! It’s [entirely open source]( ), so if you’re interested, check out the [open issues]( ), feel free to dive in, and [ping me on GitHub]( ) if you have any questions! Having said that, I have done a bit besides cost cutting [since last time]( ): <li><a href="https://github.com/snarfed/bridgy-fed/issues/1411">Generate link previews (aka embeds) on Bluesky.</a></li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1210">Launch Threads support!</a> Just via normal ActivityPub, nothing special, but I worked with them a fair amount on interop.</li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1490">Improve sign-up flow for web =&gt; Bluesky bridging.</a></li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1009">Try harder to redirect fediverse @-mentions of bridged users to their web site or Bluesky profile.</a></li> <li>Reduce confusion on the <a href="https://fed.brid.gy/">home page</a> sign-up form by <a href="https://github.com/snarfed/bridgy-fed/issues/1458">detecting web sites that are already fediverse instances</a>.</li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1446">Let fediverse accounts re-enable the bridge</a> even if they <a href="https://github.com/snarfed/bridgy-fed/issues/1130#issuecomment-2430525165">disabled it before October</a>.</li> <li>Improve interop with <a href="https://github.com/snarfed/bridgy-fed/issues/1482#issuecomment-2484901105">Friendica</a>, <a href="https://github.com/snarfed/bridgy-fed/issues/941">Hubzilla</a>, <a href="https://github.com/snarfed/bridgy-fed/issues/1093#issuecomment-2433794322">Misskey/Sharkey</a>, <a href="https://github.com/snarfed/bridgy-fed/issues/1474#issuecomment-2471681545">Sharkey</a>, <a href="https://github.com/snarfed/bridgy-fed/issues/1493">WordPress Friends plugin</a>, and <a href="https://github.com/snarfed/bridgy-fed/issues/1492">GoToSocial</a>.</li> <li><a href="https://github.com/snarfed/bridgy-fed/security/advisories/GHSA-37r7-jqmr-3472">Improve authorization to prevent a cache poisoning attack.</a></li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1268">Improve</a> <a href="https://github.com/snarfed/bridgy-fed/issues/1458#issuecomment-2504711399">DNS</a> <a href="https://github.com/snarfed/bridgy-fed/issues/744#issuecomment-2516099779">scaling</a> for Bluesky handles.</li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1419">Populate the <code>discoverable</code> and <code>indexable</code> flags on bridged ActivityPub actors.</a></li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1206">Misc bug fixes for web sites on www subdomains.</a></li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1367">Fix rare bug where we occasionally missed bridging posts or other interactions to Bluesky.</a></li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1361">Fix rare bug where we occasionally missed bridging deletes.</a></li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1595">Continued</a> <a href="https://github.com/bluesky-social/atproto/discussions/3214">debugging</a> <a href="https://github.com/snarfed/bridgy-fed/issues/1202">of</a> accounts bridged into Bluesky that occasionally get stuck and stop bridging.</li> <li><a href="https://github.com/snarfed/bridgy-fed/issues/1465">Lots of</a> <a href="https://github.com/snarfed/bridgy-fed/issues/1467#issuecomment-2467836269">docs</a> <a href="https://github.com/snarfed/bridgy-fed/issues/1531">improvements</a>.</li> As usual, feel free to ping us with feedback, questions, and [bug reports]( ). You can follow the [*now* label on GitHub]( ) to see what we’re currently focusing on. See you on the bridge!
fog over the bay was intense this morning [](image ) [](image )
Excited to announce that I’m teaming up with [Anuj Ahooja]( ) on a new non-profit for the open social web, across protocols, with Bridgy Fed as its first main project! [Introducing A New Social.](https://www.anew.social/hello-social-web/ ) When I posted *[Possible futures for Bridgy Fed]( )* a while back, I was surprised and gratified by the outpouring of support. So many of you really believe in it and want it to survive, grow, and find a stable footing beyond the useful little one-person side project it is today. Some people stepped up even further and said, “I’m willing to put the work in and actually help build, drive, and even lead this.” Anuj is one of those people. He’s a renaissance man who’s worked on the fediverse and open social web for many years at [sub.club](https://sub.club/ ), [Flipboard]( ), and more. He’s [written at length]( ) about the potential he sees in the open social web, across all sorts of networks – “people, not platforms!” – and how we have an opportunity now that we haven’t had in a long time. And there are so many more of you, across the space, who’ve joined and committed to supporting us! We’re truly humbled and grateful. We’re still only at the very beginning, we have a lot of work to do, but we’re excited to get started. Wish us luck, and please [reach out if you want to get involved]( )!