I just wish this was a native function of one or both platforms. What a feather in Bluesky's cap to say that they're interoperable with Threads, for instance.

[–] fossilesque@mander.xyz 8 points 2 days ago (1 children)

People are repeating the same problems of Twitter.

[–] ilinamorato@lemmy.world 2 points 1 day ago* (last edited 1 day ago) (1 children)

Yes, although the protocol is already open, which I think mitigates the risk slightly. Bluesky is also organized as a public benefit corp, which mitigates the risk almost not at all but is interesting. If Bluesky begins to go the way of Twitter, other corporations or entities can make interoperable replacements easily. That was not so for Twitter.

But in general, yes. This is the same song but a different verse. People have been so blinded by the brokenness of the internet as it is now that an interoperable protocol doesn't make any sense to them.

[–] minzastro@programming.dev 3 points 1 day ago

I fear that "public benefit corp" will be less and less "public" and more and more "benefit" as time passes. And opening the code does not help much if a second, third and nth server is not there and nowhere on the horizon. By the time the need arises it might become prohibitively expensive or even technically impossible to deploy a new server, as features unused are also poorly tested.

[–] Fitik@fedia.io 3 points 1 day ago

Bridgy Fed creator thinks about making it opt-in by default on the BlueSky side, there's a discussion on GitHub that you can see there

https://github.com/snarfed/bridgy-fed/issues/1471