evertedsphere

wow lmao

> Do Not Track. Some web browsers may transmit a “do-not-track” signal. Because there currently is no industry standard concerning how to treat such signals, the Services currently do not take action in response to do not track signals. We respond to legally recognized browser-based opt out signals such as the Global Privacy Control signal for California residents.

https://www.washingtonpost.com/privacy-policy/

As a general rule when it comes to this pattern of replying to "this is AI generated" with that link: the people that write these posts often read HN and attach a certain amount of importance to the opinions presented here, and it's important that people express their opinions about trends in how the majority of technical writing submitted to this website is either generated or presented, before they become well and truly entrenched as being problems "too common to be interesting".

There's a difference between criticisms of the content or the reader's ability to view it and complaints about "tangential annoyances" surrounding it.

emoji at the end of a statement are not the same thing as emoji adorning or replacing every heading

claude is nothing if not sensitive to cultural differences

Perhaps it doesn't even matter anymore, but I'm not yet past the point where it's disheartening every time I click on a link and it's clear that it came out of an LLM. Hopefully this doesn't extend to the actual report.

This reminds me a lot of…something Dynamicland.

> Always wondered why do they need to blink at the same time.

presumably this makes it more striking, and thus easier to notice and avoid

Our thoughts and prayers are with everyone affected by this unfortunate corporate-involved job loss incident at this time.

Formatting and headers aside, there are lots of local rhetorical flourishes and patterns that are fairly distinctive and appear at a far higher rate in AI writing than in most writing that isn't low-quality listicle copy artificially trying to hold your attention long enough that you'll accidentally click on one of the three auto-playing videos when you move your pointer to dismiss the newsletter pop-up.

Here's something you know. It's actually neither adjective 1 nor adjective 2—in fact, completely mundane realization! Let that sink in—restatement of realization. Restatement. Of. Realization. The Key Advantages: five-element bulleted list with pithy bolded headings followed by exactly zero new information. Newline. As a surprise, mild, ultimately pointless counterpoint designed to artificially strengthen the argument! But here's the paradox—okay, I can't do this anymore. You get the picture.

    Inside JPEG XL’s lossy encoder, all image data becomes floating-point numbers between 0.0 and 1.0. Not integers. Not 8-bit values from 0-255. Just fractions of full intensity.

Everything after the first "Not" is superfluous and fairly distinctively so.

    No switching between 8-bit mode and 10-bit mode.
    No worrying whether  quantization tables are optimized for the right bit precision.
    No cascading encoding decisions based on integer sample depth.
    The codec doesn’t care about your display’s technical specs. It just needs to know: "what brightness level does white represent?" Everything scales from there.

Same general pattern.

    JPEG XL not worrying about bit depth isn’t an oversight *or* simplification. It’s liberation from decades of accumulated cruft where we confused digital precision with perceptual quality.

It's hard to describe the pattern here in words, but the whole thing is sort of a single stimulus for me. At the very least, notice again the repetition of the thing being argued against, giving it different names and attributes for no good semantic reason, followed by another pithy restatement of the thesis.

    By ignoring bit depth, JPEG XL’s float-based encoding embraces a profound truth: pixels aren’t just numbers; they’re perceptions.

This kind of upbeat, pithy, quotable punchline really is something frontier LLMs love to generate, as is the particular form of the statement. You can also see the latter in forms like "The conflict is no longer political—it's existential."

    Why This Matters

I know I said I wouldn't comment on little tics and formatting and other such smoking guns, but if I never have to see this godforsaken sequence of characters again…

the article could be better if it weren't entirely "ai generated"

more precisely, uniq produces output in the same order as the input to it, just collapsing runs / run-length encoding it

I know we haven't seen a human-written README or technical post on a company blog in maybe the last year on this site, but posts like this being at #1 are a reminder that we can still go lower.

> choice of ONE Linux distro

fwiw the asahi kernel and patches are usable from other distros just fine; i've done it on nixos in the past and the linked blog post shows some stuff running on gentoo

how's the battery life / what's your usual workload

famously knuth was trying to (and pretty much did) solve digital typesetting not create a nice piece of hci so this is all as it should be or at least as might be expected

if only it were 10%

even the things you mention in your post paint a picture of a difference that for a lot of usage patterns is much more significant than just the last 10%

COPY is often a usable alternative.

> Expreg (teeesitter expand region)

reminds me of combobulate (which i haven't tried but think looks cool) but sounds much more light/limited

oh, totally

what i intended to point out was that regrettably few people actually pay any attention to the nozze di cana despite it being both more accessible physically and worthy of interest

one tiny famous painting from a cop-enforced distance of god knows how much while an enormous painting full of stuff stands right opposite it

sometimes you just happen to be a mathematical object

In the past I've considered forking Chromium so every asset that it downloads (images, scripts, etc) is saved somewhere to produce a sort of "passive scraper".

This article made me consider creating a new CDP domain as a possible option, but tbf I haven't thought about this problem in ages so maybe there's something less stupid that I could do.

i tried niri for a few months earlier this year

ultimately it turned out that after years of i3/sway scrollable tiling doesn't feel natural at all (and neither do dynamic workspaces, but that's less significant). when i resurrected my desktop a couple of months into the experiment i found it also lagged quite badly on my desktop with an nvidia card (a 3090, tried both drivers) and i couldn't be bothered to figure that one out so that was the final straw and i went back to sway

i was quite impressed with the level of thought that went into the ux and the amount of polish in everything though. it already feels like a serious, well-made piece of software, and it's not even that old yet

a wrapper script?

also seen in

https://lucumr.pocoo.org/2025/8/18/code-mcps/

> Web users will be charged £2.99 a month and mobile phone users £3.99 a month to scroll through Facebook and Instagram without targeted ads.

I wonder how much information this provides about the relative value of mobile users vs web users. It's complicated by the fact that part of the pricing strategy here is likely not maximizing revenue as much as it is…making it just too expensive for many people to want to pay, thus shaping public opinion in the right direction.

> If the accounts are linked, users only need to pay one monthly fee.

Is this because they manage to get some value from that edge existing in the graph even if they can't turn that into ad revenue?

Was this coordinated with Google's statement?

https://news.ycombinator.com/item?id=45381013

yes, hence the "first" (before i saw the note)

this read to me like brutalità (which would be "brutality" in italian but i don't know if it is actually a word in use) first

This is also true on Apple's app stores, to be fair. I didn't know this until I got a MacBook Pro recently and my assumption that Apple's controls would be tighter than Google's was proven quite wrong when I opened the Mac App Store for the first rime.