@WPalant I tried compiling a Rust project for Mac last year and was annoyed to discover that Apple wants you to go through some kind of developer signup program and sign a document or something in order to... compile. Throws a wrench in all the automated cross-compilation tooling.

So I'm just not compiling for Mac for now.

@WPalant I took a different approach — I kept each repo in place, but replaced the actual git contents with a single branch, single commit, single file (a README saying "moved to <link>").

For anyone else reading this, I'm happy to share the script I used for updating repos this way. (Hmm, Codeberg doesn't have the equivalent of gists.)

@quasirealsmiths @aparrish @LyricalGarfield There's definitely some difference of opinion in the community about where AI descriptions fall on the harmful-to-helpful spectrum.

Several blind people I've heard from have said that AI descriptions are worse, but it's not universal. I know that for myself, when my internet connection is bad and I'm relying on alt text, I'd *much* rather have no text than misleading text.

Maybe the best way to address this is to include "AI description follows:"?

@quasirealsmiths @aparrish @LyricalGarfield I'd very much prefer no alt text to alt text that's misleading (or in this case, complete garbage).

(To be clear, I think the bot is fun and you should totally keep running it! But ditch the auto-descriptions.)

@AmyZenunim My employer is starting in that direction. I've told my boss that I will use generative AI "for every task where it seems like a good idea" and that I'm happy to include that in my goals and performance review. He understands what that means. :-)

If they actually *require* me to use it, I'll just submit straight-up vibe-coded crap. No one will die if our software fucks up. But I'm also not going to be on the pager rotation any more, that's for sure.