#bluesky

I am once again asking for your recommendations for a #mastodon #instance to jump ship towards. Taking a break from #bluesky has highlighted the issues I had when this was my only form of social media.

Now that my local feed has more bots than my federated feed, I think it's time. Also, someone else's instance has apparently flagged mine, so it caused a warning every time they interacted with me.

I know about https://instances.social/ . It lacks criteria I need. I can't search for >500 chars

New: Fediverse Report #108

This week's news:
- Ghost's (@index) connection to the #fediverse is now availabe in public beta for Ghost Pro users, with both an #ActivityPub connection to send long-form posts into the fediverse, and a reader app to read/comment/interact with the fediverse
- @anewsocial , the organisation that manages the bridge between the fediverse and #bluesky shared their upcoming plans

Read at: https://fediversereport.com/fediverse-report-108/

Klare Ansage: Mastodon steckt Bluesky in die Tasche. Und Theads und X eh.

Voller Vergleich: https://social-media-matrix.king-consult.de

#DigitaleResilienz #Kurznachrichten #Mastodon #BlueSky
From: @digitalcourage
https://digitalcourage.social/@digitalcourage/114176766698417709

(Medien: 1)

Help! How do I add this #bluesky User via #bridge to my #mastodon Friends?

@kuhnt.bsky.social

#fediverse #socialmedia

ATmosphere Report - This week's #atproto news:

- #Bluesky releases a protocol roadmap and a proposal for handling user intents
- Tangled is a git collaboration platform on atproto
- Blacksky is working towards Cypher, an AppView with local-only posting

https://fediversereport.com/atmosphere-report-2025march-b/

ATmosphere Report – 2025march.b

Bluesky PBC shares their protocol roadmap, and a way to indicate user preference to how external parties can handle their data. Tangled is a newly launched Git collaboration platform built on ATProto, and much more news.

Bluesky PBC has published their protocol roadmap for the first half of 2025, containing the projects related to ATProto that the team will be working on. The first project the team has been working on is making it much cheaper to run a relay. In order to validate the data the relay currently stores all the network data, making hosting a relay more expensive. The update that is currently rolling out significantly reduces these requirements, making self-hosting a relay much more accessible.

Auth Scopes makes it possible to make more specific and detailed access permissions when using OAuth. Currently, using OAuth to log into an app with your ATProto (Bluesky) account grants the app full permissions to your entire account. With the upcoming update, an app can set more detailed permissions: for example, a Bluesky client would need read and write permissions for making Bluesky posts, but does not need permissions to read or write posts submitted to Frontpage.

Bluesky PBC is also working on making a web interface for the PDS. The first update is account signup, allowing people to sign up for an ATProto account directly on a PDS, outside of Bluesky. Later on it will expand to broader account management options. This update is one that will help shift the perspective of what ATProto is, and how it can be used. A publicly accessible place to store personal data is a powerful feature. PDS can be seen as a stand-alone component of ATProto, and it does not have to be integrated with a relay and appview for all purposes. A lack of a web interface makes it harder for people to perceive the PDS as an independent stand-alone part. Currently, the PDS gives people power to own their data. Allowing people to log in on their PDS and perform account management gives people the perception and awareness that they need to understand that they own their data.

Further into the future, Bluesky PBC will be working on shared private data. Work on this highly-demanded feature will only start after Auth Scopes have been completed, as this is a requirement to get to private data. Only after that will Bluesky look at on-protocol E2EE DMs.

Bluesky PBC has published a proposal on how to let people set their preference (‘user intent’) on how their data should be handled outside of the protocol. This concerns things like using their data for generative AI training, being bridged to other protocols, and having their data archived. The proposal is similar to robots.txt: a machine-readable format that good actors are expected to abide by, but is not legally enforceable.

Defining intent (and consent) in a machine-readable format is a major missing piece of the fediverse. The inability to clearly define what a person consents to and does not consent to regarding their data has been a major contributing factor to drama over the years. Implementing such a system on a protocol level is sorely needed, and this is a great step in the right direction for ATProto. It turns out that not only have people different opinions on whether they want their data to end up in training sets for generative AI, many people also have a hard time coming to terms that other people have a different answer to this question than they have.

Building a system that defines user expectations and behaviour requires defining what the default setting of such a system is. Most people will not change from the default setting in any system, so there is significant power in declaring what the default state of a system is. The solution Bluesky PBC is proposing is to set a default value of ‘undefined’. This shifts the problem to the projects that want to use the data, leaving them to decide how to process data with an ‘undefined’ user intent. Because the currently proposed user intents cover the entire ATProto account, and not only Bluesky data, it is understandable that Bluesky PBC does not set default values. Doing so would have further cemented the soft power the company already has in the ecosystem. Bluesky PBC is aware of the dynamic here, by proposing that the user intents are not governed by a Lexicon that is under Bluesky PBC’s control, and floating the possibility of community ownership with community.lexicon.

Tangled is a newly launched ATProto software forge platform. Tangled focuses on making a decentralised network for code collaboration, using the ATProto identity system. To do so, Tangled introduces a new entity, a ‘knot’. A knot is a lightweight headless server that anyone can host, and that stores the Git repository. A knot can be seen as a slightly different PDS: a PDS stores your personal data that is used in the ATmosphere, and a knot stores your Git repository that is used in the network. You use your ATProto account to control a knot. Tangled provides an AppView, which shows all activity on the network, and allows people to access and contribute to other repositories hosted on other knots.

From a protocol perspective, Tangled works in a similar manner to Stream.place. Stream.place is an upcoming livestreaming platform that is integrated with ATProto. Both platforms add their own software pieces: Tangled adds a knot to store the Git repositories, and Stream.place adds their own software parts that handles the actual streaming part. They both use the PDS to store a public key. With this public key Tangled verifies that the Git repository is indeed owned by your ATProto account, and Stream.place that it is indeed your account that is streaming.

Blacksky continues on its path towards become a fully independent place in the ATmosphere. Founder Rudy Fraser announced that Blacksky received a 30k grant from Skyseed, which will be used to further build an entirely separate ATProto implementation in Rust.

Fraser also announced that Blacksky is developing Cypher, an AppView for Blacksky that features local-only posting. Local-only posting is a concept first introduced in the fediverse, and means that posts are only visible to that specific server, and do not travel outwards to the rest of the fediverse. This is more challenging to do on ATProto, where everything is publicly accessible by default. Fraser’s proposal for local-only posting sidesteps this by having local-only posts be stored on the AppView, not on a PDS. This locks the data into the Blacksky AppView. It sacrifices interoperability, but does provide a pragmatic solution for a real problem. My expectation is that we’ll see more of these types of solutions over time.

OpenMeet is an event planning app on ATProto, and it positions itself as an open source competitor to MeetUp. OpenMeet is available for use, but still currently in development. One thing that stands out about OpenMeet is that it uses the Lexicons developed by lexicon.community for its events. Smoke Signal is the first event planner app on ATProto, and its developer Nick Gerakines is part of the lexicon.community team, and working to transition Smoke Signal to use lexicon.community as well. This means OpenMeet and Smoke Signal will be the first examples of interoperability between two platforms using a shared, community-owned lexicon.

The ATProtocol Dev initiative is a community-led initiative (unaffiliated with Bluesky PBC) that is working on various community projects for ATProto, and organises the upcoming ATmosphere conference in Seattle as well. They announced receiving a grant by Skyseed to bring location data to ATProto. Foursquare recently released their dataset of 100 million points of interest as open source, and one of the main goals of this new project is to research the best way to make this massive dataset available natively on ATProto.

Skyart is a DeviantArt clone on ATProto that is currently under development. SkyArt is using their own custom Lexicon, as well as giving people the ability to post to the platform using Bluesky’s Lexicon. This creates the challenge of how to communicate these differences to the users. SkyArt shared an initial screenshot explaining the difference between posting to SkyArt and posting to Bluesky. This is a challenge that other apps will run into as well, so I think it’s worth paying attention to how different apps are thinking about and approaching this problem.

This week was the SXSW, a culture and tech festival in Austin, Texas, and Bluesky CEO Jay Graber was one of the keynote speakers. She held a conversation with Bluesky board member Mike Masnick, and the entire keynote can be rewatched here. Graber made the news with her shirt, which resembled one Mark Zuckerberg recently wore onstage. Zuckerberg’s shirt made news with the text “Aut Zuck aut nihil”, meaning “Zuck or nothing”, a reference to the Latin phrase “Aut Caesar aut nihil”, meaning “Either Caesar or nothing.” Graber’s shirt said “Mundus sine caesaribus”, meaning “A world without Caesars”. Bluesky PBC sold the shirt as a limited edition due to the demand from the community, and the shirts sold out in 30 minutes, with the team looking into doing another sales run.

