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]( )!
Congratulations to the Threads team on [launching fediverse follows]( )! Big step for the open social web. Among other things, this means that you can now bridge your [Threads account into Bluesky]( ) by following [@bsky.brid.gy]( ), and your [Bluesky account into Threads]( ) by following [@ap.brid.gy]( ). Exciting!
my wife wants to shave racing stripes into our cat AMA
Bridgy Fed fediverse => Bluesky bridging is currently paused. The Bluesky team has been [working on their relay]( ) to handle all their new growth, and they’ve temporarily stopped ingesting data from federated PDSes like Bridgy Fed while they finish that firefighting. Sorry for the inconvenience, all! Please send their team lots of #hugops! (Bluesky => fediverse bridging has struggled a bit too, but it should generally still be working.)
It’s not just you! [Bridgy Fed]( ) is badly behind right now. Started around midnight PT last night, task queue peaked at over 3M tasks (!), 7h delayed. Down to 2.5M now, working through the backlog. Not just organic growth, something unusual happened, but I haven’t been able to look yet. Hopefully soon. In an unrelated coincidence, I got pretty sick last night, and I’m still pretty out of it. Tough timing. Also, Bridgy Fed has decent observability and tools for these kinds of events, but I deliberately don’t set it up to page me in the middle of the night. It’s still [just one person’s side project, after all]( ). Feel free to [follow this GitHub issue for updates]( ).
Most of the time, I don’t feel like a technical wizard, or a product visionary, or an inspiring leader, or an empathetic community builder, or anything like that. Most of the time, I feel like a plumber. Just trying to keep the pipes hooked up, plugging leaks, keeping the raw sewage away from the drinking water. I’m ok with that.
[ ](image ) [Tomorrowland / Walt Disney]( ) People regularly ask me whether Bridgy Fed is ready to scale and support more users. It’s a technical question, but their underlying motivation is usually broader: they believe in the social web, and the [fediverse(s)]( ), and they want them to connect [everyone who’s willing]( ), across instances and networks and protocols. Right now, the answer is, I don’t know. It’s not a technical thing; as an engineer, that part is catnip for me. I’m ready to roll up my sleeves and dive in. The more difficult part is *organizational*. Right now, [Bridgy Fed is effectively one person’s side project]( ). I love building and running (and funding!) it, and I have no plans to change that. However, it has basically no organization, governance, or institutional structure. It’s just me. That’s ok! At least, as long as it continues to be one person’s side project. It’s growing, though, and people are starting to envision it, and bridges in general, as more important parts of the decentralized social web. Load bearing infrastructure. Stable, reliable infrastructure is hugely valuable. To do it right, you need stable, reliable organizational structure. You need people to dedicate their time and expertise, sustainably. You need funding, and institutional governance, and some amount of transparency. Right now, Bridgy Fed mostly doesn’t have those things. It’s one person’s side project. That could change! I’m open to it. *I don’t plan to lead that change myself, though.* I’ve enjoyed building it in my spare time for [many years now]( ), and I have no plans to stop any time soon. It is not [my career]( ), though, or my calling, or my life’s work. I’ve spent my last 10+ years in leadership, I’m comfortable with it, but this isn’t where I’m personally looking to do it. For me, Bridgy Fed just a fun, hopefully useful side project. I’ve been between gigs for a bit now, spending a lot of time on it, but that won’t last forever. I expect to take a real job again eventually, and when that happens, I’ll have way less of that time. [ ]( ) [xkcd: Dependency]( ) So, to anyone hoping Bridgy Fed will become core infrastructure for the social web: that is one possible future! The first thing we’d need is an executive director or CEO, someone who wants to lead its organization, product, and policy. Someone who’d build relationships with groups like [IFTAS]( ), the [SWF]( ), [Bluesky]( ), [IndieWeb]( ), and others. Someone who’d own fundraising, if necessary. (Funding isn’t the real problem here, though. I self fund Bridgy Fed right now, and I could expand that to help with staff and other costs.) This wouldn’t be a full time job; I expect it would only take 5-10 hours per week. It wouldn’t necessarily need a dedicated role or standalone organization, either. Bridgy Fed could live comfortably as one of many projects inside a broader group like IFTAS or the SWF, or even a benevolent company like [Flipboard]( ) or non-profit like [Ghost]( ). Another possible future for Bridgy Fed is the glide path it’s on now: one person’s side project. I can keep running it like this for the foreseeable future. Hopefully useful and stable, but definitely not core infrastructure. No real governance or institutional structure. In particular, as one person’s side project, Bridgy Fed would probably remain opt-in in most places. This post is not about [opt-in vs opt-out](https://wedistribute.org/2024/02/tear-down-walls-not-bridges/ ), or any other big policy or product decision, but it is about *who makes those decisions*, and *how they should be made.* Regardless of how public or global or searchable a network is, or how much it encourages tools to be opt-out – like Bluesky does – making Bridgy Fed opt-out anywhere would set more of an expectation that it’s core infrastructure. As long as it’s just my side project, I can’t satisfy that expectation. If you think Bridgy Fed needs to grow up and be real infrastructure, and you’re interested in possibly leading it as executive director, or adopting it into a bigger organization, or you know somone who might be, that’s a very possible future. [Drop me a line]( ), I’d love to talk. In the meantime, when people ask me whether it can scale, or switch to opt-out, or what the long term plan is, I now have something to point them to. Thanks for reading.