Retr0id

It's easy to "escape" from timeout by daemonizing etc.

A trivial bypass I can imagine is spawning a new process via `ssh localhost foo` - the new process forks from sshd, not the client. This is simple enough that an LLM could come up with it all on its own, if it feels that you're getting in its way.

It's a broad class of bypasses that can apply to just about any "long running daemon can be instructed to spawn a new child" situation.

look up has the same number of syllables but it does not have quite the same semantic density, you can look something up without using a web search engine.

Heads up, your youtube link has a tracking ID in it that is bound to the account/device you shared the link from.

Attestation does not solve this.

> GrapheneOS does everything and more for key attestation

Right, that's the problem, in my opinion. I'm not referring to the apps that require Google's keys only, I'm referring to the ones that allow GrapheneOS keys too. If you use one of these apps, you can use vanilla GrapheneOS builds, but you cannot run your own self-signed builds.

You are gaining freedom relative to running Google's OS, but you are still not free to further modify the software running on your own device.

Apps that require "integrity" should monitor their own integrity only, they should not attempt to infer the integrity of their environment.

Maybe I'm just the wrong demographic, but I clicked around for a bit and couldn't really tell what I was looking at. In particular I couldn't figure out how to "Choose a preset or click Random".

Edit: I found the presets in the end, I was not expecting them to be above the other controls, when it's at step 3 in the "getting started" list.

It is possible to build a device where the modem is not at all trusted, but I don't know if anyone is actually doing that.

I will never feel bad about blocking ads on youtube, because they have an effective monopoly on distribution of certain content. But when it comes to music, why not just use something else?

You are not quite the owner on GrapheneOS either, because of Android Key Attestation (which has functionality analogous to desktop TPMs). If you re-unlock your bootloader (say, to run a custom build of GrapheneOS), attestation will snitch on you and the subset of apps that use key attestation to require a locked bootloader and/or enforce an AVB key allowlist will not work properly. This is a very small subset of apps currently, but I don't see it getting any smaller.

It used to be my "it just works" distro for systems I didn't want to spend time configuring, but they managed to make me feel like a second-class citizen as a not-enterprise-customer (not really anything specific, just a lot of small cuts).

I appreciate that they're running a business, but the Fedora/RHEL split feels much cleaner, and Fedora is my current go-to in instances where I used to reach for Ubuntu. (Or I use Debian, for headless/server setups)

I'm sincerely curious, when was the last time you tried agentic coding?

I'm very grateful I have public pre-LLM projects I can point at (including a 6502 emulator!), and I have absolutely no idea how I'd go about bootstrapping the same kind of reputation starting from scratch.

It'd take a few extra sentences to get the details, but I'm confident enough that it would work that I'd rather save my tokens for something more personally interesting.

They opened their AI agent and typed "make me a 16-bit computer built from NAND gates" and hit enter.

Yup. I got excited for a bit, until I loaded the page and saw it was slop. I still would be impressed if someone actually took the time to learn about and implement it for themselves.

So now that the "trial" has failed we're going to stop doing face scanning, right? ...right???

It's a federated network, so even if everyone has symmetrical 1Gbps links you cant throw 1Gbps at all of them at once.

Are you an LLM?

You're arguing with the same OP that an LLM piloted into claiming SHA-256 was on the cusp of being broken https://news.ycombinator.com/item?id=47557755, https://news.ycombinator.com/item?id=47546028

Line rate of sender != line rate of receiver (I am also not GP).

Because throwing UDP packets requires a bandwidth advantage (aside from reflection attacks), whereas application-layer attacks can impose an outsized cost on the victim.

An honest gap

Hm. The name collides with Nura, an audio company with a product called Nuraphone. I suppose any pronounceable 4-letter word has collisions.

slop

The main problem with macros (and similar language features) is that they turn every codebase into its own DSL. When done tastefully it makes the code more readable, but there's still an overhead for newcomers to the codebase - they need to learn your DSL before they can be productive.

LLMs may make this overhead less visible to you, but surely it's still there? I'd rather more of my tokens went towards solving the actual task at hand, vs figuring out a custom syntax (and re-learning it on every fresh context window).

The sandboxing was incompetent, but the broader problem is that imperfect sandboxing is an inevitability. Doing useful things with agents requires hooking them up to the outside world, in one way or another.

Ditto. I fear Opus 5 gave me a false sense of security of how easily I could spot it.

If someone makes a cheap copy of my unreleased game and it's bad, that's also bad for me, I think.

> Good devlogs don’t have that level of detail, to let people easily recreate games

The whole problem with LLMs is that you don't need the detail.