Llewellyn @ Llewellyn @lemm.ee

Posts

0

Comments

556

Joined

2 yr. ago

with absolutely no way to organize it, categorize it, order it, or in any way manage it other than deleting history

But you can pin any chat and you can reorder any pinned chat (and maybe even non-pinned ones - I haven't checked).

I think not. The problem isn't in a service, the problem is in people.

I'm ok with trans people

I thought they were trans

but no, everyone seemed to jump to conclusions

And I'm certain that it has served as the catalyst for the bitwarden decision.

Kamala, probably, would have been less harmful than Trump.
But not in regard to assisting genocide of Palestinians.

USA! USA!

And all of you had the nerve to reproach us, Russians of inability to prevent the election of the bad leader.

He will sell out America, spill its blood for his own gain, and he already has.

Like Biden or Kamala wouldn't do the same with active support of genocide in Gaza.

Red or Blue - certain things remain.

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

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?

And added some of their own commentary

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

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.

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

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.

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.

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

They created the client. In theory, they can have some backdoors. And since you store your files on their side, risk is greater, imo