There are a lot of companies and ideas competing for space on the post-Twitter internet, and Jay makes a convincing argument that decentralization — the idea that you should be able to take your username and following to different servers as you wish — is the future. It’s a powerful concept that’s been kicking around for a long time, but now it feels closer to reality than ever before. You’ve heard us talk about it a lot on Decoder: the core idea is that no single company — or individual billionaire — can amass too much power and control over our social networks and the conversations that happen on them.
There are quite some reasons that leave me very cautious about Bluesky, one being for sure the fact there's one commercial entity currently backing this service / protocol, especially one that has risen from the same ecosystem that caused a lot of the trouble we do experience with current social media platforms. But, I've then and now been at odds with ActivityPub as a protocol, which gets worse the more I dig into it, and from that perspective, it seems the AT crowd gets a lot of things right, considered a lot of things that don't just seem obvious at least in the 2010s but actually surprising to see them missing from ActivityPub, a spec that has been established at roughly the same time: Full account portability (the idea of comparing personal data, conversations, comments, posts, ... to a github repository which "of course" you want to easily be able to take, backup, move around, ... seems both stunning and painfully trivial), support of custom domains for users (which Tumblr has already been supporting for years now), distributed curation and moderation (because most obviously community structures will be different to server or domain structures and not necessarily live on one instance exclusively) - in a way I really do hope they "show don't tell" by submitting that protocol to some standardization body anytime soon. Maybe this, too, could provide a good option for the "open" fediverse to counter the problems that might arise the very moment platforms like Meta / Threads fully embrace ActivityPub. (I also found it rather interesting to listen to what she had to say about why Meta might be more into ActivityPub than AT - being "server-centric" rather than "user-centric" - but that might just be a loose end of things.)
I logged into my Bluesky account this morning to see what was going on with the platform (and to post a blog link). Most of the people who I follow haven’t posted in months, others have deleted their accounts completely.
#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.
This is from posting pretty much solely on #MECFS , #LongCovid and related conditions and to a lesser extent chronic illness in general, which shows it is possible to build up followings on them, in case people either gave up on them or never tried.
I'm not exactly sure how it's happened, but it's pretty cool I can see Bluesky accounts talking on here.
It seems a shared interest in the misfortunes of the Nazi Bar has bridged the technical divide somewhere. #Twitter#Mastodon#Bluesky
At this point, Twitter and BlueSky are virtually identical, except there's a bit more public info about users. So maybe it's worse? In any event, the whole plan all along was to create the illusion of difference and "starting over" by simply swapping a platform. Fascinating how gullible most people are.
What a pleasant surprise to have found an app (@openvibe) that aims to bring together all decentralized social networks in one! It saves you the trouble of having to post on each one separately. For now, it works with #Mastodon and #Nostr, but they plan to add #Bluesky and #Threads. Very good news! Check it out if you can. 😉
My biggest #gripe with #Mastodon is reach and the ability to discover stuff outside of chronological scrolling. Lists in #BlueSky make that better. Imho the algorithms in #Threads are too intrusive.
If there were simpler ways to connect with different topics on here it would make it excellent, to me at least. I guess it might come down to why you use different social media.
J’ai jeté un œil à Bluesky (vu qu’apparemment c’est trop woke pour Jack)
Alors oui c’est super simple (centralisation oblige) et y’a des bonnes idées :
personnaliser l’ordre d’affichage des réponses (chrono ou anté chrono)
bloquer par défaut les players externes (youtube, spotify…)
masquer son compte aux gens non connectés
MAIS.
Ben c’est vide. Au moins autant qu’ici. La seule diff c’est que quand t’arrives l’algo te pousse du contenu. Alors qu’ici ta TL principale est VRAIMENT vide.
Je me dis que si c’est un des freins à l’adoption (en plus du choix de serveur) il suffirait de charger la TL locale voire la fédérée par défaut à la création d’un compte.
Ou mieux peut-être, un message qui dit “votre home est vide pour le moment, mais viendez dehors c’est animé”
UI differences are a big factor in the success/failure of decentralised federation of diverse platforms and content
And this seems a good example: bridged #mastodon posts onto #BlueSky which has a lower character limit than Mastodon.
So, just like #lemmy posts on mastodon, you don't get the full content of the post (which ends with an abrupt ellipsis here) and have to take a link to the original platform.
However powerful the underlying protocols, this isn't far from screenshots.
A nomenclature of 'Blue Moon' almost never means a Moon of a blue color but with the summer nights, a literally blue appearing Moon, or Moon in the daytime is a fun one to spot. The northern hemisphere was showing off a bit before sunset, and with the May 23 full Moon so close I couldn't resist a few pictures. Happy lunar viewing! #astronomy#Astrodon#moonlight#lunar#bluesky#bluemoon
<a class="invalid-href" rel="noopener noreferrer" target="_blank" title="Protocollo collegamento non valido">L'aggiornamento di Ryan Barret sul bridge con Bluesky</a>
Di seguito il post di @snarfed.org@snarfed.org che dimostra una non comune efficacia nella più trasparente comunicazione dello sviluppo e aggiornamento del bridge tra #Fediverso e #bluesky
Tempo di aggiornamento dello stato del Bridgy Fed! Sono state un paio di settimane impegnative. Sono felice di riferire che ho fatto notevoli progressi su tre dei miei quattro obiettivi dell'ultima volta (affidabilità, ritardi e bug) e ho migliorato una serie di altre cose lungo il percorso. Ecco un esempio:
Modificato Bluesky => fediverso dal polling al firehose . Ciò lo ha reso molto meno traballante e ha ridotto il ritardo di 5-15 m a pochi secondi.
Risolto il problema con fediverse => Bluesky rimaneva bloccato per molti account. Ho preso alcune scorciatoie nella mia infrastruttura Bluesky e sono tornate a mordermi. C'è ancora del lavoro da fare, ma i problemi visibili agli utenti dovrebbero essere in gran parte risolti.
Vari problemi con la ricerca degli account bot, il loroseguito e l'avvio del bridge .
Immagini fisse in Bluesky => post fediverse.
Implementata l'eliminazione dei post, Bluesky => fediverse. (Fediverse => Bluesky stava già funzionando.)
Risolto il problema relativo al bridging delle risposte in entrambe le direzioni.
Risolti collegamenti , menzioni e hashtag , in entrambe le direzioni . Ancora alcuni pezzi rotti qui, in particolare i riferimenti a Bluesky => fediverse, ma per il resto ora dovrebbero essere molto migliori.
A parte le manichette antincendio, un'area degna di nota su cui non mi sono ancora concentrato è l'infrastruttura . Finora la scalabilità è ok, ma potrebbe essere molto migliore e molto più efficiente. Dovrò lavorarci su presto. Se noti che passa un po' di tempo senza molti miglioramenti visibili all'utente, probabilmente è proprio quello che sta succedendo.
Altrimenti, grazie per tutti i feedback, le domande e le segnalazioni di bug ! Per favore, continuate a farli arrivare. Come sempre, puoi seguire l' etichetta now in GitHub per vedere su cosa mi sto concentrando. Ci vediamo sul ponte!
So Ryan, thank you for this most valuable tool to bring people around the globe together in #DeSoc - creating (and curating, as you have) ***Bridgy_Fed is one of the very best things that the Fediverse has to offer people on both sides of the protocol divide, and I really don't think that there are enough Thank you's to go around for all of the selfless effort you've put into this service.
So as meek and perhaps insignificant as it may sound, THANK YOU!