Don't trust the client, store things like geolocation data and other such things server-side.
Uhm, where do you think you got those coordinates from in the first place?
TFA isn't talking about sending geoip data back to browsers to store it in a cookie, it's about getting GPS data from visitors, who will want to lie about it, e.g. to get free beers for logging in at a specific spot several days in a row.
Along the way, 345.18 billion ISK was paid out to investors as interest to make sure the scheme kept going. Another 452.72 billion was withdrawn by worried investors before the company shut down; that left 1,034 billion ISK in the hands of the company's owners.
I always wonder how many of these worried investors recognized the scheme for what it was right away, and decided to try and make some profit out of it themselves.
Companies spending too much time perfecting their UI design will go out of business while their competitors are shipping flawed but ultimately usable products.
There's a difference between perfecting a UI design and inflicting completely new, experimental ideas on unsuspecting users. Testing which particular gesture would be best for each interaction might take too much time, but completely omitting menus (leaving the only way to accomplish anything to be guessing the right gesture) is something that should've been thought over (especially if your target platform ships with a physical 'menu' button).
In any event, the only number that means anything in your relationship with your ISP is their number. You will not be able to convince them that your number is "right" or "more correct" than their number.
You might not be able to convince them, but you are able to switch ISP.
In special relativity lets say I'm sitting next to someone and then I go for a walk and come back. When we compare clocks they will be the same since otherwise there would be symmetry breaking and we could establish a preferred inertial frame.
You don't need to factor in acceleration to have the clocks get out of sync, just remember that changing directions means you won't be at rest the whole time in any reference frame:
Inertial frame of your friend: First you move away with say 1 m/s. Halfway through you move towards him at 1 m/s. You're moving, so your watch will be slow when you return.
Inertial frame of you walking away: First your friend moves away at 1 m/s. Halfway through you start moving in the same direction at 2m/s. You're moving faster, so your watch will be slow when you catch up with him.
Inertial frame of you walking back: First you move at 2m/s, while your friend falls behind at 1 m/s. Halfway through you stop moving, and wait for your friend to catch up. You've been moving faster, so your watch will be slow when he reaches you.
I agree it's stupid how browsers show self-signed certificates as more dangerous than plain HTTP.
The difference between paid-for certificates and self-signed certificates means more than just who promises authenticity though: The certificate's signature can be checked against the certificate shipped with the browser, thus preventing MITM attacks.
Basically:
Thus paid-for certificates mean you won't get MITM'd, the part where the CA also verifies identities is just bonus.
That was it. No statistical math. No deep AI.
"Always leave a multiple of four plus one" is hardly statistical math/deep AI.
It was only unbeatable because you always let it go first, but at least it seems to have accomplished its task of being fun to program.
It appears they 'forgot' the whole checks and balances thing when enacting a powerful censorship law.
FTFY
A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson
