@mackuba what's your point? guessing this isn't that recent and I'm not sure 30% was a particularly unrealistic prediction considering most startups fail and we've already seen multiple twitter replacements fail too.
Good on Bluesky not having run out of money yet but I certainly don't think they've yet really found a good way to monetize or a big enough userbase so the clock is absolutely still ticking on that VC money requiring them to put up or shut it.
@mackuba also, I'm sure you know @evan has a non-threads fediverse account too even though he happened to post that message to threads so there is no need to ping him on threads only.
@vetehinen@evan It's from February, around the time when they enabled open signups and shortly before they enabled third party PDSes for limited testing.
I saved it because I've been tracking the progress of Bluesky closely since last spring, I know what devs are working on, and at that point I could have bet real money that they would enable bridges like this in the next few months. Implying that they'd somehow maliciously block it meant that someone doesn't know that much about Bluesky.
@mackuba@vetehinen They definitely did block federation with other nodes, and disallowed bridges. The fact that we're talking about new bridges existing is because they have been disallowed up until now.
I really appreciate the work going into bridging with Bluesky and Nostr.
I still think that bridges are not going to be important long term. The momentum is with ActivityPub.
@evan@vetehinen I mean, they weren't blocking bridges specifically I think? (Were they any attempts other than Snarfed's?) - they just hadn't enabled federation at all yet at that point. I think there's a difference between "they are blocking bridges" and "federation isn't working yet"…
It wasn't enabled because it wasn't ready yet, but they had announced late last year that it would be enabled in early 2024, and it was, all according to plan (actually earlier than I expected myself).
Add comment