The #Bridgy#BlueskyBridge is great from the Fediverse side, but the #Bluesky side is still missing a lot. Posts longer than the limit just get truncated; wouldn't a Read More link be better? And self-replies don't seem to get bridged at all, so threads don't work.
#Bridgy became quietly available for people to test, but as bridged posts started to appear, other people became aware and more people started to test and use the bridge.
To make your fediverse account available in Bluesky, you’ll have to follow this account: @bsky.brid.gy@bsky.brid.gy
The same thing that drove me nuts about the BridgyFed/BlueSky bridge discourse also drives me nuts with the Threads discourse. :neofox_what: Why isn't there a fediblock level that lets admins default to suspending a server, but allows users to opt back into federating with them? Is there a technical reason for it?
I really don't think it should've been on the BridgyFed developer to build an opt-in system that rightfully should've already been in Mastodon, the same way I don't think blocking Threads outright is the best solution (granted it's better than openly federating, hence why they're suspended here). Why doesn't Mastodon have a built-in system for letting users opt-in to federating with a server? :confused_dog:
This #Bridgy nonsense is exactly the reason why #Mastodon is doomed to fail unless something changes. The whole “not in my back yard” bullshit is starting to get really old.
When your code violates the social norms of a community, you could learn that code comes after people. Or you could insist that just because you CAN you don’t need to care about that part at all and just use technical blah to justify your actions. Simple. #bridgy
If anyone had paid attention in psychohistory class, Hari Seldom would have told you that the current #bridgy uproar was unavoidable. SOMEONE was bound to make a bridge to BlueSky as soon as they opened up.
And, SOMEONE was bound to complain about it from a position of fear and ignorance.
I just want to say that @snarfed.org@snarfed.org has done tons good work for the Fediverse, and I appreciate his latest project.
I mean I just told people in that #GitHub thread to stop with the threats of suing/litigating against the #bridgyfed developer and the #FLOSS/#FOSS project and I got instantly dunked on. The initiator of the issue got dramatic, despite them not really giving out legal threats to the dev (like why did you feel hurt by that generalistic statement? :SanaeConfuzzled:) I guess it's easy for the #fediverse to just not care how such a litigious attitude can be damaging. I mean, who would want to work in such an environment knowing that people around you want you jailed? :reimu_sigh:
We're fucking lucky that the developer gave us a heads up, an approximate timeframe (where the launch is at least a month away), and was mature in their responses. And even more lucky that despite all those legal threats and mudslinging the dev still continued engaging respectfully with the criticisms and offered an opt-in method that people I knew were vocal against the bridge's opt-out, accepted. Seriously, @snarfed.org@fed.brid.gy deserves some credit for keeping up a cool head and rest from all of that mess.
Yet most of those vocal detractors couldn't just resist acting like immature people throwing out #GDPR and comparing the dev to rapists in an effort to scare them out of fedi. One of the #ActivityPub authors/founders even had to show up in the thread to clarify how those detractors got their understanding of how the fediverse works wrong. :ablobcateyeroll:
In light of current events with snarfed.org and brid.gy fiasco, you can use this tutorial to block by yourself both of them even if there is no reachable account on some of these domains:
#FediBlock snarfed.org and brid.gy for bridging fediverse folks to Bluesky against their will (and in likely contravention of GDPR in the EU) with typical Silicon Valley techbro sense of entitlement:
“[O]pt in results in far fewer users, and users are critical for a bridge to be useful.”¹
PS. I just suspended (domain blocked) both snarfed.org and brid.gy from my personal fediverse instance and saw that there was already one account from one and eleven accounts on the other so my account was apparently already being bridged without my consent.
Those links are now severed and they never should have existed without my knowledge or approval to begin with.
I am not #fedismart enough to figure out how to block those silly #bridgy domains. I mean I blocked snarfed.org but what about the others? I need to find an account on one of them first before I can select "block entire domain"? #fedihelp?
Seit letzter Woche braucht man keinen Invite-Code mehr um sich bei Bluesky anzumelden, die wesentlich spannendere Info steht aber, wie beiläufig erwähnt, im letzten Abschnitt:
This month, we’ll be rolling out an experimental early version of “federation,” or the feature that makes the network so open and customizable. On Bluesky, you’ll have the freedom to choose (and the right to leave) instead of being held to the whims of private companies or black box algorithms. And wherever you go, your friends and relationships can go with you.
Ich bin gespannt wie Bluesky federation umsetzen wird. Auf mich wirkt das ATProtocol immer noch viel zu kompliziert und „overengineered“, aber vielleicht ist das ja auch gerade der Vorteil gegenüber ActivityPub.
Ich hatte vorgestern einen kleinen Plausch mit @deadsuperhero für den Decentered Podcast, in wir unter anderem auch über die Schwierigkeiten bei der Implementierung von ActivityPub sprachen. Da WordPress in vielen verschiedenen Umgebungen laufen muss und sich die Konfiguration des Webservers, die PHP Version, das Caching, die Interferenz mit anderen Plugins und andere spezial Fälle nicht seht gut abschätzen lassen, ist es sehr schwer komplexere Funktionalitäten umzusetzen.
Ein Beispiel: Im Gegensatz zu OStatus, wo die Distribution von neuen Inhalten über PubSubHubbub (jetzt WebSub) geregelt wurde, ist bei ActivityPub der Service selbst dafür verantwortlich. Ein direktes Verteilen der Inhalte, direkt nach dem Veröffentlichen, würde bei großen Follower zahlen, den Prozess unnötig in die Länge ziehen, oder könnte sogar zu einem Fehler oder einem kompletten Abbruch führen. Um dem (so gut es geht) entgegen zu wirken, wird der Prozess asynchron über WP_Cron abgearbeitet. Leider ist aber auch das keineGarantie für einen fehlerfreien Ablauf (Siehe Ende des vorherigen Absatzes).
Lange Rede kurzer Sinn: Abhängig davon wie simpel ein Personal Data Server kurz PDS aufgebaut ist, könnte Bluesky vielleicht doch interessanter sein als ich ursprünglich angenommen habe.
For our third episode of Decentered, we talked to Ryan Barrett, the creator of Bridgy Fed! Ryan has a lot of experience in working with a variety of decentralized social web protocols, including IndieWeb, ActivityPub, AT Protocol, and Nostr, and has a lot of interesting thoughts on making them talk to each other.
Hi! I’m Ryan. I’ve been building social network bridges and related tools for over 12 years, including Bridgy, which connects personal web sites and blogs to centralized social networks…
The #IndieWeb service #Bridgy is ready to handle bridge AT protocol and ActivityPub protocol posts and replies once federation is enabled in production (already working in sandbox test server).
The format will be:
To follow a #Fediverse account from BlueSky / AT protocol: <username>.<server_domain>.ap.brid.gy
To follow a BlueSky / AT protocol user: <username>@atproto.brid.gy
Example: @atp.youronly.one@atproto.brid.gy
This allows users from each side to see new posts and to reply to these threads.
What is more interesting is that, if you have IndieWeb support on your website or blog, you will see comments from BlueSky / AT protocol appear as a comment, thanks to #Webmention. It is already possible to do this with Fediverse / ActivityPub. ^_~
OC Tear Down Walls, and Build Bridges (wedistribute.org)
A libre networking project that's designed to bridge protocol spaces together announced its progress and intentions, and Mastodon users freaked out.
OC Decentered S1E3: Ryan Barrett Has a Bridge to Sell Us (wedistribute.org)
For our third episode of Decentered, we talked to Ryan Barrett, the creator of Bridgy Fed! Ryan has a lot of experience in working with a variety of decentralized social web protocols, including IndieWeb, ActivityPub, AT Protocol, and Nostr, and has a lot of interesting thoughts on making them talk to each other.
Re-introducing Bridgy Fed (snarfed.org)
Hi! I’m Ryan. I’ve been building social network bridges and related tools for over 12 years, including Bridgy, which connects personal web sites and blogs to centralized social networks…