4 ms·
The part about viewing family.html seems kind of understandable. If you assume no bad actors, then it's crazy... But we're all developers here, we know that you
by chipperyman573 8y ago
The part about viewing family.html seems kind of understandable. If you assume no bad actors, then it's crazy... But we're all developers here, we know that you have to assume the existence of bad actors, and assume that they are going to target you (which is why we you always validate data client data server-side). I could see how viewing family.html could turn into a real headache for HR/Legal, especially if the law says that you can't discriminate based on family information.
The other part about log analysis seems crazy, though, I agree with you on that.
- deleted 8y ago[deleted]
- hombre_fatal 8y agoWe're talking about evidence in a discrimination court case that points to an IP address associated with a company that visited /family.htm around the time someone applied for a job they didn't get. Like, that person went through their blog's access.log when they got home, defeatedly looking up IP addresses, and going "aha, jackpot!"? And everyone in the company hovers links to be sure they don't go to /as-a-black-man.htm during the hiring process? And the fear seriously is that prefetching might be what spurs this chain of events? That sounds batshit insane.
- scarejunba 8y agoYes, I can't see how anyone could think this is sane in any sense. Brb putting my kids in my GitHub profile picture.
- Gaelan 8y agoA while back I saw a chrome extension that hid profile pictures on GitHub specifically for this reason.
- hueving 8y agoJust go right for the kill and put your marital status, ethnicity, and sexual preferences right below your name on your resume. That way they're trapped the instant they open it!
- deleted 8y ago[deleted]