The Pirate Bay is mining cryptocurrency again, causing a spike in CPU usage among many visitors. For now, the notorious torrent site provides no option to disable it. The new mining expedition is not without risk. CDN provider Cloudflare previously suspended the account of a site that used a similar miner, which means that The Pirate Bay could be next.

https://torrentfreak.com/pirate-bay-is-mining-cryptocurrency-again-no-opt-out-171011/

https://techcrunch.com/2017/10/10/nvidia-built-a-real-holodeck-aimed-at-creative-collaboration/

https://techcrunch.com/2017/10/09/a-chat-with-the-creators-of-arduino/

https://techcrunch.com/2017/10/07/google-parent-alphabet-looks-to-restore-cell-service-in-puerto-rico-with-project-loon-balloons/

https://youtu.be/As8XkJNaHbs

https://www.theverge.com/tldr/2017/10/3/16412372/star-trek-discovery-cbs-windows-code-command-line

https://fossbytes.com/google-engineer-religion-develop-ai-god-way-of-the-future/?utm_medium=browser-notification&utm_source=onesignal&utm_campaign=notification-engagement

here were six hours during the night of April 10, 2014, when the entire population of Washington State had no 911 service. People who called for help got a busy signal. One Seattle woman dialed 911 at least 37 times while a stranger was trying to break into her house. When he finally crawled into her living room through a window, she picked up a kitchen knife. The man fled.

The 911 outage, at the time the largest ever reported, was traced to software running on a server in Englewood, Colorado. Operated by a systems provider named Intrado, the server kept a running counter of how many calls it had routed to 911 dispatchers around the country. Intrado programmers had set a threshold for how high the counter could go. They picked a number in the millions.

Shortly before midnight on April 10, the counter exceeded that number, resulting in chaos. Because the counter was used to generating a unique identifier for each call, new calls were rejected. And because the programmers hadn’t anticipated the problem, they hadn’t created alarms to call attention to it. Nobody knew what was happening. Dispatch centers in Washington, California, Florida, the Carolinas, and Minnesota, serving 11 million Americans, struggled to make sense of reports that callers were getting busy signals. It took until morning to realize that Intrado’s software in Englewood was responsible, and that the fix was to change a single number.

https://www.theatlantic.com/technology/archive/2017/09/saving-the-world-from-code/540393/

As the 184-metre-long tanker was docking in Novorossiysk, Le Meur was on the ship’s bridge overseeing the final approach. Suddenly, the ship’s warning signals started blaring. “As soon as the GPS lost the signal, we had tons of alarms,” he says. “You cannot miss it. Pretty much everything on the bridge started raising alarms.”

Instead of displaying Atria’s actual position, the ship’s systems located it 25 to 30 miles away – at Gelendzhik airport. GPS disruptions aren’t uncommon, Le Meur says, but most of the time when problems happen they’re limited to a few hundred metres.

“In my entire career, it’s my first time I have experienced such a big discrepancy.” To be sure of the failure during the incident in June, the crew restarted both the main GPS and the backup unit, only to find both systems still gave the same incorrect positioning data.

https://www.wired.co.uk/article/black-sea-ship-hacking-russia