Edit: It’s “Bad”, but about what I expected with the Autobahn nearby
Are you committing to master
? I don’t see any reason why you shouldn’t commit your debugging code to your own branch. Obviously clean it up before merging
You could change the dog to Merlin the wizard, Clippy or a couple others
There will always be someone who wants to fight
It was just a pun on the sound of crickets being used to represent no answer
I get being surprised about the others being down, but what did you expect from a provider called Cricket Wireless
You just have to make it think it wasn’t you
And No Poop Challenge
Funny that you mention army bootcamp. The officer is a vet
If you run large‑scale Internet services,
That means if you’re large enough that A can pick up the slack if B shits the bed. The only impact would be that you have to use HTTP2
Newer ones aren’t that large, but why bother when you have a cellphone always with you anyway
You can get a VoIP phone that works over the Internet
If you do examine what it’s doing you will catch this as soon as an attacker exploits it, and can disable it. Also, you should maybe not run the entire production with experimental features enabled. In a stable feature this would absolutely be a CVE, but this is marked experimental because it might not work right or even crash, like here
It was on purpose on the side of the road so people could gice feedback. But the issue wasn’t a health issue (privilege escalation, etc), it just wasn’t tasty (DoS). Something you really don’t want to sell in the store, but in an alpha/beta version it’s no big deal
In a lot of cases there’s no naughty context to 69