This article shares 31 project danger signs you should recognize, so you can decide if it's possible to fix them or bail. But oh, we can be so certain that there are plenty more to add...!
Extremely common, actually. It's one of the major pitfalls and difficulties of doing multi-threaded programming and one of the hardest things for programmers new to multi-threaded design to learn how to solve. It can also be extremely difficult to debug, even for experienced programmers.
Improper garbage collection is another extremely common bug that becomes harder to find and debug with multi-threaded programming, and that can also lead to memory leaks.
There are time tested techniques to mitigate these issues and strategies to find and squash the bugs, but as you said, they can be extremely hard to reproduce while testing.
Windows Store has more mobile games that have been ported to Windows 10 than Steam or GoG. I've also seen a lot of "free" games that have huge advertising banners covering most of the screen. They're the same type of cheap and easy to make clones filled with advertisements and pay-to-win crapware that you'll find on any other mobile platform.
These aren't AAA titles, nor are they decent, older games with great gameplay like you'd find at Steam or GoG.
The future's good and the present is nothing to sneeze at. I've used Audacity as my primary audio editor for years. Admittedly, my requirements are pretty lightweight, but it does what I need.
What you're talking about is a forward proxy. Forward proxy servers do this (and will even proxy SSL traffic).
In the whitepaper, they're actually talking about making a new protocol that measures the one way distance time and compares it to their database of network speeds and distances to determine your location. Their solution is an application-level solution, which depends upon a Forward Proxy to know about the protocol and spoof it correctly.
The problem with their solution is that network speeds are fluid and a computer with a problem (e.g. a local neighborhood node or a legitimately slow client that is delaying all traffic 20-30ms) can make their estimates wildly inaccurate. Even today, Cogent to Level 3 has a 197ms ping in LA. In the paper, they used average speeds for various known networks. This can be mitigated somewhat by measuring client traffic and only counting outliers (e.g. all traffic from a certain area being delayed the same, except for our rogue client) but it still doesn't mitigate the local computer problem.
A second problem with their solution is that it only measures distance - a server in Miami, Florida accepting data from a client in Seattle, Washington is 2732 mi and the same distance (roughly) as Lima, Peru. This means that a client in Lima should pretend to be from Seattle when they connect to their combo VPN/Forward Proxy in Miami. Satellite customers are will almost always have extremely high latency because of the round trip between Earth and the Satellite, even if they're legitimately in the correct area.
In addition, they were only able to make this accurate to about 400km, which means if you have a nearby beneficial country within that range, you can use a VPN in that country and they still won't know.
2 30-second preroll ads? Barf. I've always considered 15 seconds -- or "skip ad after 5 seconds" -- the maximum that should be inflicted on readers/viewers. I'll check with our ad and tech people, see what's happening. I know a lot of publishers consider 30 seconds okay, but 2X30 seconds? Not good, but obviously not under the control of anyone who actually works on the site. Sigh.
Thanks for catching the typo. Fixed.
That's a question the lawyers are starting to wrestle with. What if you're handicapped in some way? How does the ADA apply?
"Never ascribe to malice that which is caused by greed and ignorance." -- Cal Keegan