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.
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.
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.
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.
Very confusing! To clarify for others, what they mean is that if there was a secret embedded in the log drain URL, rotate it. This is often the case for HTTPS log drains.
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.
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.
I recently visited San Diego and was absolutely blown away by how many scooter companies were operating there, and how many unused scooters I saw lying around.
I just started reading books again in the last couple of years and I think it’s definitely worth it.
My recommendation is that you start with a physical book and not an ebook or audio book. It might test your attention span at first, but it’s the best way to get your focus back and you’ll find that your reading speed and comprehension will start to improve. Also, it’s nice not having to charge them ;)
Been building Django apps for almost 10 years and after seeing the amount of wasted time going into organizing things into apps, I settled on this technique.
It doesn’t really swim against the current as long as you import models into the __init__.py file in their package.
I don't use multiple apps anymore and instead treat the project as the app, so my directory structure looks something like this ('project' can change to something specific to what you're working on):
* manage.py
* project/settings.py
* project/urls.py
* project/models/ (each model gets it's own file here)
* project/views/ (same for views)
...and so on. And in `INSTALLED_APPS` I just add 'project'.
Makes it so I don't waste a bunch of time trying to figure out which app to put a model in, etc.