☢️ Giles 🌎

So you’d like to pay for the privilege of having a mailbox every month? Got it. Besides, it’s required to have mail service since, for example, IRS letters come certified mail needing a signature and court documents must arrive. Mailmen also sign off on legal documents certifying someone lives at that address all the time

@YssupN15919 @crassrocker5 @Ultima_Fool @ADNPorte76 @ClownWorld Because it would be cheaper for everyone. Profit is not bad. It just means you’re providing a valuable service in a free market.

Homeowner asks the mailman not to walk on her grass Mailman gets annoyed by her response, throws the mail on the ground, says something as he walks away Internet is now split. Some siding with the homeowner, others with the mailman Who do you think is wrong here? Homeowner or mailman?

@sphigel1 @ADNPorte76 @ClownWorld With the exception of emergency relief during the pandemic the post office pays for itself with postage, junk mail, and package deliveries. It’s literally a free service for the average person to receive mail

@Ultima_Fool @ADNPorte76 @ClownWorld Yet another reason mail delivery should be privatized. Only the government can get away with this BS. Shitty service at high cost, that’s the government way!

@richisrich214 @ADNPorte76 @ClownWorld He wouldn’t get fired. He’d get a PDI and maybe a Letter of Warning if he hasn’t gotten in trouble lately.

@Ultima_Fool @ADNPorte76 @ClownWorld So is throwing someones mail to the ground for being asked not to walk on a lawn a written rule. He should be fired

@JackDangerLIVE Yeah and they turned around and did the exact opposite because they’re evil and think we’re stupid

Dad, what were Democrats like in the 1990s? Volume up 🎧

@falloutc1oud @ADNPorte76 @ClownWorld I walked and timed routes for USPS

@Ultima_Fool @ADNPorte76 @ClownWorld You can verify through the USPS website which is what I did

@falloutc1oud @ADNPorte76 @ClownWorld No they absolutely need to fill out a written request because it needs to be factored into the route’s length the next time they’re walked. There needs to be a paper trail or they get penalized for working inefficiently and the time deducted

@Ultima_Fool @ADNPorte76 @ClownWorld Half true. They are allowed to cross lawns. However, the homeowner can make a complaint without filing paperwork. In this scenario, the homeowner made the request. The carrier then littered in response.

@ADNPorte76 @ClownWorld It literally is a written rule. Letter Carriers are required to cross lawns unless the homeowner fills out paperwork at the post office and the postmaster approves it as an exception. Crossing lawns is built into the route’s length

@ClownWorld Mailmen get a pass to walk on lawns. Everyone knows that. Unwritten rule of society.

@realKalos Thanks man. I sent this to my girl and I got laid

Hey. Hey, you. Yes, you, the girl reading this. This is you. You are this bee. You do this. You are exactly like her. A cute little creature playing with rose petals. When I see this bee, I see you. You and color pink. Always together. And cuteness. You, pink, cute. I love you.

@arqotx @Mappy6984 Doesn’t matter the point is to discourage the behavior

@Mappy6984 The best part? That shit's probably going straight in the dumpster anyway because "hygiene."

I want this dudes job

The American Hemisphere

I CAN'T BREATHE 🤣🤣🤣

@AtnsXBT This might be the worst gameplay I have ever seen

clefable randomly explodes with metronome lmao

‼️🚨 BREAKING: An AI found a Linux kernel zero-day that roots every distribution since 2017. The exploit fits in 732 bytes of Python. Patch your kernel ASAP. The vulnerability is CVE-2026-31431, nicknamed "Copy Fail," disclosed today by Theori. It has been sitting quietly in the Linux kernel for nine years. Most Linux privilege-escalation bugs are picky. They need a precise timing window (a "race"), or specific kernel addresses leaked from somewhere, or careful tuning per distribution. Copy Fail needs none of that. It is a straight-line logic mistake that works on the first try, every time, on every mainstream Linux box. The attacker just needs a normal user account on the machine. From there, the script asks the kernel to do some encryption work, abuses how that work is wired up, and ends up writing 4 bytes into a memory area called the "page cache" (Linux's high-speed copy of files in RAM). Those 4 bytes can be aimed at any program the system trusts, like /usr/bin/su, the shortcut to becoming root. Result: the next time anyone runs that program, it lets the attacker in as root. What should worry most: the corruption never touches the file on disk. It only exists in Linux's in-memory copy of that file. If you imaged the hard drive afterwards, the on-disk file would match the official package hash exactly. Reboot the machine, or just put it under memory pressure (any normal system load that needs the RAM), and the cached copy reloads fresh from disk. Containers do not help either. The page cache is shared across the whole host, so a process inside a container can use this bug to compromise the underlying server and reach into other tenants. The original sin was a 2017 "in-place optimization" in a kernel crypto module called algif_aead. It was meant to make encryption slightly faster. The change broke a critical safety assumption, and nobody noticed for nine years. That bug then rode every kernel update from 2017 to today. This vulnerability affects the following: 🔴 Shared servers (dev boxes, jump hosts, build servers): any user becomes root 🔴 Kubernetes and container clusters: one compromised pod escapes to the host 🔴 CI runners (GitHub Actions, GitLab, Jenkins): a malicious pull request becomes root on the runner 🔴 Cloud platforms running user code (notebooks, agent sandboxes, serverless functions): a tenant becomes host root Timeline: 🔴 March 23, 2026: reported to the Linux kernel security team 🔴 April 1: patch committed to mainline (commit a664bf3d603d) 🔴 April 22: CVE assigned 🔴 April 29: public disclosure Mitigation: update your kernel to a build that includes mainline commit a664bf3d603d. If you cannot patch immediately, turn off the vulnerable module: echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf rmmod algif_aead 2>/dev/null || true For environments that run untrusted code (containers, sandboxes, CI runners), block access to the kernel's AF_ALG crypto interface entirely, even after patching. Almost nothing legitimate needs it, and blocking it shuts the door on this whole class of bug...

Timeline altered realityrevolt.com

I was skeptical but I can’t unsee it now

@AnimexTwts They made him Mexican

Name a bigger downgrade:

🚨 JUST NOW: Karoline Leavitt calls on everyone to watch tonight because Donald Trump will bring the heat and there will be “shots fired” LET’S FREAKING GO 🔥

What do you think the Google chrome thing is supposed to be

I AM STRUGGLING TO BREATHE HEEELP