523 karma · joined December 25, 2015
[1] https://cpl.thalesgroup.com/encryption/hardware-security-mod...
I personally feel J.S. Bach would be a better metaphor here.
For more realistic programs, binary sizes go down by 3.5% or as much as 22%.
The original linker was written by Ken Thompson, who is now retired.
a; b # Execute command b after a. The result of a is not used by b.
In Haskell: a >> b # Run function b after a. The result of a is not used by b.
In Unix: a | b # Execute command b after a. The result of a is used by b.
In Haskell: a >>= b # Run function b after a. The result of a is used by b.Unix pipelines actually helped me make sense of Haskell's monad.
deno run --allow-net myWebserver.ts
With SELinux, one can specify the port range and network interface that the application is allowed to access. It also provides audit log that can be examined by the admin. Maybe there is no need to reinvent the wheel but just use some form of MAC if you really care about security.
Some founders of altcoins apparently don't understand this and try to buy hashpower to artificially increase the hashrate, hoping to increase the price of their coins. If there is no demand for their coins, an ASIC farm is no different from a Rasberry Pi.
[1]https://filecoin.io/blog/participate-in-our-trusted-setup-ce...
[1] https://bitcoin.stackexchange.com/questions/81624/can-two-or...
If the attacker sends the legit transaction and double-spending one at the same time, it will be detected due to the few seconds wait by the payment processor.
Yes, there is a risk of double-spending, but since this is a small amount, the cost of the attack may be higher than the benefit. The payment processor can also deploy more full nodes in different geographic locations to monitor and detect potential double-spending transactions in the transaction memory pool.
Not sure what is the best way to verify Twitter/Github account though. This has to be managed by users themselves. E.g. one user posts a proof in the Twitter account, the other user verifies the proof by checking the proof against the public key posted in the database.
Together with W3C's draft Decentralized Identifiers (DID: https://www.w3.org/TR/did-core/), it could provide a decentralized alternative.
Not sure what is the best way to verify Twitter/Github account though. This has to be managed by users themselves. E.g. one user posts a proof in the Twitter account, the other user verifies the proof by checking the proof against the public key posted in the database.
Edit: updated description.