Hacker Newsnew | past | comments | ask | show | jobs | submit | SecurityLagoon's commentslogin

Protip on Firefox is to head into about:config and toggle dom.event.clipboardevents.enabled to False.

This will prevent all websites detecting clipboard events and it defeats a lot of the annoying website behavior without needing to disable javascript entirely.

The only things it may break is if you legitimately do use any web apps that need to detect clipboard events; but, I have yet to run into anything.


> or if you have ever done so

Do you not think that most people who have stopped using animal products have not already come to the conclusion that what they did was (direct or indirect) killing and they deemed it as immoral? Using this argument in an animal ethics debate is ineffective at best.


This is the same argument used for meat production and is questionable. Would you really care that your murderer treated you well before killing you? Or would you feel even more betrayed?

This pig would have lived a very short and probably isolated life (to isolate from pathogens). No matter how well it was treated in life it was still forcibly operated on and/or killed at the end.


That's the same as slurring at someone in a language they don't know. They don't understand what you meant so it doesn't matter right?

The point is not the animal's comprehension of the term but the implication that the animal gave consent to have their organs harvested by saying "donor". If you argue that the pig cannot understand English so can't be offended the same applies that they can't understand English so cannot give affirmative consent.


Exactly.

I work in cyber security and I am more convinced by the day that the answer is not having the data to steal rather than attempting to mitigate every possible threat.

This combined with zero trust and 2fa/passkeys will go much further than many other snake oil solutions the industry loves.


> Once you’ve got them, even if you’re more established, it would be crazy to leave them off of your resume, right?

For sure include them if they are relevant to the role or show real commitment to a topic. If you see a string of disperate certs though it's easy to assume the applicant doesn't know what they want to do.

Not saying I would discount someone on this alone but it would raise questions for the interview if they were otherwise qualified.


And that's totally fine. We all have our own heuristics for determining what we like in a candidate, but we need to be very, very critical of those measures and make sure they aren't masking other less justifiable gut instinct decisions. Bias is generally subconscious— If it really was as cut-and-dried as we like to think, then it wouldn't be a gut feeling metric at all— we'd be able to back up our reasoning with hard facts. As rational as they might seem, 'gut feeling' criteria almost universally favor people we're comfortable with rather than the most qualified candidate. That's a real problem for folks who aren't part of the dominant culture of the industry: Millenial to Gen-X straight white and asian guys.

If a qualified candidate only having certificate credentials merely prompts further investigation, then great. However, it's quite often the tipping point between round-filing a good candidate and calling another one in for an interview. While it might seem innocuous on a micro level, on a macro level this affects big swaths of the population.

In the 2005 Study Are Emily and Greg More Employable than Lakisha and Jamal (https://www.nber.org/system/files/working_papers/w9873/w9873...), they responded to 1300 job ads with 5000 equally-weighted resumes with randomly assigned names which were either stereotypically white, like Emily Walsh or Greg Baker, or stereotypically black, like Lakisha Washington or Jamal Jones. Resumes with white sounding names were 50% more likely to receive a callback. Fifty percent! The likelihood of 1300 randomly chosen job ads being run by the KKK is pretty low. Most, if not all of them were probably letting "gut instinct" criteria swing their judgement.

If you had a video game where the sole task was getting a job, one race having a built-in buff where the callback was 50% greater without being balanced somewhere else would be insanely unfair. Not only is it not balanced, but we're literally only talking about these folks names— never mind their appearance, manner of speaking, cultural references, etc.

We all like to think of ourselves as good people but that's not enough to stop this. We need to deliberately interrogate our MO, here.


Also very interested in this one. I do some casual locksport but would love to be able to legitimately carry tools and help out friends and colleagues.


Oh no.... I think we have very different definitions of fun. I haven't touched UML since uni and I'm glad to keep it that way.


That's really interesting. I have used gather.town for conferences before and it works really well - but I haven't seen it used on an ongoing basis. It does make sense in a lot of ways to incorporate some of those physical cues of an office environment into a WFH setting.


It's strange but really cool to zoom out and see various meetings between people in different rooms, or when we bring an outside contact into our space for a meeting you can introduce them to coworkers ad-hoc (like a real office).

Swinging by with a guest, like other real world experiences translated into a 2D world, require developing a new set of social norms. For instance, if you're screen sharing through their app, you won't see someone approaching and the screen share feed will show up expanded by default for whomever enters. That can be problematic for a number of reasons (client data, personal info you were sharing with a close coworker, etc.).

We also have recreated games like tag using the confetti feature, have rituals like hitting a lap around the entire space on go karts after code reviews, and occasionally raid Client Experience's office for supplies.

It is a jealous god when it comes to CPU though and since modern JS environments are greedy as well, my fan gets a lot of work.


Should 100% demand a work supplied device for work. Or at worst buy a cheap second Android to use as a work device. There is no circumstance where using your main personal device for work is a good idea.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: