You can guess my opinions, but I have left them out of this particular thread. My goal here was actually just to see if my gut sense was correct that Bluesky was heading in a vibecoding direction. I think that feels fairly confirmed based off the discourse I highlighted and also what seems to be an indirect response from Bluesky's team (though I think that's more because of what @davidgerard wrote about it than what I did)

Anyway, gnarly time, but people can decide for themselves whether that aligns with their values. One thing seems for sure: it's a bet many orgs are making, and this will be one thing where in the ~decentralized space we'll be learning much more about whether that bet pays off and results in a better or worse ecosystem over time.

@cwebberChristine Lemmer-Webber ai usage has been normalised in most of the atproto dev ecosystem for a while now. just as some recent other examples,

tangled's seed round also explicitly mentions ai agents for coding as a use case (blog.tangled.org/seed) , and semble also targets ai agents as a use case (blog.cosmik.network/updates-fe)

0

If you have a fediverse account, you can quote this note from your own instance. Search https://indieweb.social/users/laurenshof/statuses/116172165945298765 on your instance and quote it. (Note that quoting is not supported in Mastodon.)

0