Recent submissions

Comment · 3 months ago
Damn, this one hit hard. Grew up watching him on ZDTV/TechTV. RIP.
Comment · 1 year ago
I set my son (8) up with a ChatGPT account and he loves it. He uses it to generate scripts for Roblox Studio, recipes to cook, etc.

I used the "Instructions" field to indicate he is only a child and to interact with him appropriately, and overall it does a decent job keeping the language somewhat simple when chatting with him.

Comment · 1 year ago
Wow this triggered some neural pathways I forgot I had.

I remember using both of those clients.

Comment · 2 years ago
Damn, I’m reading Thinking Fast and Slow right now. RIP.
Comment · 2 years ago
Comment · 2 years ago
I'm confused -- wasn't ChatGPT upgraded to 128k tokens at their last release? Or was that just the API?
Comment · 3 years ago
What went wrong is that after being divested from Condé Nast, reddit went and raised a huge round that ensured they would have to go down the route of synthetic growth tactics.

This whole operation could be wildly profitable with a team of 50-100 people and no major investors to appease.

Instead they read the room wrong, or just didn't care, and now we're here.

Comment · 3 years ago
1. Wow a thing, people seem to be excited about it.

2. Are people excited about my thing? Am I excited about it?

3. Have I made the wrong life choices?

4. This makes me feel uncomfortable.

5. If I can defend my life choices I can feel good again.

6. I will downplay this thing, that will resolve my uncomfortable feelings.

Comment · 4 years ago
It's a little hard to parse parts of that paragraph, but it sounds like the repo (presumably hosted on GitHub) had access tokens granted to third party integrations (similar to Heroku being granted access to GitHub on behalf of their mutual users).

Assuming that's true, it should be trivial for GitHub to tell them which third party integration the token was associated with.

Comment · 4 years ago
I just received an email back from an Incident Handler at Salesforce. I wrote:

> A statement that confirms whether or not config variables and secrets were accessed, or that you're not sure, needs to be sent out.

To which they replied:

> We currently have no evidence that Heroku customers’ secrets stored in config Var were accessed. If we find any evidence of unauthorized access to customer secrets, we will notify affected customers without undue delay.

Take that as you will, but it doesn't fill me with confidence.

Comment · 4 years ago
Comment · 4 years ago
This is turning into a complete train wreck and a case study on how not to communicate with your customers.

For those of you that haven't been following, Heroku has been adding non-update updates to this security thread over the last couple of weeks, which began with the announcement that some (or maybe all) of their GitHub granted access tokens had been compromised: https://status.heroku.com/incidents/2413

Now, weeks later, we're hearing that all account passwords are being reset, and for some reason if you have been using an HTTPS-style log drain that you should reset any secrets related to it as well.

Heroku needs to come out and clearly state what they know about this situation, and more importantly what they don't know -- which is starting to sound like the answer is "a lot". It's not even clear they know how this all happened -- whatever door was left open might still be open. So if you've gone and rotated all of your application secrets (which you probably should do), be prepared to rotate them again when this is all over.

Comment · 4 years ago
It’s not really about being justified, it’s about being gentler with people. We don’t have to jump all over each other, there is another way.
Comment · 5 years ago
Yep, I’ve been referring to this as “work locally”, and I also feel this is an ideal balance, although it does limit your access to talent.
Comment · 6 years ago
I once jokingly said it to an employee and immediately felt bad about it. Did a quick all-hands (we're a small company), apologized and said it wouldn't happen again.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton