It didn't take very long...

Special thanks to @mactunag for giving me a heads-up about Bluesky's message on X from November 2025

Sources:
1: https://x.com/bluesky/status/1991513731541647733

2: https://bsky.app/profile/jay.bsky.team/post/3mi5pwoncqs2g

What I find particularly egregious is that Bluesky already had a custom feed builder: #Graze was an independent project that had proved to be super popular. They had raised a million dollars just last year! They even sponsored the AtmosphereConf last week. Then Bluesky PBC steamrolled over them and announced their own project - Attie - powered by AI... at AtmosphereConf (the event where Graze was listed as a major sponsor - you can't make this up).

A developer for ATProto was horrified by this, writing:

"Why would anyone fund an Atmosphere project if Bluesky, with $100 million in the bank, might ship a competing feature at any moment? Why would a founder bet their career on this ecosystem? The presentation didn't just hurt Graze. It made the entire ecosystem look unfundable."

🔗​: https://trezy.com/blog/the-marshmallow-test

I am getting A LOT of heat for pointing out shady behaviors by Bluesky PBC. Even from Fedi friends. But I think it's important to be wide-eyed and consider all this mounting evidence of problematic behavior.

#Bluesky #ATproto #openwashing #VC #cryptobros

@alina were it so easy…

• To me #AGPLv3 is a non-starter and only beaten by source-available #OpenWashing of the #SSPL kind when it comes to "#AssholeLicensing".
• It only exists as contagious #AssetDenial licensing. But that's the maintainers choice.

Either way, a .noai file is a good indicator.

Gerade diskutiert @spinfocl die verschiedenen Aspekte von Offenheit bei LLMs: Gewichte, Inferencing Code, Trainingsdaten, Trainingslogik.

https://opensource.org/ai/open-source-ai-definition
https://isitopen.ai/
https://doi.org/10.48550/arXiv.2405.15802
https://doi.org/10.1145/3630106.3659005

#OpenLLM #OpenSourceAI
#OSI #OAID #MOF #OpenWashing #DHd2026

@mrmasterkeyboard that's basically a 3-clause BSD, so obviously not a problem.

I'd not consider it if it was some "source available" #OpenWashing like SSPL or RSAL.

• I mean, I can totally understand why one would not do release something as #FLOSS (I.e. #Tarsnap is #SourceAvailable as a means to evidence to it's customers that it truly has #SelfCustody and that they hold no keys to the encrypted data)...
  • Even if that means like #DolphinProject [when there was that huge Nintendo Leak] I cannot even look at Tarsnap's source code!