leevlad's comments

Wheeler's past history doesn't invalidate the article's lack of substance.

I was hoping to see at least some hints as to why the security of 5G is flawed in its current state. The only argument I seem to parse out of this is what you stated.

Note that the author is Tom Wheeler - former chairman of the FCC. It does seem to be a 100% political piece rather than anything to do with the tech.

I don't think that's feasible, to be honest.

I'd imagine that you would want to look for evidence of a double spend as that's the most likely goal of a 51% attack. But then the blockchain must have up-to-date knowledge of likely double spend targets (such as exchanges, OTC desks, etc), and be able to algorithmically and deterministically prove malicious intent with high certainty. Only then will you be able to maintain consensus and prevent unnecessary or accidental forks.

But since this is all open-source anyway, it would only be a matter of time before a slightly more sophisticated attacker read through the updated consensus algorithm and figured out how to game it. And so the cycle continues.

In truth, the only real strategy for mitigating attacks in PoW blockchains is hash power. It has proven to be very effective if you have enough of it (see BTC), and looking for other 51% resistance measures isn't really that productive unless you start from the ground up and rebuild the consensus mechanism on a different paradigm (e.g. PoS, which is still unproven afaik).

I think it's just not worth the time. What do you do when you've successfully run a 51% attack? You go on an exchange and double spend the money, which means you have to maintain the 51% attack for longer than min # of confirmations for this currency on said exchange. And even after that, most exchanges (in NA at least, can't say much about intl) require KYC.

Because it's an eventually consistent system. If what you proposed was implemented, you could end up with a fork that would never get reconciled.

Anecdotally, it seems to be flying through pages it used to struggle on when I last tried it (~version 60). Tab switching seems faster too, but I haven't had enough time to put it through its paces yet. Fairly promising so far, though!

Firefox has noticeable delays and scrolling performance issues on OSX. I have a top of the line macbook from last year, with i7, 16GB RAM, etc. But even on that it's sluggish and stuttery. I've tried all sorts of performance tweaks, beta/nightly builds - nothing really makes it as snappy as Chrome or Safari. So, unfortunately, I have to go back to those.

I don't know if that's really a problem. When a AAA title that I want to play comes out, I will buy it regardless of what launcher it comes through. I'll download the installer straight from their site if that's what they want to do.

I think having something like Steam is great primarily for discovery and ratings.

After years of clicking cancel as a student, I was more than happy to shell out the full amount for a license after my first paycheck. Don't think I would've stuck around if the free versoin was gimped in any way.

To add to many other valid points others have provided, OVH is a discount provider and they use second-hand / refurbished hardware at their data centers to keep costs low. I used to manage hundreds of servers on OVH and found that their hardware failed much more frequently than even us-east-1 on EC2. Most common issues were memory and disk related failures. A few times, their techs tripped over a power cord that took a few of our racks down, and they used to have frequent issues with network connectivity (I believe it's gotten better since).

On top of it, you will find that they cut costs on some of the less obvious things. For example, one day we found that their vRacks are not redundant, so a failure in one of them caused hours of downtime of our intranet.

As far as customer support - our account manager was always very helpful and understanding.

Amazon has had a development office in Toronto since at least 2013.

Fascinating every time I read about it. Found a nice infographic: http://2oqz471sa19h3vbwa53m33yj.wpengine.netdna-cdn.com/wp-c...

Kinesis works well for low volume, and isn't any more or less complicated than SQS. You should give it a try, it will certainly make some things simpler

Yup, getting elevated error rates uploading to S3 - writes failing as well as closing the uploads. Also seeing 503 slow down as reported by others.