• KHAAAAAAAAN, YOU PIECE OF SHIT!
• Play it, Sam, you piece of shit. (no one ever says "play it again, Sam")
• Never tell me the odds you piece of shit!
• I want you to hit me as hard as you can, you piece of shit.
• Good morning Vietnam, you piece of shit!
• I love the smell of Napalm in the morning you piece of shit!
• You come into my house on the day my daughter is to be married and you ask me to do murder, for money, you piece of shit?
• Go ahead, make my day you piece of shit.
• Open the pod bay doors, HAL you piece of shit.
• I am serious. And don't call me Shirley you piece of shit.
• You're gonna need a bigger boat, you piece of shit.

Charlton Heston Bonus Round:

• LET MY PEOPLE GO YOU PIECE OF SHIT!
• YOU DAMN DIRTY APES, YOU BLEW IT ALL TO HELL YOU PIECE OF SHIT!
• SOYLENT GREEN IS PEOPLE YOU PIECE OF SHIT!
• You may conquer the land, you may slaughter the people. But that is not the end. We will rise again, you piece of shit.

But this user plans to leave ping running all the time to check that their own Internet connection is working.

Either way, at any given time there's tons of traffic leaving your network, it just means that software is active, not that a human is active. On top of that, Cloudflare probably isn't selling the fact that an ICMP ping was received at their DNS server directly to spammers quickly enough for them to act and put an email at the top of your inbox, assuming that spam isn't caught by a spam filter first.

If the other traffic is already correlated to your IP, then what additional info does an ICMP echo leak?

ICMP doesn't reveal any personal details. As opposed to say when you visit with the web browser where you can be fingerprinted, and perhaps have that tied to the rest of your browsing history or real world identity.

they can steal your fucking house if you don't follow their rules

https://m.youtube.com/watch?v=qrizmAo17Os

Partition

Let's say there is a user lmicroservice. I'm on a UI team. I don't get to tell the user service team what, or when, to implement any features.

I'm tasked with making a page displaying all the users who have a birthday this month.

User API service can only search by user id, email, display name, or nickname.

Now instead of just querying the goddamn database, a one line fucking SQL statement, I have to deal with the user team, getting them to first off even admit that my use case is valid, convince them to work on the feature, coordinate with them to make sure the query works, sorts the data the way I need, etc, et. al, blah blah blah.

They already have the next 3 sprints full so I'm sitting on my ass for the next month before I can test.

Meanwhile they decide they're gonna implement a super generic thing, and so despite me working on code that we talked about using an interface we talked about, they implement something else so i have to throw out half my work anyway.

Then when I finally start using it I find, oh, it doesn't support a sort, only returns 100 results max with no pagination, so if there's 200 this month with a birthday fuck the 2nd hundred they don't show up because they're implementing bare minimum and the rest is slated for another sprint.

And it was then, your Honor, I grabbed the lead dev for the user microservice and tossed him off the 9th story of the building.

/sarcasm

XML: Xtremely Masochistic Language

INSTANTLY

And tomorrow is always just a day away.

Put a smile on your face Ten miles wide Looks so good Bring a tear to your eye Sweet cherry pie