brigade

You know those data brokers and skip tracers like Acxiom and Epsilon that merge all the government databases like property records or USPS change of address notifications with private databases like all the contact lists every random app wants you to upload?

They probably did a fuzzy merge and your number (or a number typo'd to yours) got associated with some random old lady.

That's how I got on the lists of all the scummy PACs targeting elderly voters that Adam Bonica called out recently. I only figured it out because the cash for homes cold contacts trying to lowball his house will actually respond.

STOP to a 10DLC number should block further texts from that specific number at a carrier level, regardless of whether the campaign honors its 10DLC requirements. At least, until it’s recycled to a new campaign.

There's a certain online segment that's proud of not having a "real" job and has made that core to their identity. For reasons (4chan), Touhou blew up in part of that community during the great recession. They twist their arguments about Touhou specifically (reading OP's rant, wow the goalposts sure have shifted in the last decade), but ultimately I'm convinced it just boils down to wanting to feel superior for having opted out of the entire economic system.

When I first tried using IDE AI coding assistants a bit over a year ago, they would frequently fail to read files and completely hallucinate the code I asked it to analyze or edit. And even when it did successfully read my code, it would often hallucinate the API of other frameworks.

I don’t think hallucinations are a major issue with agentic coding a year later? At least, not for me.

Legal writing does have the problem that there is no such thing as a correct argument that a goal-driven loop can target. But basic things like “does this case even exist” seem solvable with research agents, and even harder problems like “does this case support the argument being made” seem conceptually very similar to questions I now ask Claude daily.

HEVC intra is definitely not 10-20x slower than decoding VP8 intra, so something is way off with your numbers. That's on the order of comparing HM at -O0 against an actual VP8 decoder.

If you're arguing that SIP isn't a useful defense against malware, I agree there.

Sandboxing full disk reads is orthogonal to what SIP actually provides. It's entirely possible for an unsandboxed binary to slurp your private data even with SIP enabled.

Protection from the sort of malware OP was hit with is the most commonly cited dire warning against disabling SIP. I just assumed that was also the reason you were against disabling SIP in order to grant permissions to software you intentionally installed.

Sort of; SIP originally was simply meant to protect /System from root. But nowadays, it's more used for system attestation. Which in turn is used by the OS to decide how to ask for and enforce certain user permissions and sandbox profiles.

Which system integrity protection are you worried about missing? Muse being able to exfiltrate the contents of your messages db doesn’t compromise system integrity to begin with. It being able to write arguably does, but this whole conversation was about how to grant it full disk access in the future anyway.

And OP had SIP enabled, but his system still got compromised with a remote exploit.

Or the scary warnings today against disabling SIP, repeated by forum users anywhere it’s discussed.

Which happens to be the only way to disable the TCC permission dialogs OP complains about. Guess the warnings worked well enough that no one knows that anymore.

App store apps are required to run in a sandbox that denies file accesses without user permission.

Muse is not available in the macOS app store. Almost certainly because of the sandboxing requirements.

Thumbnailing happens in a background process and shouldn’t block the main thread; rather hangs are usually because fetching xattr over SMB is slow and Finder will block until it’s enumerated the metadata of every file in a folder.

Preview actually does use progressive rendering for large enough images, even from SSDs. You can tell because opening an image will be blurry for several seconds, even when the full size image could have been decoded in a quarter second or less.

You're wrong. AVIF does support spatial layering where the full-resolution image is derived from the lower-resolution layer, and cannot be decoded independently.

Yes, the format is not inherently progressive. But having the fine steps in progressive quality that JPEG-2000 and JPEG-XL have has less general usefulness than the amount of words complaining about it.

For like a decade, the "opt-in" to ACR was included in the ToS agreement needed to use any smart features. Then at least some brands made the opt-in separate, but made it look like a recommendation engine or "help us improve your experience" agreement.

LG adopted the "Maybe Later" dark pattern for opt-in to ACR, at least in some markets. Though I guess you never know for sure with A/B testing.

All 10 cores support the same extensions. It’s silly to implement an SoC any other way, and it’s been a decade since someone has last made that mistake.

Well the original article is also about RISC-V isn't a great ISA for embedded either, and how that's supremely disappointing because there's no inherent reason why the designers couldn't have learned from decades of ISA research and made it suck even a little less. OP doesn't even defend the ISA committee (unlike HN, somehow...)

As much as people complain about warts in other ISAs like x86, their design decisions made sense back when they were made (or at least, no one really knew better)

There's an order of magnitude difference in speed requirements between file format parsing and image decoding, then another order of magnitude difference to video decoding. Even rav1d reuses dav1d's assembly (most of the actual runtime) to approach its speed.

Still true for extended attributes, which Finder and Spotlight love to query.

Even backwards compatibility is optional in USB4. There are USB4 devices (SSDs at least) that will not function when connected to USB 3 ports.

Zero micro ops to be precise, that’s handled entirely at the register rename stage with no data movement.

Cortex A8 vsub reads the second source register a cycle earlier than veor, so that can add one cycle latency

Not scalar, but still sub vs xor. Though you’d use vmov immediate for zeroing anyway.

Fine, you made me look it up. M1 Air defaults to 2880x1800 on a 2560x1600 display, which is a 1.125x scaling. Nowhere near the 1.5x you claim.

Apple never supersamples by 2x. Default MacBook Air scaling was around 1.1x iirc.

OP dances around the key context that this isn’t hidpi, but rather a 3rd party hack that uses hidpi rendering to supersample their “native” 4k resolution by 2x, since the end result looks more pleasing to them than the native 4k render.

And that itself is a recent policy change from just in the last two months; as of January United's official policy [1] matched the FAA's in only requiring checked devices to be powered down

[1] https://web.archive.org/web/20260129152627/https://www.unite...

It’s really a question of whether a team believes bugs are defects that deserve to be fixed, or annoyances that get in the way of shipping features. And all too often, KPIs and promotions are tied to the features, not the bugs.

Plus, I’ve been in jobs where fixing bugs ends up being implicitly discouraged; if you fix a bug then it invites questions from above for why the bug existed, whether the fix could cause another bug, how another regression will be prevented and so on. But simply ignoring bug reports never triggered attention.

That's why I said generally - once testimony is compelled, it can no longer be used against you. And the definite exception for compelling your name is if the government already believes that you committed a crime and is trying to figure out who you are, and you cannot articulate specifically why your name could be incriminating.

5th amendment protections can include questions of identity, if the question of identity is relevant for incrimination. Like, if the government has a warrant for "Joe Smith", you're not required to testify whether that's you. It's usually a waste of time since could just prove it with the non-testimonial evidence that lead to your arrest, but the protection does exist.

First, you have the right to say nothing at all; there is no requirement to incriminate someone else to protect yourself.

Second, you can still generally invoke the 5th amendment during testimony even if you already claimed someone else did it. You aren't under oath until said testimony, so it still protects against you having to choose between committing perjury or self-incrimination, and doing so cannot be used as evidence of either.

Most of the world also doesn't have the same degree of protections against self-incrimination that the 5th amendment provides. If someone shot a person with my gun, while the police can obviously ask questions, in the US I have the right to not answer and force them to prove beyond a reasonable doubt who fired it.

It’s not a hard limit, especially if you aren’t pushing the frequency wall like Intel. AMD used to use a 2-way 64kb L1, Intel has an 8-way 64kb L1i on Gracemont, and more to the point, high-end ARM Cortex has had 4-way 64kb L1 caches since before they even supported 16kb pages.