1,853 karma · joined March 24, 2013
Personal: erictj@gmail.com Twitter: @etjossem
Kindly avoid posting it to HN every day. Post the articles Levine links to instead, if you must.
That's the main concern going through my mind when I see this. It would be different if the average user was a business, a developer, a security professional - but this isn't Heartbleed and we're talking about normal people this time. Are they even going to read this, and if so, what can they do besides keep an eye on their permissions?
Definitely a factor to take into account, particularly when deciding how the information will be publicized.
If you as a security researcher reasonably believe the vendor has neglected to patch the vulnerability, and you release exploit details, you have made things less safe for security-unaware users. There's no way around that. You already gave the vendor the opportunity to fix the problem. Now you are giving attackers the tools they need to take advantage of it.
You and I might care about abstract principles of corporate responsibility, but the typical user just wants to avoid getting phished, and I can't help but feel open disclosure has a lot of potential to harm them. I hope it's worth it.
> Current — All the attacks discussed by this work are still practical, even with latest version of Android (Android 7.1.2, with security patches of May 5th installed).
Honest question - does HN feel this is actually responsible disclosure? A large number of Android devices seem to be vulnerable to the issue, and the whitepaper includes exploit details. Is the intent to force Google to pay attention to the issue?
Taking care of each other is steeped into the culture, and I wouldn't be surprised if that's why we see a far lower rate of hospitalization.
Your mileage may vary! But this is exactly my point: when a group of you get together to take mushrooms, you recognize the need to have someone sober around to take care of everyone else and make sure they're safe.
For comparison, let's look at alcohol - you're very lucky if you can find someone willing to be the designated driver, let alone a group where emphasis is placed on keeping each other safe. There's even a level of taboo around slowing down those who are drinking too much.
It doesn't surprise me how many people are hospitalized for alcohol overdose or related accidents. The culture is very different.
The decision to ingest mushrooms isn't a matter of psychological need (as it sometimes is with alcohol or amphetamines), and it's very rarely made out of impulse in a social setting (e.g. ecstasy). It is typically a deliberate choice with the expectation of having a psychedelic experience - complete with the understanding that it might be a bad trip. You do as much prep work as you can beforehand to make sure it's comfortable.
Taking care and preparing for the high isn't really baked into the culture of other drugs in the same way.
This is a your-mileage-may-vary thing and there is no easy answer for all cases.
Your example sounds perfectly fine! But if you've spent decades building "3D animation engines for games" at various companies that do so - and that's basically your career now - you won't be helped much by being specific about what type of work is considered competition. YMMV, so concede only in ways that leave your options open.
- Are fairly new to the industry or are otherwise trying to act in a buyer's market for labor,
- Are being offered market-rate or lower with no extra incentives, and
- Have a potential employer trying to foist a noncompete on them for no particular business reason.
Understand the employer's business model and whether noncompete will be a sticking point for them. If it is, then the situation is very different, and you should be asking for lots of money rather than the clause's removal.
If they're cool with it, sign the clean employment agreement together on the spot. Make copies and you're done.
The difference is that with an illegal contract, your future employer might actually believe it's more headache than it's worth to fight. I would err on the side of casually striking it out of the employment contract, simply saying "this part of the standard document doesn't apply in our state" etc.
So no, a noncompete - even one that only applies to the time you are employed by the company - isn't typically necessary.