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.
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.
@tomkindlon@longcovid@mecfs As someone with #fibromyalgia I find that we're mostly forgotten in the chronic illness community. While I would love to connect more, I have stopped talking about it because it's considered the "hysteria" of the modern era. I have some unique theories on what caused mine. But there is a much larger community around some illnesses than others.
Getting a larger number of followers is helpful when you're trying to provide information about an illness (ME/CFS, myalgic encephalomyelitis / chronic fatigue syndrome) that affects millions of people but is still not very well known. ME/CFS is often is not even taught in medical schools.
An #MEAction advocacy campaign called "Teach M.E., Treat M.E." is trying to correct this problem:
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é”
@thisismissem Well, with the added feature that you can't accidentally add someone to the conversation by mentioning them in a private message, like in Mastodon's mentioned people only posts ;)
@josh@thisismissem They definitely want to use some existing solution (they've mentioned MLS), but it will take a lot of time to research and implement and test properly, and they wanted to have something in the meantime because a lot of people want it and they want it now
@Rathmox Le but c'est de l'intégrer à AT protocol et d'utiliser le même protocole pour faire les comptes privés. Je pense que s'ils avaient choisi XMPP ils l'auraient déjà implémenté :)
<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!
I'm thinking of checking out #bluesky now that dorsey left, but I can't find a list of bluesky servers/instances. Is the federation feature too new? I just don't wanna do bluesky.social because I don't want the bs of being in a mainstream instance.
@Cheesealicious There's also no such thing as "The Algorithm" on Bluesky like on Twitter/Threads. There is instead a system where anyone can built their own "feeds" that pick posts using any filter or algorithm, and there's something like 50k of them right now. You can follow and pin any of them, and now you can even replace the default "Following" feed with some feed that you like.
@Cheesealicious So, on the Fediverse, the instance is your community, your handle, hosts your data, does moderation for you and serves a web UI.
On #Bluesky, you use bsky.app (or 3rd party app) as the UI, host data on the PDS, use any domain as the handle, subscribe to some number of selected moderation services, and use search, hashtags and custom feeds to find interesting content and people.
I have a question about BlueSky :blobfoxthinkgoogly:
So the point of BlueSky is to try to simulate a centralized social media platform with decentralized hardware, right? So, like, what's the incentive to hosting your own BlueSky servers? I can see having a single-user repository for your own data, but there's no reason to host anyone else's personal data, right? :confused_dog:
With Mastodon, the incentive to host a server comes from the fact that servers are smaller, tighter-knit communities, so hosting your server comes with building a community. What's the incentive on BlueSky?
@Rusty I’m not sure, I honestly thought we’d get customizations like we have here on Mastodon, but it looks like that’s not the case.
Maybe we just don’t have the full picture yet, atproto is still being developed so maybe it’ll become clearer as more applications are spun up using the standard.
I think the federation is more for that use case, like people could make tumblr clones or run their blog off the atproto and people could follow those updates within BSKY
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.
I sometimes wonder how things would've looked on #Bluesky if the first beta had been ready just 6 months earlier, if all those people who left Twitter for Mastodon could have gone there…
I've just checked the hashtag feed for #swiftlang and apparently there were 19 posts in total… (and 9 of those from me) 😕
@pshadov … you know what… I haven't actually checked, because I assumed it would be just Taylor Swift, but there's actually quite a lot of relevant posts on #swift apparently 😄
Bluesky now allows you to unpin or even remove the default "Following" feed and make any other custom feed the default one.
The "Following" feed is the chronological one by Bluesky but there's thousands of other custom algorithmic feeds created by other users and generated by federated third party servers.
@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.
There are problems here too. I suspect this is a fundamental issue that decentralised social media hasn’t taken seriously enough. It’s a bit like back and front end people not working together well. Protocol people can be inclined to underestimate the importance of what happens in the client, which IMO is where federation actually happens, as it’s there that platforms and UIs need to get stitched together.
I clicked a #bluesky toot or whatever they're called and it turns out they've implemented the most critical twitter feature: in-page loading spinners that make you wait several seconds for no fucking reason before you can read less than a kilobyte of text
