Retr0id

HN has a lot of people submitting/upvoting AI-generated content, and also a lot of people who work with AI extensively and therefore know how to identify it. It's not a big surprise.

Not just that, it seems to conflate "the internet" and "social media apps"

Worth noting that something perf-optimized for RP2350 is almost certainly not going to be optimal on a modern desktop-class core (with deep pipelines and wide ILP/SIMD).

This should be illegal. And maybe it already is? What consequences will Lenovo face, if any?

This was reasonable advice 12 months ago, but at the rate kernel exploitation is going it's less of a security boundary than ever. Hypervisors aren't much better, but it helps.

Wow. That's more than the cost of the storage space you'd be downloading onto.

Maybe a bit of that, but I think I'm just more careful about what I buy in the first place.

> read enormous amounts of generated text

This is something I avoid at all costs. If it's someone else's slop I just won't read it, and if it's "my" slop I prefer to interactively ask questions about it rather than reading a wall of text.

This article made me realize I'd never consider returning a non-defective product, I wonder why that is.

https://github.com/anyblades/blades seems to be a continuation in the same spirit

YC backs slop security startups (though this is not from one of them), and they've been having trouble getting people to take their slop writeups seriously. See also https://news.ycombinator.com/item?id=50294391

Oooh fun, the rare moderator superdownvote. My comment currently has +58 karma but it's been demoted to the bottom of the thread.

A DoS like this is quite bad (in theory at least) but I think it's the first time I've seen one dressed up with a hypeslop landing page.

This works well if there are obvious hot spots that can be easily isolated, but sometimes the perf issues are more uniformly distributed throughout a codebase.

At this point if you have a python codebase where perf is an issue, the "AI-pilled" answer is to rewrite it in a faster language.

Even ignoring learning outcomes, answer sharing was a good excuse for the nerds to talk to the not-nerds.

I don't know anything about the actual legal responsibilities, but even there aren't any, a defrauded customer takes up support resources just having the conversation about it. Upset customers (regardless of how well placed that upset is) will complain about it in reviews etc.

A lot of people aren't able to distinguish "I got scammed" from "the bank took my money away".

If it's a single particle I don't think there's much to worry about?

Spotify's offline playback DRM hinges on a HMAC key that's a human-readable phrase, based on a certain lyric. I'm curious whether it's just a fun easter egg, or if there's some kind of legal basis for the choice.

See also https://theapplewiki.com/wiki/Dont_Steal_Mac_OS.kext

Well, they can only do that if they're using robust watermarking. You'd need to get two accounts on two boxes on two IPs, and compare the results.

I'm tempted to buy one of their boxes and tell claude to make no mistakes, but if they're smart they're also using watermarking so cracking the DRM alone will not be enough.

As long as they keep making the disks, they'll keep making their way onto my jellyfin instance via a series of tubes.

Selling tokens is what scales best right now.

wow I've always wanted to see pure unfiltered slop

I haven't got the PoC to land successfully on my device yet, but it does seem to be legit.

I predict that this take will age poorly.

fun fact: cpython also has memory safety bugs lurking in OOM codepaths

Sometimes CVSS 10 "oversells" the true severity of a bug but this doesn't seem to be one of those cases.