contrarian_

"linear transformations with soft thresholds sandwiched in between"

Investment in mining hardware whose value is tied to a speculative asset without fundamental value beyond utility.

None of the current implementations can scale, so even their utility is questionable. There is a way to make a scalable trust-less digital currency by using a mutable leder, but none of the current coins that I know of are heading that way. The main difficulty will be how to distribute ledger space in a way that cannot be monopolized by the richest. That is a simple technical problem to solve though, because storage capacity will eventually surpass the ratio of richest to average wealth. Then you can allocate ledger space in exchange for an affordable deposit, redeemable when the balance is emptied.

It's a winner-takes-all market, so there are absolutely strong economic incentives to build the best robovacuum control software.

> Mining new bitcoins makes transaction easier

No. As long as at least one person is brute forcing hashes, transactions will be processed at the same rate of about 10 tx/s.

Sure you might not like SAP's business practices but there are very few large software companies in Europe.

How do you suggest writing a thin API layer to expose an interactive real-time stream consumed over WebSocket?

> The idea would be that you want sellers to pay something to participate in the market

What? Why would you want to do that beyond covering expenses for scam prevention?

The network connection side panel also seems to never open when you want it to, only to open 2 minutes later when you are watching a fullscreen video.

The toy example referenced in section 6.4 is actually closer to Spectre. It's missing the crucial distinction that the speculatively loaded address should belong to a page inaccessible from the current ring level.

To see why that toy example is insufficient, consider that you could simply execute the load directly without putting an exception in front of it and you would be able to read the value.

AMD CPUs are completely unaffected by Meltdown, since AMD checks permissions before fetching memory into the cache.

Emphasis on "mitigate".

WRONG. You fell for the Intel PR strategy. AMD is completely unaffected by Meltdown, since AMD checks permissions before fetching memory into the cache.