3,073 karma · joined February 9, 2011
[ my public key: https://keybase.io/lekevicius; my proof: https://keybase.io/lekevicius/sigs/hrkS3l9IZp-H77PDQFN9cbMbAM9rFQ-6sISj9gTId9Y ]
The article mentions the core problem: being your own bank is a HUGE risk. I can accept that risk and deal with complex security mechanisms I have to maintain to both protect my own bank and keep it accessible. But a good security guide for crypto is 20-30 pages and requires serious cryptographic understanding. Currently, I can’t expect that from average users.
Everything can be solved over time. Social recovery wallets and user-friendly hardware might become mainstream. But I don’t see that happening in the next 5-6 years, and I fully expect CBDCs to be far along in that time. Then, countries will be a lot less motivated to promote crypto for the unbanked.
However, each PIN entry is accompanied by "code check": bank's support person says their 4 digit code, and you can verify that it matches on request for PIN screen. This neatly prevents someone pretending to be a bank during a call, because each PIN request uses a different "code check".
I'd love to see two things:
- A decent free or one-time payment editor for Lottie (don't make me use AfterEffects)
- Perhaps a Lottie implementation using Web Animations API, if that is even possible.
I'm struggling to understand this "measurement".
- Kape with Cyberghost, PIA and ExpressVPN
- Tesonet with NordVPN, and allegedly a couple more most known, but there is no strong proof, so I'd rather not list them here.
<section name="Options"><checkbox flag="c" label="Compile" /></section>
It shouldn't be a hassle at all to convert a man page to a UI that speeds up actions and avoids common errors.Anyway, this idea is free, so feel free to take it and do whatever, even full HTML (:
I think that's the wrong goal. The goal should be really simple definitions and ok quality apps. Simple JSON (or XML, don't care).
{ control: checkbox, flag: c, label: "Compile" }Idea would be to define UI structure that outputs (and executes) essentially a string (command) to run.
I'd much prefer an encryption format that hides itself in a well-known one layer encryption (like encrypted zip).
Mixing "normal" people and self-hosted email is a recipe for very bad experience.