Post

The challenge with Attie for the builder community isn't the use of AI. It's the question of whether Bluesky begins absorbing/cannibalizing existing ecosystems within the Atmosphere.

I have no idea what’s going to happen to the application developer ecosystem because of AI coding but I would say the call to action should be for all of us to start utilizing this tech in our work

I’m going to be starting a virtual meetup for agentic personal computing so we can all row in the same direction I don’t care if it’s Attie, I care if it’s the atmosphere

As I said elsewhere I am basically radicalized about this. We fight now for personal computing and personal agency or we lose another decade to closed clouds We push now for an open internet and open models. Nobody is going to hand it to us because they’re nice

I can see the reasons behind this push, whether I agree with them or not. But then, why not go all-in? Why not make it a fundamental requirement that Attie *only* use open models. From my understanding, the current system is to use Claude. Why not push the limits from day 1?

Really good question So- we did test it. And the open models are, you know, in striking distance but not as good yet The way we see it then, the interface is very exchangeable, so we build in anticipation of those models catching up to claude. But very open to counterpoints here

Agree with Paul... It's worth acknowledging that most users care about outcomes, not process; using the best quality model is the only way. Also the "api" for LLMs is literally just prose. There has never been SW where it's easier to switch horses. LLMs are lock-in-proof in a way web 2.0 never was.

0 reposts0 likes

But "taking a stand" without taking a stand is "open model washing" the way "openwashing" has been a problem for open source. I'm not claiming malice, the point I'm making probably wasn't considered. But if you're going to take a stand for open models etc as part of the future, take a stand for it