HN user

kenperkins

192 karma
Posts4
Comments53
View on HN

I think the premise is that modern scanners are really good at finding malicious code (and are run by dozens of companies in the industry), but when it gets pushed and installed inside of that 7 day window, the spread is uncontrolled. This basically gives you opportunity to let the machinery in the package ecosystem do it's job.

GoDaddy | 2 Mid Level Positions | Platform/Data Software Developers | Full-time remote ( Pacific/Mtn/Central mostly )

I'm the hiring manager for the Social Platform team at GoDaddy; we're building data pipelines and services (on AWS) to drive insights and connectivity to social networks for our GoDaddy customers. A huge number of our growing customer websites are built on how they interact with their customers on social networks, and we're building a team to facilitate the tools and data driven insights that power these new experiences. If you're into that and cloud-native tooling, we should talk: kperkins at godaddy dot com if you want to chat. The team is fully remote, and is going to stay that way.

https://boards.greenhouse.io/godaddy/jobs/4630550003

No they don't. Researchers propose they (the carmakers) do.

I can't even imagine the maintenance or repair considerations of a pack that's embedded inside of the frame or a monocoque chassis.

Lastly this isn't even an Ars article, it's from Wired. It really is a terrible click-bait headline. The article, imho isn't much better.

I think it is a valid question when the defaults are google and there is a reasonable suggestion to not use google as the defaults in lieu of community or open-source options. When that question isn't answered (evaded) it's perfectly reasonable ask why.

My 7 and 9yo kids start school at 8:50am, and don't get off the bus until 4:30pm. It's ridiculous. They're young and need time off but because the district moved everyone back to make room for the High Schools now elementary kids aren't home until half past 4.

Not enough time for them to play in the afternoons now.

Well I'll give them credit for being able to recognize and reverse a mistake. That's a good sign for the future.

It's very concerning that they made that call in the first place. It should never have been reversed because they shouldn't have done it. I'm a huge fan of Tesla, but I can't help but say it feels completely chaotic atm.

Most people have no desire to go to a theater anymore, so making people wait months to see a new film means they're going to try to find a way to see it sooner. If they released streaming alongside movie theater releases I would imagine you'd knock out 90%+ of the piracy out there.

Aside: Saw Pets with my kids this week; Large Soda is now more than a Bud Light at a Football game ($8). Consider me among those who would gladly stop going to the theater.

I think this is on the management as much as the employee. I'd hope employees look for more work to do as opposed to just taking a paycheck.

We've all had times where we're not fully invested in our work. Sometimes even weeks, maybe months in extreme circumstances. 6 years is absurdly bad. I can't imagine the management getting off lightly here either.

Instead of asking what else he can do, or provide more value or grow into more responsibility, he sat on his hands and played League all day?

I'm disappointed it took them 6 years to act on it.

People who find vulnerabilities purely for the bounty seem to fit the classical definition of Bounty Hunters or Mercenaries. Certainly not researches. They're not in it for the academic benefit or advancing the state of the art. They're in it for the cash.

I've felt for quite a while that we could have had a 4 octet semver that allows for a first octet romantic version while the others are proper semver.

For example: io.js version 1.2.0.0 instead of 1.3.0.

It would still be machine readable, but allows a human component (romantic version) to precede.

Thoughts?

It's not dead pixels that you notice; I have a hot pixel on my Retina MBP, and it's very noticeable. But Apple doesn't warranty a single hot/dead pixel.

Ideally yes, it's running on a different machine. But most certainly a different process.

For the queue, I've wrapped redis and rabbitmq clients with a simple retry logic that re-enqueues the job on failure to send. It's about choosing what's right for your use case.

Regardless of which package you use for delivering email, I can't recommend enough to put the email delivery code into an async job queue that automatically retries.

Even with major providers there are enough occasional blips that you don't want to impact delivery of your email. Additionally, it would allow you to decouple sending (popping from the queue) if you ever needed to delay it momentarily.

Really neat. I enjoyed scrolling to earth. After that it became painful.

Thankfully, the solution was easy:

Open Chrome Inspector Console:

$('.essay').css({ left: '20px', marginBottom: '15px', maxWidth: '600px', position: 'relative' });

$('#bigspace').css('left','inherit');