With what bandwidth though?
With what bandwidth though?
Top of the line graphic cards still cannot max out the latest games at 4k60, how can they achieve 8k?
Top graphic cards will always be catching up to the latest games. Software is developing much much quicker than hardware.
Resolutions higher than fullHD are useful not only for TV in front of your sofa. You need 8k (and even higher) to VR-helmets. Also there already are cinemas with giant displays instead of projectors. Don’t be a retrograde.
There are on premise LLMs
Rhyming is a mnemonic device
Rhyming has other purposes: creation of additional sonic rhythm and restricting of words usage - for making matter more distinct and interesting (as rules do for any game).
Isn’t that the point of capitalism?
I mean, when you need to operate chats via folder structure, wouldn’t it make Оutlook out of it?
Wouldn’t the folder structure kind of defeat the purpose of the messenger vs mail?
deleted by creator
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.
but no, everyone seemed to jump to conclusions
And I’m certain that it has served as the catalyst for the bitwarden decision.
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
But what about “sava”?