chrismarlow9

I actually think network ACL triggers based on billing might be the only way to really enforce this.

I witnessed a DDoS attack once that changed how I think about billing. It was locally provisioned hardware and the attackers had saturated the switches. Naively I said "just block the CIDRs" but the problem was the incoming ram is so saturated that it can't even get to the point of "deny" in the firmware.

So from a technical perspective if there's an internal DDoS at AWS what do you do? Do you turn off the endpoint? Do you drop the sources from hitting it at the router? And even that costs money. Anyway that incident gave me a different level of appreciation for this challenge.

Edit: this is mainly targeted at the people complaining why this took so long. At some point in scaling even telling you "no sorry" in a nice way is expensive. I'm sure recruiters can sympathize with this nowdays.

https://naehrdine.blogspot.com/2024/11/reverse-engineering-i...

Tl,dr: it's likely baked into the sep, no ntp

I'm wondering if you put the phone into a mode where it thinks it's dialing emergency services or contacting them via crash detection etc that it won't reboot. I could picture a scenario where the code is written to never disrupt an emergency services call.

Full disclosure I don't own an iPhone so this may not even be a thing. Just guessing based on liability risk from Apple of "what's more important than protecting the phone"

I can't even fathom the trend these days of "we don't review the code" from security team perspective.

Just my guess though.

Overall I agree though, this is a bit of an abuse of that concept.

EDIT: I'm sure op is familiar with this workflow but I'm being overly verbose to clarify what I think they mean and my thoughts.

"Expand. Clarify for human. 5 minute read max. Senior engineer audience."

```

~/.config/opencode/AGENTS.md

~/.claude/CLAUDE.md

~/.codex/AGENTS.md

~/.copilot/copilot-instructions.md

~/.gemini/GEMINI.md

```

Define it as a graph and iterate. I use more tokens, but I can also use more tools without disruption. Delegating markdown to folders/smaller repos can solve the tokens/context issue.

I see it like cloud computing. We were told infrastructure engineers wouldn't be necessary and anyone could build at scale now and blah blah. Instead we got Terraform and solid practices for infrastructure as code and moved beyond having to email some dude to get a new VPS or dedicated server spun up and making trips to the colo. It just changed the possibilities of what we could build.

I've been treating AI the same way and just leveled up what I build now and my ambition. It has helped a great deal with being okay with AI. All those fun insane projects in my head that I never figured would happen because "it would take a full team months to code that" are realistically possible. Big things that used to be entire companies are now possible. You hate Google search now? Guess what, you can make your own!

I don't treat my side projects purely as an "end goal" anymore but as a learning experience now. I slow down and actually read the code. These are my own projects. Then I take these things I learn to work and apply them. That's how it's always been when new tech comes along. I also hated kubernetes when it first came, but have now settled into "it has it's place". I learned about myself a bit and that I should be a little more open to change if for no other reason than peace of mind.

The targets in the spam world (email and seo) that want to make money want the low hanging fruit. They want uneducated people to visit the site. I remember when google was still young, these same people wanted visitors from AOL. Why? lower traffic and much higher conversion. What kind of person uses AOL when google is available? An uneducated one and a new one to the internet. Or an older person who is likely to fall for a scheme.

I suspect more and more visitors coming from google will be seen this way in the age of AI and social media searching. Easy targets. Whether it's true or not is debatable (maybe people just want to read a real webpage and have AI burnout). Anyway thanks for coming to my ted talk.

This is the part of it that bums me out the most. I just wish aesthetics didn't drive so much of the current tech world. Everything has an absolutely beautiful interface now that is slow, buggy, can't be shared, etc. But I guess at least it's pretty and pays the bills.

My life of working with it got easier when I started just looking at the actual code, using network level tools like nc/tcpdump, making extensive use of the debug exporter, and almost ignoring the docs entirely except as a basic summary of what a thing does.

Seems to indicate a collection cron with a manual query to truncate can fix it. This is fun little things I like to learn. SRE Easter eggs.

Edit:

To be clear still interesting finds. I think with some chaining some of them might be more severe. Like the ovpn one and windows potentially registering vpn app as default open or some protocol opener for a url location like openvpn:// in an I frame and some clever social engineering. Just a random thought