Llewellyn

joined 1 year ago
[–] Llewellyn@lemm.ee 1 points 1 week ago

Well, maybe I am more sensitive to such a matter because of being Russian.

[–] Llewellyn@lemm.ee -1 points 1 week ago (2 children)

He's in the middle of a set and someone starts yelling about some political issue...

Some political issue..? That's what the genocide is to you?

[–] Llewellyn@lemm.ee 1 points 1 week ago

And added some of their own commentary

[–] Llewellyn@lemm.ee 0 points 2 weeks ago

Keepass could have backdoors too. The difference is: authors of those backdoors are not from the same company, which I use as cloud storage.

[–] Llewellyn@lemm.ee 0 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

I find risk slightly bigger when you encrypt your private data with the product of the company and store that encrypted data on servers of the same company.

Why: because if they have some backdoor now or plans to introduce it in future, they have all the time in the world to apply that backdoor to your data. Without you knowing it.

[–] Llewellyn@lemm.ee 0 points 2 weeks ago (4 children)

That different FOSS client stores your data on their company's server. It's an important factor, IMO.

[–] Llewellyn@lemm.ee -4 points 2 weeks ago (6 children)

If it was backdoored, many people would be calling that out.

In theory. And not necessarily soon. Don't forget the context of this thread: we compare bitwarden with keepass, which does not offer to you your password base on their server side.

[–] Llewellyn@lemm.ee 4 points 2 weeks ago

I have an even better idea: make tool creators and / or CEO of the company, using the tool, liable for all tool's mistakes and hallucinations.

[–] Llewellyn@lemm.ee 6 points 2 weeks ago (1 children)

Which has the same concept as the LLM under the hood, hasn't it?

[–] Llewellyn@lemm.ee -4 points 2 weeks ago

encrypted is the key word

view more: ‹ prev next ›