202 karma · joined July 16, 2014
The problem with DE is it's so inexpensive and effective, and that makes it difficult to sell as a product. I got a 2kg bag of it for $10, and it's enough to last decades.
Weekly releases (or slower) is appropriate when you rely on users to update their software or firmware. Most mobile app development does this.
It's all open source and playable at https://ora.kennerspiel.com
Keep the logic in your YAML "dumb". Avoid variables and subroutines in the file, if you want to DRY something, create your own custom action. You can have unit tests on an action, you can't have unit tests on a GHA workflow.
I suspect the author hasn't actually done this on a project with more than one person, supporting 99% of browsers in the wild. I also suspect they didn't run their own code, because either my screen is not as tasty, or "onlick" is not an handler of div.
There, I made it point-free. Isn't it much simpler?
It uses PGP rather than rolling its own encryption, which also makes it compatible with hardware tokens, for free.
It's not some complicated project... it's just a thousand or so line shell script.
The real transaction happens at the beginning, and another transaction happens at the end when the channel closes and we settle out who gets the remainder.
You would be absolute mad to use any other platform. AWS gets it right on the customer service front. Amazon, perhaps deeply less so... but AWS? amazing.
The overhead of maintaining a properly secured PKI key and implementing signing of generated PDFs with it is nonzero.
Banks aren't always rotten and soulless, they are cold and lazy machines that do the bare minimum that their customers ask.
This project is great, let's spread awareness that PDFs _can_ keep an internal digital signature and maybe someday their customers will demand it.