Farmer Brown believed his injuries from the accident were serious enough to take the trucking company to court. But the company’s slick, high-priced lawyer was ready to tear his case apart.

“Mr. Brown,” the lawyer said, straightening his designer tie, “is it true that at the scene of the accident, you told the responding officer, ‘I’m fine’?”

Farmer Brown scratched his head. “Well now, I was just about to load my favorite mule, Bessie, into—”

“I don’t need a story,” the lawyer interrupted sharply. “Just answer yes or no—did you or did you not say, ‘I’m fine’?”

Brown frowned. “Well, like I was saying, I was loading up Bessie, and we were headed down the—”

“Objection, Your Honor!” the lawyer huffed. “The witness is being evasive.”

But the judge, now curious, leaned forward. “Actually, I’d like to hear what he has to say about Bessie.”

Farmer Brown smiled. “Thank ya, Judge. Now, as I was saying, I had just loaded Bessie into my trailer, and we were driving along when this big ol’ semi blew right through a stop sign and smashed into us. BOOM! My truck flipped, I flew one way, and poor Bessie went the other.”

He shook his head. “I was hurt bad—couldn’t even move—but I could hear Bessie moanin’ something awful. Next thing I know, a highway patrolman shows up. He walks over to Bessie, listens to her groanin’, shakes his head, pulls out his gun, and BANG! Puts her down right then and there.”

The courtroom gasped.

Farmer Brown continued, “Then, the patrolman walks over to me, still holding his gun, and says, ‘Your mule was in bad shape, so I had to put her down. Now… how are YOU feeling?’”

The jury erupted in laughter. The lawyer slumped in his seat, defeated. And Farmer Brown? Well, he walked out of that courtroom with a fat settlement—and a brand-new mule named Lucky.

I left my optical drive at home.

Where's the best place in a small city to buy an external Blu-ray drive?

POSIX allows an implementation of getpgid (pubs.opengroup.org/onlinepubs/…) to fail when the process calling getpgid() is not in the same session as the process it wants the pgid of.

Reasonably, Linux and FreeBSD ignore that part, and simply return the pgid, no matter who asks.

But OpenBSD sees a standards-conformant opportunity to be a giant pain in the ass, so it has to jump on it. And so, when A calls getpgid(B) and B is in a different session, it returns -1 EPERM, even when A and B have the same uid and gid, and it would be perfectly legit for A to send signals to B and its whole process group.

The behaviour is the same for getsid, of course.

As a consequence, s6-supervise on OpenBSD is unable to target the process group of its supervised process, which disables one of its mitigation strategies for misbehaving daemons that leave children behind when they die. And since OpenBSD doesn't have cgroups, that doesn't leave many mitigation possibilities.

I am curious of why POSIX allows this. It seems to go against the common Unix principle that the uid is the key to which process is allowed to communicate with which.

It might make sense to forbid setpgid from the outside, but forbidding reading the pgid feels wrong. Especially since it's defeatable: since I control the parent and child, the child can getpgrp() and communicate its pgid to the parent. But that's a lot of work for something so niche that only breaks on OpenBSD.

I am starting to believe that OpenBSD's reputation for security is mostly due to the fact that no rational person bothers to port software to it.

(Edit: typo)

Starburst isn't taffy. Hersheys isn't chocolate. Twizzlers aren't licorice.

America is obsessed with fraud.

@autistics

So, tbh, I would not change anything about having #Autism and #ADHD. Sure, if I had been diagnosed properly and had more support, some aspects of my life would have been better. But I have no regrets on having a semi-eidetic memory, being able to recognize patterns, thinking outside the box, etc. What I could have used less of? Being bullied, not knowing there were others like me out there (and the subsequent isolation), over-masking and paying the price, having meltdowns from not understanding sensory overstimulation, etc. But it's never too late to delve into self-understanding and awareness, and, most importantly, building community with like-others!

#ActuallyAutistic #AuDHD #IAmWhoIAm

So Elon's new Wikipedia clone, grokipedia.com, is actually 10x as accessible as Wikipedia itself.

This is despite it being a React / Next.js ap, while Wikipedia is a classic, server-rendered site.

The Walton family (who own Walmart) are worth over $400 billion, yet many of their employees are on SNAP.

Bezos is worth over $400 billion, many Amazon employees require SNAP.

The people who need help are not the problem.

It’s corporate greed. It’s an unwillingness to pay a living wage.

#snap #fascism #uspol

A thief trashed Calgary's The Camera Store, making off with $71,500 in cameras and lenses

dpreview.com/news/6757730480/a…

Crime. In Calgary.

С обновлением интерфейса Youtube на 24" 1080 мониторе я могу видеть на странице только 6 видео или 3 видео и 5 шортсов. Хотя, зачем вообще показывать шортсы в рекомендациях на десктопе?

Вот бы еще в самом гугле на одном экране было видно только первые 2 результата, одним из которых был бы "обзор от ИИ", вот тогда это было бы UI consistency

dnes asi prvý krát som použil "vieme odkiaľ vietor veje" a ani si nie si istý neviem odkiaľ

edit: teda viem presne len neviem odkiaľ to mám

Random tip for comparing the performance of Rust and C programs that use stdout:

Rust stdout is line-buffered, even when redirecting to a file.

Glibc (and most C libraries I know of) are smarter than this, and will switch to a more aggressive buffering scheme if they aren't writing to a terminal.

Running the program _under hyperfine_ is enough to trigger this behavior, because hyperfine takes over the stdout stream. Glibc senses that this is not a terminal and turns on a 4096-byte buffer; Rust continues making one syscall per line.

So if a Rust program that prints stuff seems to lose a performance advantage over a C counterpart when run under hyperfine, it's worth stracing to check.

(There's continuing talk of fixing this default in Rust, but it's not fixed yet.)

Sensitive content Reveal/hide

Bluefin knows what's up. It's been a joy to collaborate with and fix issues for everyone!

docs.projectbluefin.io/blog/20…

So one thing I notice about #blind Internet culture: even back on Twitter, and now here in the #fediverse, blind people tend towards having discussions in giant threads, sometimes with as many as 10-12 people in them, that can often stretch on for days. I rarely (if ever) see sighted culture do this. I wonder why? It's not a criticism, it's just interesting to me. Maybe because Discord and other chat apps were historically less #accessible, so blind culture tends to use the fediverse more as a discussion platform? Or maybe it's something UI related that makes it easier for blind folks to track giant threads of doom? The few times I've been involved in this style of discussion with sighted folks, they've become confused and begged for everyone to move to Discord or Slack or somewhere. On the other hand, I rarely see blind people do a single, lengthy post broken up and threaded the way sighted people do, with (1/N) at the end. We tend to just move to instances with longer character limits, or put our long form thoughts on a webpage or something.

Edit to add: I'm pleased to say that this post has now become a perfect example of the thing I was talking about; my last post in the thread included the phrase "transsexual furry puppygirls". It makes me happy that people unfamiliar with what I'm talking about need do nothing more than look at the thread on this post.