Lazarou (@Lazarou@mastodon.social)
Bluesky has automated it's Reply Guys, will the contagion spread? đ
Show Original Post
TirotG (@TirotG@mastouille.fr)
#Bluesky s'apprĂȘte Ă lancer #Flashes, une application de partage de photos qui vient comme une #alternative aux plateformes centralisĂ©es comme #Instagram. Flashes entend bien donner davantage de contrĂŽle aux utilisateurs.
Source : MĂ©lina Loupia | Clubic
https://www.clubic.com/actualite-550394-apres-twitter-bluesky-s-attaque-a-instagram.html
Show Original Post
jelloeater (@jelloeater@mastodon.social)
https://www.sbnation.com/nfl/2025/1/22/24349479/nfl-ban-bluesky-social-media-elon-musk-nazi
#bluesky #nfl
Show Original Post
asm0dey (@asm0dey@fosstodon.org)
Iâve just done my #eXit! the X exodus is massive. Don't lose any of your followers. Thanks to #HelloQuitX I've registered 2616 new passengers for a journey to #BlueSky & #Mastodon. Join us on https://app.helloquitx.com and automatically find your communities on #January20!
Show Original Post
robert_winkler (@robert_winkler@mstdn.social)
After analyzing the guest list the #Trump inauguration event, I cancelled #BlueSky. Although a Social PBC, its location in the #USA presents a risk for its #independence. I'm so sorry to state that, because I was born in a #democratic Germany, thanks to the #USA.
Show Original Post
notes (@notes@catodon.social)
@tasket (sorry for the bsky mention, *key is buggy with handles with special characters)
also don't quote me on this but i think the platforms themselves are centralized. like i don't think you could make another social network on ATProto and have it communicate with Bluesky outside of everything that transfers over when you join it (because of data portability, i think)
i'm gonna repost this actually. can anyone confirm if this is true (or if i'm at least in the right track) or not? #bluesky #atproto
Show Original Post
txt (@txt@fedibird.com)
The number of Bluesky users has exceeded 28,800,000! #bluesky #bsky #fedibird
Show Original Post
txt (@txt@fedibird.com)
Blueskyăç»éČè æ°ă2880äžäșșăçȘç ŽïŒ #bluesky #bsky #fedibird
Show Original Post
atproto-explained-lexicons-and-video (@atproto-explained-lexicons-and-video@fediversereport.com)
ATProto Explained â Lexicons and video
With the US news around TikTok, Bluesky and AT Protocol (ATProto) has seen a surge in interest in building video apps on Bluesky and ATProto. Weâre seeing two different approaches: projects that build an app to display videoâs posted on Bluesky (such as Skylight), and projects that are building their own video platform (such as reelo). The difference between these two approaches gets expressed by people asking the question: âdoes the project have their own Lexicon?â
In last weekâs newsletter, I wrote this deep dive explaining how Lexicons are part of ATProto, and what they do. Lexicons are a part of the protocol that are not widely known, but their presence has major impact on how people experience the network. Specifically, Lexicons explain the major difference between two different approaches people are taking to build video apps on ATProto. Here is the deep dive, slightly edited, and expanded upon at the end to further explain their impact on how people are building video apps.
On a high level: Lexicons are the part of ATProto that specify how an âobjectâ on ATProto works. For example, the Lexicon for a Bluesky posts specifies that it has to be contain text, that it might contain an image. Technically that makes Lexicons about data structures, but it also makes Lexicons about power: defining how an object work can have big impact on many people and projects.
To explain what Lexicons work, first a simplified explanation of ATProto. There are two core parts: A Personal Data Server (PDS) which contains all your data, and AppViews, apps/sites that take all public data and display it in a useful way.
A PDS can contain any sort of data. It can contain a microblogging post from bsky.app, and it also can contain a recipe from recipe.exchange. The dream of ATProto is that someone else can build their own microblogging platform on ATProto, and reuse the same data and social graph by using the data that is already on the PDS.
If someone were to build another microblogging app on ATProto, lets call it GreenField, they would look at the data in the PDS, and see that Bluesky already has formatted the data related to Bluesky in a specific way. You can see what that looks like in reality here by using PDSls. The GreenField app wants to display a post made by someone on Bluesky, so it would look at the data that is formatted under app.feed.bsky.post. This is a Lexicon, created by Bluesky PBC, and Bluesky PBC has determined that post made by with the Bluesky app all follow the format that is specified by app.feed.bsky.post.
So far so good, you open the GreenField app, log in with your ATProto (aka Bluesky) account, and you see the posts made by your friends. Now you want to make a post yourself using the GreenField app. This is where GreenField will have to make some interesting decisions. GreenField can store this post as a app.field.bsky.post in your PDS. People who are on the Bluesky app can now see the post youâve made using the GreenField app, great. But what if the GreenField app wanted to do a few things differently from Bluesky? For example, what if GreenField decided they wanted to set a character limit of 500 characters on their posts? app.feed.bsky.post has a limit of 300 characters (defined here, line 16), so if the GreenField app would store a post with 500 characters under app.feed.bsky.post on your PDS, the post would not be visible to people in the Bluesky app. GreenField could also decide to make their own Lexicon, app.feed.greenfield.post, and define the character limit of the Lexicon to be 500 instead. But the Bluesky app only displays posts with the app.feed.bsky.post Lexicon, and not posts with app.feed.greenfield.post. So the post would also not be visible on Bluesky.
This example shows the power of Lexicons, and who gets to determine the specifications of a Lexicon. Anyone can create a Lexicon, which results in a system where the Lexicons that have the most users have the most power. Bluesky determined that their microblogging posts have a maximum of 300 characters. Anyone else can create their own Lexicon that sets a different character limit, but the soft power of 910 million posts that are already using the Lexicon that sets a 300 character limit is incredibly strong.
This is a long explanation of what seems like a technical detail, but worth knowing: decisions made via Lexicons can have powerful and long-lasting impact on the entire community, and I think it is important that decisions made here are not only left up to a few enthousiastic developers.
An example of the impact of Lexicons: There are now three different ATProto apps for sharing text snippets, effectively Pastebin clones: atpaste, plonk.li and Pastesphere. The three apps have similar features and purpose. But they all use different Lexicons. This makes these apps not interoperable with each other, and if one of the apps shuts down, it means you cannot access the text snippets that youâve made with that app with any of the other apps.
It is the same with the review sites (reviews made with Skylights are not interoperable with Bookhive), the recipes sites (A recipe on recipe.exchange is not visible on recipes.blue). These apps could be interoperable if they agreed on either a common Lexicon, or supported each otherâs Lexiconâs. But the apps were build at the same time when they were not aware yet often of eachâs otherâs existence, had different requirements, or just simply like doing their own thing.
A way to deal with the non-interoperability of Lexicons is with Lexicon.community, an community-organised project by independent ATProto developers to come to a set of standardised Lexicons that developers can use. The project got set up in the last month, and the first community defined Lexicons are now getting formalised. The benefit of using a generic community Lexicon for other app developers is that they automatically get interoperability, as well as a standardised Lexicon that is still extendable for customised additional features that are specific to that app.
We now have some better perspective to explain the difference between the approaches an app like Skylight takes, which uses the Bluesky Lexicons, and an app like reelo, which is creating itâs own Lexicons:
Skylight uses Blueskyâs Lexicon for videos. That means videos that are shown on Skylight will have to follow the definitions set by Bluesky, such as video length being limited to 1 minute. It also means Skylight gets to use Blueskyâs infrastructure for moderation, and does not have to set up their own moderation infrastructure. Videos posted with Skylight will also be automatically visible from Bluesky.
Reelo is creating their own Lexicon for videos. This gives them the flexibility to add other features to their videos that Bluesky does not support. It also means that they will have to provide their own moderation infrastructure for moderating the videos posted with reelo. This makes using your own Lexicon significantly more involved.
Both approaches have their advantages and disadvantages: Skylightâs approach is easier and cheaper, but makes the project dependent on another party. Reeloâs approach is more involved, takes more effort and risk, but does give reelo control to build their own independent platform.
Thank you for reading. I write a weekly newsletter about Bluesky and the ATmosphere. To follow along you can follow me on Bluesky or subscribe to receive a weekly email update in your mailbox:
https://fediversereport.com/atproto-explained-lexicons-and-video/
Show Original Post
baco001a (@baco001a@piaille.fr)
Je viens de faire mon #eXit! Lâexode de X est massif. Ne perdez pas un seul de vos abonnĂ©s. GrĂące Ă #HelloQuitX jâai inscrit 560 nouveaux passagers pour partir vers #BlueSky & #Mastodon. Retrouvez automatiquement vos communautĂ©s le #20Janvier via https://app.helloquitx.com !
Show Original Post
gigi (@gigi@mastodon.nl)
@mobileatom @the-fediverse-vs-corporate-social-media-mobileatom The fact that #Bluesky needs Bridgy to talk to the fediverse illustrates it is not decentralised: it is 1 company collecting the data of their users on one server. #Mastodon and the rest of the fediverse should bow out fast.
Show Original Post
vij (@vij@sfba.social)
This leads to Buddhaâs Five-Fold Path (#Blueskyâs mute phrase button)
Show Original Post