985 karma · joined February 23, 2023
It's crap either way.
If I search for "DeepL" the first hit on the play store is "Preply" whatever that is, only the second one is actually DeepL.
You can just vibe code it yourself. If your requirements are narrower (eg. you only need support for 3 networks and not 12), you will end up with something that takes less time to develop (possibly less than a day), it will have a smaller surface for problems, and it will be much better tailored to your specific needs. If you pay attention to what the LLM is doing it will also be easier to maintain or extend further.
The surface for security vulnerabilities also gets narrower, since you "only" have to trust the LLM (which is still a huge ask, but still better than LLM + 1 random person).
Of course MythosGuard won't be a complete solution either, but it will be just enough to steer the discourse into the "it's your own fault for running without MythosGuard really" area.
Having the ability to sue, and having the resources to sue is also not the same.
The amount of times I had to deal with support cases (as the reporter, not the handler) where I felt like the support person was actually incentivized to solve my problem vs just following the script is astonishingly low. Even with paid support. Paid support just means you get to follow their script faster.
Which ones are these "most distros"?
What would you consider broken?
Surely if your license says "LLM output trained on this code is legally tainted", it is going to dissuade them.
>Claude Code users typically treat the .claude folder like a black box. They know it exists. They’ve seen it appear in their project root. But they’ve never opened it, let alone understood what every file inside it does.
I know we are living in a post-engineering world now, but you can't tell me that people don't look at PRs anymore, or their own diffs, at least until/if they decide to .gitignore .claude.