ROOST is a recently launched initiative to build open source tools for content moderation for social platforms, and Bluesky PBC is one of the partners. Juliet Shen, an employee of ROOST, showed a proof-of-concept this week on an integration between ATProto and Meta’s Hasher-Matcher-Actioner. The goal is that media is scanned, to prevent unwanted/illegal content from being stored on a PDS. The integration with Meta’s Hasher-Matcher-Actioner allows illegal content also to be automatically reported to the relevant authorities. For use cases such as scanning for CSAM, such a system also needs access to the relevant datasets. Getting access to these datasets is not easy however. IFTAS tried to get a similar system off the ground in the fediverse, but they had to shut it down due to a lack of funding.

Popsky is a new pop culture review app on ATProto, using its own Lexicons. It is available for iOS, with Android in testing. Popsky joins other ATProto review platforms like skylights.my, but it seems to be the first one to be focused on mobile.

• ATProto Isn’t What You Think – Zicklag/Muni Town
  Zicklag is one of the developers behind Roomy, an upcoming ATProto-based public group chatting app. This article takes a different look on how to view ATProto, and it describes it as a system that allows for centralised apps that use decentralised data. It also goes into the importance of seeing the PDS+Identity system that ATProto provides as a vehicle to build apps that are otherwise not further connected to the rest of the ATProto system.

• Creating a decentralized bathroom (powered by the AT Protocol) – Dame
  Dame is an independent tech artist that has been experimenting with ATProto, and is also behind the cred.blue project. Their latest blog post focuses seeing Lexicons as a file format, and exploring what using Lexicons for more personal data would look like. The best way to illustrate this concept is by putting it into practice, which Dame did by releasing the app Flushes. Flushes is an highly serious ATProto-based app that allows you to share when you went to the bathroom.

• atproto by example part 1: records and views – Samuel Newman
  Statusphere is an example app by Bluesky PBC to help people get started building on ATProto. In the previous link above, Dame took Statusphere in a more whimsical direction. In this blog post, Bluesky engineer Samuel Newman expands on Statusphere as well, and uses more advanced ATProto concepts working with Lexicons.

And some more links to ATProto tech:

• An experimental Go OAuth client by Bluesky engineer Hailey.
• Create tiny 3d rooms that are stored onto your PDS.
• A local-first atproto CAR viewer by Blacksky founder Rudy Fraser.

That’s all for this week, thanks for reading! If you want more analysis, you can subscribe to my newsletter. Every week you get an update with all the articles of this week, as well as extra analysis not published anywhere else. You can subscribe below, and follow this blog @fediversereport.com and my personal account @laurenshof.online on Bluesky.

#bluesky

https://fediversereport.com/atmosphere-report-2025march-b/

(Medien: 1)

Hausputz, Teil 1: Social Media

Am Wochenende wollte ich mir endlich eine Übersicht über die diversen Dienste und Anwendungen verschaffen, die sich in den letzten Jahren und Monaten auf meinen Servern angesammelt habe. Leute, habe ich eine Überraschung erlebt.

Oder bin dran verzweifelt, je nach Sichtweise. Kurzum, da muss eine Menge runter. Aus Gründen.

Irgendwann fing das Ganze damit an, dass ich (m)eine eigene Mastodon-Instanz haben wollte. Zuerst auf einem gemieteten VPS, dann in einer VM auf der heimischen NAS. Im Laufe der Zeit kamen weitere Dienste wie #Friendica, #Pixelfed, #Iceshrimp etc. dazu.

#Castopod und #Peertube lasse ich jetzt mal außen vor, da diese doch wesentlich andere Zwecke erfüllen als die klassischen Facebook-, X- und Instagram-Alternativen.

Aktuell verwende ich hauptsächlich Friendica als Zugang zum Fediverse, lange Zeit war allerdings #Mastodon für mich der wichtigste Dienst. Leider musste ich dort nach jedem Update erneut die Zeichenbegrenzung von 500 auf 12345 erhöhen, da ich kaum etwas weniger mag als endlose Threads aus kleinen Häppchen eines langen Texts.

