Well, now that we can do video, it means this video can be posted here, which apparently started over on the other site. Noah Garfinkel noticed that Trump's claim about eating cats and dogs fits with the Peanuts theme song & then someone made a longer version of it.
@mmasnick.bsky.social @mike Is the bridge two-way? In other words, can you see this comment on blusky? Or is it one way like the threads.net bridge?
@bhawthorne @mmasnick.bsky.social yes. I replied to Mike from Flipboard and he replied to me from Bluesky. It’s super cool. I wish it was opt out and not opt in so more people could benefit.
@mike @bhawthorne @mmasnick.bsky.social
@snarfed.org Are there any plans to make #BridgyFed opt-out?
@mike @bhawthorne
I know how my instance sustains itself financially. I know it will never allow ads and subscriptions and scummy things.
Bluesky, however, is a mystery. It has over 10 million members, gifs, videos, DMs... How is the business run? No one has been able to give me a definitive answer.
@adrianmorales @mike The great thing about federation and bridges is that I don’t have to care how anyone else’s instance or service is run. I know how Jerry runs infosec.exchange, and that’s really all that matters to me.
I am happy that I can now interact with (some) people over on Bluesky who prefer a more corporate approach [shudders], but I am equally glad that their 10 million people are not all trying to squeeze into our instances! Sure, they will eventually succumb to the inevitable enshittification as the Bluesky investors start demanding returns on their investments, but that’s their problem, not mine. And if Bluesky starts leaking shit into the Fediverse, we have the tools to fix that.
It’s just like Threads.net. Everyone was all worried about them shitting ads into our streams, but they haven’t even succeeded in making their bridge two way!
(Also, minor nitpick, Threads isn’t bridged to the fediverse, it’s just federating via AP normally like any other instance.)
@snarfed.org I’d call threads.net a bridge. Just like bsky.brid.gy speaks AP to the fediverse and AT to bsky, threads.net speaks AP to the fediverse and who knows what to their internal servers. Threads.net is still only a one way bridge as far as I know.
The difference with bridges in my mind is that fediverse instances – mastodon.social, threads.net, etc – host users and their data. Bridges, on the other hand, don't. They just translate profiles and data that are hosted elsewhere.
(You're right that Threads's AP implementation is incomplete though! They do now show Threads users replies, likes, and reposts from the fediverse, so it's somewhat bidirectional now, but not all the way yet.)
@snarfed.org Do we know anything about how threads is architected? I have assumed it was just a branch from the Instagram code, and they are still building the ActivityPub/Streams bridge to it. I didn’t know replies went too now. That’s new.