re: password manager PSA (keepassxc)
@argv_minus_one @hazelnot I quite like the global/shared menu bar approach that macOS uses, and I think KDE still supports. A bit of the best of both worlds: distinct without costing vertical real estate per window
password manager PSA (keepassxc)
@Ember
How is it different from allowing pull requests from rando's on the internet?
Using LLMs for coding has some ecological, legal, and ethical repercussions, but as long as you review the generated code properly the same way you're supposed to review code from 3rd parties, *security* should not be an issue, in my view.
Am I missing something?
How is it different from allowing pull requests from rando's on the internet?
Using LLMs for coding has some ecological, legal, and ethical repercussions, but as long as you review the generated code properly the same way you're supposed to review code from 3rd parties, *security* should not be an issue, in my view.
Am I missing something?
- replies
- 1
- announces
- 0
- likes
- 0
re: password manager PSA (keepassxc)
@Ember
OK. I see what you mean. It's a risk, though I don't see it as likely as you seem to think.
IME, reviewing code is faster than writing it from scratch. This applies whether the code is generated or submitted. Whether that happens is the more interesting question, rather than whether LLMs are used, IMO
Corruption bugs are always possible, LLMs may increase the risk but they don't introduce it. You need backups of your vault regardless.
OK. I see what you mean. It's a risk, though I don't see it as likely as you seem to think.
IME, reviewing code is faster than writing it from scratch. This applies whether the code is generated or submitted. Whether that happens is the more interesting question, rather than whether LLMs are used, IMO
Corruption bugs are always possible, LLMs may increase the risk but they don't introduce it. You need backups of your vault regardless.