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!
At this point, if you go to #Bluesky just to document bad things happening to that particular social network or to report back to #Mastodon what people on a social network say about people here… I envy the time you have at your disposal.
@fediversereport Thank you for sharing. It is exciting to see what is happening! I think your point at the end is really worth considering: is #Bluesky and the #ATProto interested in multiple apps or is it merely a vehicle for microblogging? I don't have technical background, but I suspect that the decentralization for BSKY is more for show than practice. Critique #ActivityPub all we like but I do think the commitment to platform diversity is there and is practiced.
Video, audio and blogging: Japanese Bluesky is building in the ATmosphere
When Bluesky dropped the invite code requirement early in 2024, it led to a big inflow of the Japanese community into Bluesky. At some point, they became the biggest community on Bluesky, with 43% of the posts being made in Japanese, compared to 34% in English. Over the last few months, the Japanese Bluesky community has build a variety of cool new tools, projects and platforms for the ATmosphere. Let’s take a look at three of them: Whitewind, a blogging platform, Bluecast, a social audio app, and Bluemotion, a video hosting platform.
Video with Bluemotion
Bluemotion is a video platform that integrates with your Bluesky/ATmosphere account. You log in with your Bluesky handle and (app)password, and get an overview of the videos hosted on the platform:
front page of bluemotion showing 3 cat videosThe basics of a video hosting platform are all there: you can browse through categories, see what other people have posted, and post your own videos. Where it gets really interesting is that the accounts that post the videos are easily recognisable as Bluesky handles.
Now let’s take a look at a video. On the left is the video on Bluemotion, on the right is the same video, but now as a post on the official Bluesky app.
2 screenshots of the same video, on the left of bluemotion and on the right of bluesky. it shows the same video and engagement numbersWhat is worth noting here is that this is the exact same post, as visible by the engagement numbers. You can interact with the post from the Bluesky app, but you can also boost and like it directly from Bluemotion itself. Now, the only difference here is that the official Bluesky app cannot play videos, so it is a link to the Bluemotion site instead. Still, its a great example of what you can build on top of the AT Proto. Bluemotion is made by developer So Asano.
Blogging with WhiteWind
WhiteWind (stylized as whtwnd.com) is a blogging platform build on top of ATProto. As with all the products in this article, you simply login with your Bluesky/ATProto handle and (app) password.
https://fediversereport.com/wp-content/uploads/2024/05/image-4-1024x568.pngLogging into WhiteWind shows you a front page with the latest and popular blog entries, as well as the ability to write your own blog posts. The integration with ATProto is visible in two different ways: first of all, your WhiteWind account is your ATProto/Bluesky account. Secondly, you can comment on blog posts with your account, and these are visible as a post on Bluesky as well. WhiteWind is developed by @K-NKSM.
Audio with Bluecast
Bluecast is an audio app build on top of ATProto. The idea is fairly simple, but well executed. Log in with your ATProto/Bluesky account, and browse the current live audio streams. You can also host your own live audio stream as well.
https://fediversereport.com/wp-content/uploads/2024/05/image-6-1024x748.pngWhat impresses me most about Bluecast is that it has managed to build up an active audience of users. By far the hardest part of building a social app is getting people to consistently use it. Audio apps build on top other other protocols (such as audon.space for the fediverse) have struggled to get people to use them, even though they work perfectly fine. For Bluecast however, every time I have checked over the last week I have seen active audio rooms and people using the app. Part of it is that developer So Asano has been running events with multiple streams after each other, with some 60 people tuning in.
Integrating ATProto into Bluesky
The developers have made some impressive new products. At the same time, their work also showcases some struggles for new developers building on top of ATProto. The developer of WhiteWind wrote a blog recently about their experience developing WhiteWind, and write: “My service’s data should be reaching Bluesky, but Bluesky doesn’t understand it and simply discards it. It’s true that I can improve the quality of the service by for example making the UI more beautiful, without relying on atproto. But if it is the only way, what is the point of using atproto in the first place?”
To understand the point they are making, first a quick and oversimplified explanation: A lexicon is part of the protocol, and defines what a post does and how it looks. The official Bluesky app has defined the lexicon for posts to be short posts, limited to 300 characters. Anyone can build their on app on top of ATProto, and define their own lexicon. You can create a Lexicon for long-form blogging, videos, or whatever you want. Importantly however, the official Bluesky app does not process posts with a different lexicon well.
This is the problem that the WhiteWind developer is referring to: WhiteWind has their own lexicon for long-form writing, which does not get processed by the Bluesky app. This is quite different from the fediverse, where long-form posts (from WordPress/Discourse/WriteFreely/etc) can show up in your microblogging app, such as Mastodon. I connected my WordPress blog to the fediverse, and now my blogs show up as full text in the feed of people who follow me, in turn gaining me quite some extra organic reach. This is not possible with AT Proto,new users will still have to visit your website to start using it, making growth for a new product that much harder.
At the same time, Bluesky developers are understandably wary of the Bluesky app becoming an ‘everything-app’. The goal of the Bluesky company is to build a decentralised protocol after all, and the Bluesky app is explicitly an app for microblogging. Bluesky users have regularly criticised the move by X to promote longer-form writing as well, indicating that native long-form writing in Bluesky might not even be appreciated by a part of the userbase.
Overall it points for an interesting point in time for the ATmosphere: Japanese Bluesky developers have build some impressive new products on AT Proto, but is the network interested in adopting other products beyond Bluesky’s own microblogging?
Hat durchaus noch Probleme, aber prinzipiell funktioniert es und das ist natürlich richtig cool. Gibt schon Accounts da drüben, denen ich gerne von hier folgen würde. Meiner ist schon verbunden: @fingolas.bsky.social@bsky.brid.gy
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
I know have separate Mastodon lists of bridged #BlueSky accounts I follow here (thanks @snarfed.org@snarfed.org), Flipboard accounts I follow here (thanks @mike), federated WordPress blogs I follow here (thanks @matthias ), federated Podcast feeds I follow here (thanks @dave ) and Threads accounts I follow here (thanks @jessel & @pcottle ) ... and that fact that we can do this at all, and now feels like the new normal, should be an Internet history milestone of some kind.
Jack Dorsey is furious that #Bluesky has attracted "very very common" people. He also doesn't like the idea of moderation tools facilitating the banning of racists.
All these tech billionaires are like a version of the movie Big, in which a pre-adolescent boy wakes up in the body of an aging Howard Hughes. Or Colonel Kurtz. Or a sardine. #JackDorsey
Jack Dorsey interview post-#Bluesky. Whatever you think of him, his views on why he helped getting Bluesky started in the first place are interesting. I wonder which of those might apply to the Fediverse (which he doesn't mention at all).
Talk about decentralization: I'm quote-boosting a skeet from Bluesky's CEO that federated via #BridgyFed talking about an article where Jack Dorsey talked about #BlueSky and #Nostr. 😱
(It's not peak decentralization yet because not bridging my posts back to Bluesky. If you want to do that, here are the instructions to opt in to Bridgy Fed. On the other hand, if you don't want to see any posts that originated on Bluesky, I'm pretty sure you can just block the domain bsky.brid.gy.)
Former CEO of Twitter wanted to build a social protocol no-one can control, like SMTP or HTTP for social media. Bluesky’s ATProto was supposed to be an open source protocol that Twitter could eventually utilize, but then Musk happened and Bluesky started taking it to the wrong direction and everything fell apart in Dorsey’s mind.
A very revealing interview. I now see even more future in W3C’s ActivityPub.