I don't like the use of the word "fight" here, but this is a good overview of the issues and what's at stake.
Money quote: "Soon, Meta’s Threads app plans to become interoperable with ActivityPub networks like Mastodon. Flipboard and #Automattic, owner of #WordPressDotCom and #tumblr are also betting on ActivityPub."
When he built a bridge to connect Bluesky to Mastodon and other ActivityPub-powered platforms, @snarfed.org@snarfed.org started a new chapter for the fediverse. The software engineer opens up to @mike about his rollercoaster ride in the latest episode of Dot Social:
Like, here's the thing: rather than harassment and brigading of one developer who is trying to solve a use case, why not focus your energy on an actual long-term solution.
Support a FEP, talk to the SWICG, file issues on the mastodon issue tracker or support issues there, go read about ZCAPs or the various writings on social networks of consent and the proposals around that
(Don't harass them either. Stop harassing people.)
Or you can just put the tag in your profile or block them
@verge Great episode! Truly embarrassing regarding the culture regarding the #BridgyFed mention. You would hope that adults could handle and behave themselves better, oh well.
Slowly, but surely my Mastodon posts (this one included) are showing up on Bluesky. Bridgy.fed kicks in. Thanks to @snarfed.org@snarfed.org for all the hard work.
I want to add my voice supporting Ryan Barrett's #bridgyfed project.
The #Mastodon#HOA has outed itself as intolerant & abusive as the worst of the twitter trolls.
The HOA tries to impose a minority view on the entire fediverse using abuse & viral outrage tactics in the face of software & protocols that do exactly the opposite.
I noticed this dynamic when I first joined & listened to the cultural differences.
It's now possible to connect #Bluesky and #Fediverse accounts together, and talk across a bridge! We get into the nuts and bolts of how it works, and what you can do to get started! #BridgyFed
A great breakdown of Bridgy Fed and the whole situation. I personally am excited for the project, as there are people I want to follow on #Bluesky and I also want them to be able to follow me, without me having to manage two accounts.
I hope you don't let people harrass you @snarfed.org@snarfed.org You're doing some really interesting work! (You also seem to be taking vitriol and feedback very well!) Good luck!
Apparently the #bridgyfed debate has moved on from the opt in or out debate (cause it's obvious the #fediverse is opt-out) to how this threatens the culture here. I agree, it does.
Do we want the culture here to be one which says you can't admin a server if you like Harry Potter? That you should be hounded if you don't tag or hide images properly? Where hosting nice but conservative accounts can get your server defederated?
We're finally getting to the crux of the issues here...
"#Mastodon is the most established decentralised #socialweb app to date. For anti-establishment Mastodonians, Dorsey’s involvement was strike one. Strike two came when #Bluesky decided to create its own protocol instead of using an existing one, like #ActivityPub. Now, the debate over #BridgyFed is something like a foul tip ahead of strike three."
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:
Have you heard about #BridgyFed? Using this free service, I have been able to link my four #Substack publications to the #Fediverse so that each now has a handle that can be followed on #Mastodon and other #ActivityPub platforms. Here they are:
Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/@border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@marcthiele) and @jkphl.is (@jkphl@jkphl).
Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE#backfeed ).
Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday!
This noob is testing the interconnectivity of the #Fediverse:
The word out there on the Fediverse make it seem as if all the different tools (Mastdn/P-tube/Lemmy/etc.) can interact with one another. But this is not the case, as some work both ways, whilst others only one way, or at all.
a) Using #Bridgyfed, to test between AT ( #BlueSky ) & AP protocols (Mastodon, etc.)
b) Meta's #Threads for testing with Mastodon.
c) Starting to test #Nostr with its peer-to-peer network.
TL;DR:
The #Fediverse holds a lot of promise, but it the ideal level of interconnectivity isn't there yet. (And yes, not all of them need to be able to connect and interact on the same level of details as with the others, as they are different tools.)
Using #Skybridge to see my Bluesky account in #Ivory to boost fed.bird.gy (#Bridgyfed) allowing me to see #Bluesky posts on #Mastodon, and vice versa. If I post something on Mastodon will it appear on Bluesky, and so appear on Mastodon, and so forth, in a mirror of infinite recursion?
#BridgyFed ist eine Brücke, mit der echtes Interagieren zwischen #Fediverse-Accounts und #Bluesky-Accounts möglich wird. Allerdings nur zwischen Accounts, die da aktiv mitmachen. Wie's geht?
Das Fediverse-Profil, dem ihr als Fediverse-User folgen müsst, damit Bluesky-User euch hier folgen und mit euch interagieren können: @bsky.brid.gy@bsky.brid.gy
Das ist ein #Bot. Nachdem man ihm folgt, folgt er zurück und richtet ein Bluesky-Handle namens @DeinFediverseHandle.Deine.Instanz.ap.brid.gy ein. Dieses Handle ist dann bei Bluesky auffindbar, und Bluesky-User können ihm folgen. Damit folgen sie dann euch hier und können eure Beiträge auch liken, boosten und kommentieren.
Umgekehrt müssen Bluesky-User folgendem Bluesky-Profil folgen, damit ihr ihnen von hier aus folgen und mit ihnen interagieren könnt: @ap.brid.gy
Auch das ist ein Bot. Auch er folgt dort auf Bluesky zurück. Und er richtet ein Fediverse-Handle namens @BlueskyUserHandle.bsky.social@bsky.brid.gy ein. Das ist dann hier auffindbar, und man kann ihm folgen. Auch so herum kann man dann hier Beiträge von dort liken, boosten, kommentieren.