lkoolma

Related: https://news.ycombinator.com/item?id=40361128

I agree that many in the financial sector do not know much about quantum computing, but it also does not seem that some in the quantum that do not understand the details of the problems that the financial sector has either. For instance, those in the capital markets/trading floors in Europe and North America do significant risk calculations with hundreds or a thousand variables on up to 100,000 positions with a certain confidence. Many of these risk calculations need to be reported nightly to regulators. These financial companies are paying many millions per year to AWS, Azure, or Google to do these calculations on classical computers. However, many parts of these calculations could be done with quantum computers relatively instantly, given enough qubits. I realize that the technology and reliability is not there today, but hopefully it will come soon. I would not be surprised if by 2035 using quantum computers to do many variable risk calculations would become (almost) mandatory for major European and North American financial companies.

After working with a few large corporations and their DDoS protection solutions, I did not have a good experience with Verisign, and they were not able to handle attacks or get things working. However, I have great experiences with Akamai and Cloudflare. I trust the people at Wikimedia will choose wisely. I would I have learned that Verisign has one of the worst BGP mitigation/scraping solutions out there. There are a few alternatives that have more experience and provide much better uptime, include solutions from Cloudflare and Akamai.

Might be late, but has anyone in CloudFlare tried to switch away from regex to something more efficient and powerful? Tools like re2c can convert 100s of regexs and CFG into a single optimized state machine (which includes no back tracking, as far as I remember). It should easily handle 10s of millions transactions per second per core if the complete state machine fits into the CPU level 3 cache (or lower), with a bit of optimization.

I agree that just using a credit card number and the expiry date is definitely bad, but I am not aware of any authentication solution that fully solves this problem (but please enlighten me if there is). We know passwords have many problems. Two factor authentication with SMS has problems with SIM hijacks. Physical tokens (e.g. RSA tokens) have problems when users lose them.

Feel free to enlighten me if someone has a better solution for all of this.

There are a few comments about the fear that many of the top websites of the world get/use this data. I understand that people would be scared about this.

However, fraud is big problem, and any site that is dealing with anything precious is (hopefully) doing whatever they can to prevent fraud to protect their and your resources/data. From what I can tell from the JavaScript from some of the top 100 sites, it looks like many are using this data, and if the data is not what they expect, the transaction can be rejected. I do not like when a company like Facebook would use this data, but it is a tradeoff for allowing other companies to use it.

Not sure if someone from CloudFlare, Akamai, or another company (Coinbase?) can publicly comment on what they do.

Would be nice if the browsers would at least notify of its use.

GitHub: https://github.com/google/data-transfer-project

Several other companies are working on it in various forms. Disclaimer: I am working for one of those companies.