Four short links: 23 March 2018

Tech Facts, History Lesson, Chrome DevTools, and Online Communities
  1. 12 Things Everyone Should Understand About Tech (Anil Dash) -- must read. Some "obvious" things in our world that aren't obvious to people outside it (or, indeed, to everyone in it). Tech history is poorly documented and poorly understood. [...] It’s often near impossible to know why certain technologies flourished, or what happened to the ones that didn’t.
  2. AI, Functional Programming, OOP (Alan Kay) -- fascinating reading for the historical perspective on time-tagged data, state, consistency, and scale. John started thinking about modal logics, but then realized that simply keeping histories of changes and indexing them with a “pseudo-time” when a “fact” was asserted to hold, could allow functional and logical reasoning and processing. He termed “situations” all the “facts” that held at a particular time—a kind of a “layer” that cuts through the world lines of the histories.
  3. Cool
    Continue reading "Four short links: 23 March 2018"

Four short links: 22 March 2018

Security Policy, Censored 3D Printers, Standup Tips, and Auto-Banning
  1. Protecting Security Researchers -- Dropbox issues, amongst other good steps toward public security researchers, a pledge to not initiate legal action for security research conducted pursuant to the policy, including good faith, accidental violations.
  2. Early-stage Malicious Activity Detection in 3D Printing -- teaching a 3D printer to recognize that it's being used to print a gun, so it won't. (via Miles Brundage)
  3. 5 Ways to Tune Up Your Standup -- Teams need to start thinking of impediments in terms of "what is slowing me down" rather than "what has stopped me." Testify!
  4. Fail2Ban -- scans log files (e.g., /var/log/apache/error_log) and bans IPs that show the malicious signs -- too many password failures, seeking for exploits, etc. Generally, Fail2Ban is then used to update firewall rules to reject the IP addresses for a specified amount of time, although
    Continue reading "Four short links: 22 March 2018"

Four short links: 21 March 2018

Incident Response, Google VPN, Deep Learning, and Neural Network Quine
  1. 10 Steps to Develop an Incident Response Plan You’ll ACTUALLY Use (Salesforce) -- high-level process, but solid.
  2. Outline -- self-hosted VPN from Google.
  3. nGraph -- open source C++ implementation of a framework-neutral deep neural network (DNN) model compiler that can target a variety of devices. Intel's software entry into the neural network space. Why Intel? Users can run these frameworks on several devices: Intel Architecture, GPU, and Intel Nervana Neural Network Processor (NNP).
  4. Neural Network Quine -- clever! I have a Python quine scarf, but I'm not sure I'm going to enjoy this so much. Here we describe how to build and train self-replicating neural networks. The network replicates itself by learning to output its own weights.
Continue reading Four short links: 21 March 2018.

Four short links: 20 March 2018

Magic Leap, Autonomous Death, Computational Cognitive Neuroscience, and Analysis of Competing Hypotheses
  1. Creator -- Magic Leap released their SDK, with some details of the product, including: eye tracking, persistent location tracking across multiple locations, small field-of-vision, can't draw black, etc. (The HN commentary is informative)
  2. Uber Autonomous Car Hits Pedestrian -- first of many. This is where the rubber of the (faith-based) statistical argument "machines will kill fewer pedestrians than people do" meets the road of human emotional perception.
  3. Computational Cognitive Neuroscience -- This is a new wiki textbook, serving as a second edition to Computational Explorations in Cognitive Neuroscience.
  4. Open Synthesis -- an open platform for intelligence analysis. We're taking the best practices from the intelligence and business communities and adapting them to work at internet-scale. Open source, too.
Continue reading Four short links: 20 March 2018.

Four short links: 19 March 2018

ML Reproducibility, Data Research, Blockchain IP Crimes, and PLATO Flashback
  1. The Machine Learning Reproducibility Crisis (Pete Warden) -- Even the original author sometimes couldn’t train the same model and get similar results! He was hoping that I had a solution I could recommend, but I had to admit that I struggle with the same problems in my own work.
  2. Facebook and Cambridge Analytica (Guardian) -- horrifying. We exploited Facebook to harvest millions of people’s profiles. And built models to exploit what we knew about them and target their inner demons. That was the basis the entire company was built on. Short story: researcher makes quiz at a time when Facebook's API gave out A LOT of data, then uses that data for purposes beyond T&Cs. Takeaway: if you manage personal data, a burden upon you is to work closely with researchers who want to access it so that you can
    Continue reading "Four short links: 19 March 2018"

Four short links: 16 March 2018

Longevity, Partner Violence, Leaking Secrets, and Fallacy of Objective Measurement
  1. Longevity FAQ (Laura Deming) -- I run Longevity Fund. I spend a lot of time thinking about what could increase healthy human lifespan. This is my overview of the field for beginners.
  2. Intimate Partner Violence -- What we’ve discovered in our research is that digital abuse of intimate partners is both more mundane and more complicated than we might think. [...] [I]ntimate partner violence upends the way we typically think about how to protect digital privacy and security. You should read this because we all need to get a lot more aware of the ways in which the tools we make might be used to hurt others.
  3. The Secret Sharer -- Machine learning models based on neural networks and deep learning are being rapidly adopted for many purposes. What those models learn, and what they may share, is a
    Continue reading "Four short links: 16 March 2018"

Four short links: 15 March 2018

Traffic Attacks, VR/AR Audio, Travel Bot, and Location Codes
  1. Adversarial Traffic (Paper A Day) -- What if an adversary—perhaps just a single vehicle—tries to game the system? Maybe to try and speed their own passage through traffic light junctions, or perhaps to deliberately cause congestion and bring traffic to a halt. The authors look at data spoofing attacks on the I-SIG system, targeting design or implementation issues in the signal control algorithm (i.e., not relying on implementation bugs). [...] Using just a single attack vehicle, the total traffic delay at a junction can be increased by up to 68.1%, completely reversing the expected benefit of the I-SIG system. Attacks can also completely jam entire approaches—in the example below, vehicles queuing in left-turn lanes spill over and block through lanes, causing massive traffic jams. 22% of vehicles take over seven minutes to get through the junction, when
    Continue reading "Four short links: 15 March 2018"