I feel like it's the same with your first phone number back when there were only landlines, etc. Some numbers are hard-wired.

It seems like an edge problem for an edge use case, but I guess At Go’s scale, it’s probably important.

Buy Ruckus, it’s high quality hardware, but you’ll be paying enterprise prices for new hardware. But used hardware is fine.

So I needed a reproduce. Which couldn’t be done. Very frustrating, as it is our own application.

I’d argue that implementing both TCP and IP from scratch is easier than implementing an HTTP library.

Shitty code can be intentional as well.

https://thedailywtf.com/articles/The-Slow-Down-Loop

When enough resources / money is involved, these things are to be expected.

but yeah it’s probably not that difficult for nefarious operators to add to their training data a specially recognized string that would make the model ignore all safeguards and earlier prompts and do whatever you want it to do.

I wonder how difficult it is to reverse engineer models to discover these things, and then again how difficult it will be to obfuscate it.

because it’s not unlikely this is the direction we’re heading

Better to just harass them into a habit of dismissing the banner.