I think about it like this - seed oils are in nearly all processed foods. Read the labels of anything in your house that's in a bag, or will not expire in the next week. 95% chance there is sunflower/canola/safflower/sesame seed oil in it.

By avoiding seed oils, you tend to eat more whole foods. It's not an awful cue to pay attention to.

if the seed oils in Cheetos are not the problem, what is it? the flour?

The amount. The western diet includes tons of snacks and additional sources of calories like soda.

Could be ingredients that are complete non-foods, such as artificial colorings.

anecdote for anyone else reading about Covid related tinnitus - I've had hearing damage related tinnitus for a decade. Got Covid in April '22 which caused my existing tinnitus to 2-3x in severity, lasting a couple months before it either reverted to baseline or I got used to the new normal. Very scary experience. The CEO of Texas Roadhouse famously committed suicide due in part to severe post-Covid tinnitus.

For anyone struggling to cope with Tinnitus out there, one thing that has helped me immensely is Zen meditation. Doesn't make it go away, but builds up a control over attention with which you can cope much better.

where did you get testing done?

I got blood testing through the MIPHES study:

https://www.michigan.gov/mdhhs/safety-injury-prev/environmen...

And well water testing through the Michigan DEQ, county health department, performed by Rose and Westra GZA:

https://www.accesskent.com/Health/PFAS/contact.htm

Culligan Water installed and serviced our whole-home water filter system until a township-approved excavation contractor was able to connect us to municipal water, which was funded by a separate lawsuit against Wolverine/3M.

No idea what (if any) the consequences were for the executives in the 70s and 80s who dumped chemical waste and leather scraps in a swamp behind a friend's farm upstream from my house, or their successors in the 90s who covered it up.

it's well known and not debatable that Cinnabon is fire

>The one service token and three accounts were not rotated because mistakenly it was believed they were unused.

This odd to me - unused credentials should probably be deleted, not rotated.

This smells weird, surely? I'd be looking at who chose not to rotate those particular credentials.

1: "what are these accounts?"

2: "oh they're unused, they don't even appear in the logs"

1: "we should rotate them"

2: "no, let's keep those rando accounts with the old credentials, the ones we think might be compromised ... y' know, for reasons"

?

More likely: "no one has any idea what these old credentials do, so let's not touch them and potentially break everything"

Sounds like the perfect time to revoke the credentials and find out what uses them, so we can find why they weren't registered as credentials in use. Personally I'd rather do that, have a team ready, and break production for x minutes in order to properly register auth keys.

I'd definitely consider a "silent" credential - a credential not registered centrally - to be a huge red flag. Either it could get stolen, or break and no one knows how to regenerate it. And it's pretty easy as devs to quickly generate an auth key that ends up being used permanently, without any documentation.

> Personally I'd rather do that, have a team ready, and break production for x minutes in order to properly register auth keys.

Sure, but you aren't going to do all that when your team is juggling N other priorities. At least, it will be very difficult getting mgmt and others on board. Unless it's explicitly in the context of a recent breach.

Very true. Ideally the culture would be that we’re experiencing some pain now to avoid more later, so we should do it - I’d hope management was on the same page. Real world, unfortunately, often differs.

this is more plausible to me

Agreed. This whole post reads as "I'm the victim" but they don't admit on the one mistake that snowballed

congrats! Really crisp idea, excited to try this out

Thank you! Hope you will like it

didn't see any mention of caching in the docs. This tends to be pretty important for fast build/CI at many different key points of a given workflow (dependency cache, build cache, docker layer cache, image cache, etc). Wondering if I missed something.

we have no theories of intelligence. We're like people in the 1500s trying to figure out why and how people get sick, with no concept of bacteria, germs, transmission, etc

using it for an internal Golinks service