more transactions can commit at the same time, but with one counter they would conflict (as it did in the Redis case)

they should use CRDT (and trying to model that with this 1000 row workspace, no?)

still, eventually at some point they need to do the math

no need to start futile fights when you are in the (ideological) minority.

in general to work on something that will get "into the rust compiler" it needs at least an RFC and then a Major Change Proposal [0]

in practice it starts with asking on zulip [1]

[0] https://forge.rust-lang.org/compiler/proposals-and-stabiliza...

[1] https://forge.rust-lang.org/how-to-start-contributing.html

spending time on fake CVEs while people are exploiting real 0days against your system.

who was first to some kind of novelty? who cares. someone did something but no one can replicate it? intentionally wasting public money. fraud by any other name.

"science" wouldn't move slower if we would build more robust data generating processes.

of course, since usually it's hard to judge quality academia uses proxies. not to mention that the people who could usually are also live inside fancy glassware. and it would be a shame to rock the boat.

... but math is doubly special, because we accepted that it doesn't matter (until it does, but then it's called cryptography and logistics network optimization and high frequency trading, and machine learning), and how long a problem stays unsolved was quite a good proxy.

still, if AI solves the easy ones we can finally have fun with the hard ones!

https://stackoverflow.com/a/32802486

though there's sandbox: https://jinja.palletsprojects.com/en/stable/sandbox/

it simply predates the "sanitize by default" mindset/convention that nowadays React (dangerouslySetInnerHTML) and Angular has.

(see the open (Lean) label for Erdos problems https://mathstodon.xyz/@tao/116987866420438091)

(tangentially related recommended reading https://danluu.com/p95-skill/ )

as others mentioned, there's BitWarden (cross-platform, self-hostable), but if you want something simple there's KeePassXC (and you can put the store file on a dropbox shared folder)

those that don't have this built-in (eg. KeePassXC) recommend using Dropbox or some external sync mechanism

but the keys are stored in a file, which you can back up.

> all the security vanishes if you put usable recovery mechanisms for the passkey or the second factor

no, not at all. it still gives you better UX, because when you use the passkey you know it's the site you want to log in to. (because there's mutual authentication.)

BitWarden, KeePassXC, and probably a bunch of other password managers have very thorough support for import-export, automatic/periodic backup, sync/merge, etc.