That's not really relevant. "anoncvs" was just the ability to retrieve source code from the project's repository without an account, as opposed to being forced to download a tarball. It didn't do anything more than ladybird's public github-hosted repository[1] to facilitate contributions.

Think of ladybird's github issues like the openbsd mailing lists. If you start submitting good issues with patches there, and you do it often enough that they would rather let you merge your patches yourself, there's a high likelihood you'll no longer be an outsider. (I don't know this from personal experience with ladybird, but it's the vibe I get from their posts about the matter.)

[1](https://github.com/LadybirdBrowser/ladybirdP)

I don't think an ORM is necessary, but I do think you need to say what people are meant to do instead and how your batteries are included without it, if you're going that direction.

Failure to do so certainly makes me think the new project isn't very serious.

I do too! And I appreciate your transparency about the vibe coding. But nowhere in the repository that I've found so far do you say who is writing this. For something like a password manager, I kind of need to know who's responsible for it, and who's reviewing the LLM source code, what they've done before, what their business model is, etc.

Can you share?

https://github.com/anthropics/claude-code/issues/73125#issue...

In #30740, customers asked for the ability to turn it off, and anthropic closed it as "not planned".

I think I've been using it for 10 years (or so) now. It's my favorite thing Mozilla has done on iOS.

https://www.firefox.com/en-US/mobile/focus/

The only thing I use Firefox on iOS for *is* its ad blocker.

There's no reason to believe they're any less subject to US jurisdiction than LetsEncrypt.

https://www.ifixit.com/Guide/MacBook+Pro+14-Inch+2021+USB-C+...

I've only changed a battery on that model, not the ports, so I haven't verified, but those steps are detailed enough and consistent enough with what I observed, that I believe them.

"The Neo has the same modular bits and bobs we’ve applauded in recent MacBook designs. The USB-C ports are modular, so a damaged charge port doesn’t turn into logic board work."

https://www.ifixit.com/News/116152/macbook-neo-is-the-most-r...

https://github.com/thedaviddias/Front-End-Checklist/blob/mai...

I've found that it's a thing that develops over time with experience, though. And I want people I'm training to develop that skill rather than farm it out to an LLM that never gets it right.

Unless I knew the maintainers personally, this would prevent most of my contributions, which are most often accepted. Maybe it's worth losing out on my small contributions to avoid slop. But things would absolutely be lost this way.