HNHacker News
TopNewBestAskShowJobs

SoReadyToHelp

157 karma · joined April 13, 2019

submissionscomments
SoReadyToHelp··on 'I wash all my food like crazy': scientists voice concern about nanoparticles
Says the Linux communist.
SoReadyToHelp··on 'I wash all my food like crazy': scientists voice concern about nanoparticles
You need to move to a better city.
SoReadyToHelp··on Huawei’s Ace in the Hole: Undersea Cables
"Encryption is so expensive!" cries the 1990s
SoReadyToHelp··on Vignette: add photos to your contacts by searching public social media profiles
I couldn't find the vignette filter in this app. Can anybody help?
SoReadyToHelp··on PEP 594 – Removing dead batteries from Python's standard library
> So what reason is there for adding a new string formatting syntax that looks nothing like string formatting syntax used in any other language

The new syntax is more like other modern languages, not less.

SoReadyToHelp··on JavaScript Array.push is 945x faster than Array.concat
It's not 945x faster, it's O(N) faster.
SoReadyToHelp··on Getting my personal data out of Facebook
The typical approach is to keep the PII in the backups encrypted with a user-specific key which is stored separately and can be deleted without touching the backups. I'd expect Facebook to do the same, but who knows?
SoReadyToHelp··on US has underestimated Huawei, says founder
No, they just do it in slightly different ways than Americans so it's framed as something exotic and weird instead of typical human behaviour.
SoReadyToHelp··on Update to Security Incident
The user in question uses a nonunique pseudonym and Tor, so I'm not sure if they actually want attention. Maybe they were also the hacker. ;)
SoReadyToHelp··on Update to Security Incident
I believe they were polling the list of moderator-or-greater-access users on each site through the API: https://api.stackexchange.com/docs/moderators
SoReadyToHelp··on Update to Security Incident
As it happens, this incident was discovered by a curious user who had a script watching for new accounts with staff privileges, who brought the attacker's account it to the company's attention (in chat) because it looked unusual.

Stack Overflow seem to be following a very responsible incident response procedure, perhaps instituted by their new VP of Engineering (the author of the OP). It is nice to see.