Friendica erfüllt so ziemlich alle meine Ansprüche, mit entsprechenden Resourcen auch erfreulich schnell. Gut, ich kann an Umfragen nicht teilnehmen, aber die betroffenen Posts öffne ich dann halt in #GoToSocial. Letzteres läuft auf einem kleinen VPS als Backup für den Fall, dass die Technik daheim ausfallen sollte oder Vodafone an der Leitung schraubt.

Die aktuelle Planung schaut also wie folgt aus:
• Friendica bleibt als Hauptinstanz, GoToSocial als externes Backup.

• Castopod und Peertube laufen ebenfalls weiter, auch wenn der Podcast eher selten bespielt wird.

• Alle drei (in Ziffern 3) Pixelfeds werden gelöscht, sobald ich einen Weg gefunden habe, die Posts und Bilder zu exportieren. Diese schiebe ich dann entweder per Script gesammelt nach Friendica oder integriere sie statisch in mein Blog. Hat vor Jahren schon mit Instagram funktioniert, auch wenn es einiges an Handarbeit war. Pixelfed als Service benötige ich eigentlich nicht mehr, die überschaubare Anzahl von Bildern pro Woche oder Monat passt auch in mein Friendica-Profil.

• Mastodon behalte ich aus sentimentalen Gründen. Ich wüsste gerade nicht, was ich mit den knapp 17.000 Beiträgen sonst machen sollte.

• Ersatzlos gestrichen werden also die Dienste, die nur aus Neugier installiert und praktisch nicht genutzt wurden: Iceshrimp, Glitch und Misskey.

Am Rande sei noch #Bluesky erwähnt.

Ja, ich habe vor Wochen einen eigenen PDS aufgesetzt und per AddOn mit Friendica verbunden. Nach wie vor sind leider einige für mich wichtige Personen nicht im Fediverse zu finden, aber zumindest auf Bluesky zu lesen. Ich selbst bin dort nicht wirklich aktiv, ab und an setze ich bei neuen Friendica-Posts den Haken, um eine Kopie des Texts rüber zu schieben. Allerdings ist es recht praktisch, Posts von drüben in die lokale Timeline gespült zu bekommen.

Den VPS, auf dem der PDS läuft, werde ich kündigen und das Geld in eine zweite Storage Box investieren. Offsite Backups sind wichtiger.

Es werden also einige Ressourcen frei. Mal schauen, was ich damit anfangen kann. :smile:

Bluesky To Sell Your Content To AI Data Miners

So it begins. Hidden in Jay Graber's recent charm offensive is this innocuously framed initiative: Bluesky is weighing a proposal that gives users consent over how their data is used for AI (https://techcrunch.com/2025/03/10/bluesky-is-weighing-a-proposal-that-gives-users-consent-over-how-their-data-is-used-for-ai/)

Not so fast.

1) Shows they are planning on doing content deals with AI companies.
2) Seems like it is Opt-out vs. Opt-in (see below).
3) It is just a voluntary robots.txt file

h/t @Lydie https://tech.lgbt/@Lydie/114149023344861046

more...

#Bluesky

if not now, when? Mutual aid and organizing in the fediverses and the ATmosphere

https://privacy.thenexus.today/if-not-now-when/

Mutual aid. Organizing. Sharing, contextualizing, and making meaning of news and health information to counter propaganda and information overload. The use cases for alternative social networks – not controlled by techbro white supremacist CEO's working with their cronies in authoritarian governments – practically write themselves in today's world. And with so many talented social scientists, designers, systems thinkers, and developers directly impacted by DOGE, MAGA, et al, there are a lot of people with the right skills for these new networks to make rapid progress.

The good news is there's a lot of promising work happening in the decentralized social media ecosystems known as the fediverses ("federated universes") and the ATmosphere (a fediverse built on Bluesky's AT protocol), including DAIR-tube, Blacksky, the #FreeFediverse, and more.

Still, as promising as these efforts are, there's still a long ways to go.

#organizing #fediverse #atmosphere #bluesky #blacksky

#Bluesky rüstet auf: Längere Videos, besserer Spam-Schutz und einfachere Moderation. Mit 33 Millionen aktiven Nutzern wächst die dezentrale Plattform stetig. Kann sie X und Threads Konkurrenz machen? https://winfuture.de/news,149483.html?utm_source=Mastodon&utm_medium=ManualStatus&utm_campaign=SocialMedia