I do use it, and rewriting the whole file annoys me especially when the storage is not local and the database contains sizable blobs. For storing passwords and short secrets, it makes little to no difference but if I have 10 1MB blobs stored in there, it becomes upsetting.
Well, yes, this is what OP is saying, and I'm not arguing against that. However, this is not what *.kdbx was designed for. And I am only talking about what cryptographically changes for the intended use case if we encrypt every page separately.
Also curious why would one be proud of having an LLM rewrite something that there is already a library for. I personally feel that proud LLM users boasting sounds as if they are on amphetamines.
Yeah but it’s like saying, “why are you impressed with Claude making a car when there are plans for an engine online?”. Even if Claude used that code (it didn't), it made the whole car. Not just an engine. There’s a lot more stuff going on than simply calling a backend mail server over jmap.
And fyi, jmap is just a protocol for doing email over json & http. It’s not that hard to roll your own. Especially in a web browser.
Your initial claim talked about jmap and this looks to me like a full implementation of the RFC in rust. That is the hard part of an email client IMO so I’m not sure I’d agree with your analogy, but you’re saying it made a web app which called a library like this?
Would be interesting to see it, did you publish it yet?
> looks to me like a full implementation of the RFC in rust
Only the client parts. And only the client parts its actually using. JMAP clients can be much simpler than servers. A JMAP server needs the whole protocol. JMAP clients only need to implement the parts they use. Servers also need to parse email message envelopes - which is way more difficult to do correctly than people think. JMAP clients can just use pre-parsed messages from the server.
Anyway, the code is here if you wanna take a look:
Cute that you think that's how it works. I guess you're also thinking everyone that voted for the current administration agrees with them on everything they do and voted them in exactly for that. I am at least glad you didn't say if you don't like how it works, move elsewhere.
I know that’s how it works and I also know it’s not a zero sum game. That’s why every law or policy gets time for comments and debate and sometimes policy gets revised. It’s how governance works.
But if you feel you have the perfect solutions, then by all means get yourself on the ballot so we can finally see the light.
What websites a person is allowed to access should not be a matter of debate, it is for the individual to decide. Other people's opinions are not relevant. Even if 99% of people think a person should not be able to access a website, it is still their right to do so and they have no need to justify it.
Democracy is for deciding what to do with taxpayer money. It shouldn't be a mechanism by which people can vote to take away other people's freedoms.
Does that apply to websites full of CSAM, or that sell for-hire animal torture real-time streaming services, or that provide hitman hiring services, or...
I think your view on how government and the internet works is somewhat outdated. Social media is not just "what websites a person is allowed access to" and government is so much more than what we do with taxpayer money.
The US is evidently a poor example of what a fully formed government is so I wouldn't use that as a basis for one's world view.
> but he’s instructed not to send anything without explicit confirmation from his owner
How confident are you in guardrails of that kind? In my experience it is just a statistical matter of number of attempts until those things are not respected at least on occasion? We have a bot that does call stuff and you give it the hangUp tool and even if you instructed it to only hang up at the end of a call, it goes and does it every once in a while anyway.
reply