HNHacker News
TopNewBestAskShowJobs

joshka

2,489 karma · joined June 6, 2011

[ my public key: https://keybase.io/joshka; my proof: https://keybase.io/joshka/sigs/ElI6j13SI-_2rTrkLnoKyV-uDepH4JvAQAzp2OWV_W0 ]
submissionscomments
joshka··on Tim Curry has died
Dammit
joshka··on Migrating a Synology NAS to a UniFi UNAS Pro 8 with Robocopy, SMB Multichannel
I took a look into it mostly to satisfy my curiosity. The AES-NI chip on the J4125 in the Synology DS1520 hits 5Gbit/s transfer when using 4 cores (AES-256-GCM). So technically this it would be possible to saturate its 4 ethernet ports (or at least the encryption wouldn't be the bottleneck). You could back this down to 128 or drop the encryption altogether on an network that you own like this reasonably.

My guess is the actual bottleneck would be directory traversal and metadata stuff - i.e. trying to keep the pipe full, not saturation effects.

Yeah I know on src/dest. I've done this sort of approach countless times in various technologies in the past 40 or so years, but that always puts the mechanism for checking things in onus of the human rather than having that one command that does it all right.

Anyway, not a slight on rsync in the slightest - it doesn't have this probably because no-one realistically actually needs it most of the time.

joshka··on Stop Making TUIs
It's mostly something I'm thinking a bunch about recently. Nothing written up yet aside from the above. I'd go read Mitchell Hashimoto's Lobsters interview fora different take and see how that resonates with you as well as the recent blog posts about TUIs and accessibility.
joshka··on Stop Making TUIs
yeah, something along those lines - but more robustly defined.
joshka··on Stop Making TUIs
one step deeper - it's a failure of WIMP[1]. Imagine if instead of having a border around the parts of an app that make it an app and instead we applied the unix way but to the gui? What if we had lightweight widgets that had a lifetime of their own and could be nested and combined.

[1]: https://en.wikipedia.org/wiki/WIMP_(computing)

joshka··on Stop Making TUIs
I have built a pretty full version of that idea in rust (codex tui2). There's a while tonne of downsides that make it basically impossible to really get to 100% good on this.

> Under the hood it's still a terminal app, but from the UI author's perspective you're not fighting terminfo, CSI sequences, or varying terminal support. You get proper cursor tracking, scroll regions, and editable text areas out of the box.

All that is not true. Take scrolling for example. Each terminal emulator implements this subtly differently (mouse/trackpad/speed etc.), scrolling will never feel native unless you push the control of it into the terminal emulator.

There's more than that, each and every point on this becomes something that you have a gap between native and the terminal emulator that you're building to run in the terminal.

See https://github.com/openai/codex/issues/8344 and https://github.com/openai/codex/pull/9640

Claude code and gemini have both had various versions of the same idea at times. I'm unsure where they ended up.

joshka··on Stop Making TUIs
The problem succinctly is when the terminal emulator only sees cell values and instructions it can't do anything more with things. Two really good examples are implementing accessibility well, and scrolling / changing things above the terminal pane without rewriting the whole history.
joshka··on Stop Making TUIs
> as you're drawing interfaces with punctuation characters

Yeah, in my hypothetical new protocol, the character cell is still there, but it's not the element that drives the main abstraction. The layer above that being more semantic is where the smarts is. So borders, interactive areas, mouse hit mapping to elements, etc. ends up being built into the protocol rather than being a cell level thing. Cells having proper borders being similar to how they allow for underline, being able to have both images and text, ...

I think it's important to do something about the VT100 +kitchen sink stack and to have that as something that still works with that in areas of the new terminal proto. I've got a slopcoded rust library in the works that's about fully mapping the full list of terminal protocols and related things in one coherent library (VT100, ECMA48, DEC modes, iTerm extensions, Kitty, ...). From there I think making that fairly isomorphic with the terminal emulator layer (I have a RIIR ghostty slopfactor there too that fits).

I think ghostty / superlogical looks at this from the perspective of doing pty things and then transfering that calculated state across the wire while doing fun stuff with windows, panes etc. with replay and that sort of thing. I think this is valuable too.

I suspect that there's possibly a way to do a bit of a hybrid on this - normal pty things with the extra sidecar of more semantic structured, but it'll make things more complex for app builders on that side of things.

(On another comment I saw you mentioned "couldn't help noticing how much of the tedious work of putting a TUI together". I think probably textual in python is probably the best of the low ceremony libraries for making TUIs if you haven't checked that out yet. I think someday there will be a good Rust library that has that level of put together-ness. I have some ideas on this for ratatui and have seen a bunch of things that are directionally right for this, but nothing that gets close yet).

joshka··on Felony charges for citizen deleting phone data at US Border
Could he? To answer properly without possibly committing further possible crimes, he needed a lawyer familiar with whether that's allowable, something he was explicitly denied after asking multiple times. See https://www.courtlistener.com/docket/71998357/21/united-stat...
joshka··on Stop Making TUIs
The problem is that cells don't compose well as an accessibility thing. You need a DOM equivalent in order to realistically do a bunch of things that are meaningful at an app level. TUI libraries are all basically doing that DOM thing already - just custom and treating the final shippable product as the cells, positions and imperative instructions for how to tell a terminal what to do. I' just saying that a more declarative interaction is very likely the sort of simple and boring that helps portability (long term) and speed.
joshka··on Stop Making TUIs
If you're redesigning a protocol layer, then I'd say you still want to target fixed size cells as the unit of rendering. It's just not the central abstraction like it is in the current terminal approach. Because you're one step above here, you have th ability to do better border handling. There's a lot a things you miss trying to force borders through a character set thing (e.g. missing characters depending on your font, missing ability to position borders naturally, interaction with background color, adjustment of size and space of rendered text due to interaction with unicode characters and fixed positioning) ...

But in general, going with a fresh new protocol allows you to do a bunch of things semantically that are currently done as pure graphical stuff and that's useful.

joshka··on Felony charges for citizen deleting phone data at US Border
The existence of a key only being somewhere other than your current location during a border search enables you to legally say "I cannot unlock this device" and move on with your day.
joshka··on Felony charges for citizen deleting phone data at US Border
See https://www.cbp.gov/document/directives/cbp-directive-no-334...

> The border search will include an examination of only the information that is resident upon the device and accessible through the device's operating system or through other software, tools, or applications. Officers may not intentionally use the device to access information that is solely stored remotely. To avoid retrieving or accessing information stored remotely and not otherwise present on the device, officers will either request that the traveler disable connectivity to any network ( e.g., by placing the device in airplane mode and disabling Bluetooth and Wi-Fi connections) or where warranted by national security, law enforcement, officer safety, or other operational considerations, officers will themselves disable network connectivity. Officers should also take care to ensure, throughout the course of a border search, that they do not take actions that would make any changes to the contents of the device.

and

> Passcodes or other means of access obtained during a border inspection will only be utilized to facilitate the inspection of devices and information subject to border search. Passcodes or other means of access may not be utilized to access information that is only stored remotely. Passcodes or other means of access should only be recorded by the officer in a temporary format and should not be uploaded into CBP systems. Passcodes or other means of access recorded by the officer will be deleted or destroyed when no longer needed to facilitate the search of a given device.

joshka··on Felony charges for citizen deleting phone data at US Border
I'm talking specifically about the graphene OS ability for that approach, not the ability to add an external key to some generalized encryption. The threat model here is that the traveler was required to provide a passcode unlocking a key they had with them on their phone. If that threat is not there, then this bypasses problem.
joshka··on Felony charges for citizen deleting phone data at US Border
Not really - the government have stated that he's in the US. It's the first sentence of the indictment. [1]

> On or about January 24, 2025, in the Northern District of Georgia...

[1]: https://storage.courtlistener.com/recap/gov.uscourts.gand.35...

But in general, the thing to note here is that the 4th amendment is always applicable and in force. It's how it's interpreted that changes depending on the circumstance.

joshka··on Stop Making TUIs
I really liked this article (despite disagreeing with its conclusion and agreeing with many of the concerns about failures of TUIs). It gave a feeling of "here's a bunch of cool stuff I've done" to help back the claim, which is far more personal than a lot of blog posts tend to be.
joshka··on Stop Making TUIs
As a ratatui library maintainer, NO - please don't stop making TUIs ;)

As a developer outside of that, I love the scratch the itch apps stuff mentioned in here. I have a vibe coded SwiftUI chess repertoire builder app that fits in that same sort of space that I'm currently working on, where I'd probably not have chosen to explore the idea if not for coding agents.

I agree with the article that the terminal is an odd shape which you're fighting against historical specs, etc. The key observation I have though is that the mismatch of terminal apps and libraries to deal with this are all fundamentally built around character cells and cursor movement plus various CSI/OSC/ASC/DEC/xterm/... protocols which are complex and have varying support and interact in weird ways.

To get a good terminal UX, I think the answer to this is probably to throw all that compatibility mess away and redesign a modern terminal protocol that bakes in accessibility, regions, scrolling, selection, proper keyboard, etc.

I know Mitchell Hashimoto has a bit of a different perspective on this, which seems like it's to define some more protocol stuff and continue to build up on things. I think that probably gets to 95% pretty well. But a 100% good is a full replacement.

joshka··on Felony charges for citizen deleting phone data at US Border
So the part of this that feels like it triggers the government issue here is that in effect you have a locally stored encryption key which gates access to the device, which was removed from the device due to duress password.

What if we flipped this to instead be something that's explicitly not on the device?

The border search stuff only applies to information on the device. It cannot compel you to provide access to e.g. emails stored in a cloud provider.

If instead of making the process of stopping searches like this be a destructive one, we instead pre-purge the key but store it offsite with the ability to get it from an online location, then this feels like it's probably reasonable here. In the sense that the 4th amendment explicitly allows "The right of the people to be secure in their persons, houses, papers, and effects, ..."

There's probably some sort of technical problem I'm missing here (or maybe this functionality is available already).

joshka··on Felony charges for citizen deleting phone data at US Border
I'm just guessing here, but the most problematic word on the 4th amendment to attack from the government's perspective is "unreasonable". It's easy to see how a phone border search could be construed as reasonable, and (without digging into this deeply) I suspect that's where most of the push back on this will be.

I suspect the 5th amendment is probably more valuable to the defense here as the password is effectively testimonial and the give us your password or we'll ... is compelled speech.

Either way, it's gonna be many 10s of thousands of dollars in lawyers fees to fight this. Which sucks.

joshka··on Felony charges for citizen deleting phone data at US Border
It's a fairly shallow point that ignores how laws work.

The premise that the law doesn't apply because you're not in the country is false. The constitution applies generally everywhere to all Americans, it's just that what's regarded as reasonable differs during a border search. IANAL, so just my lay opinion on this. Just to validate this, it's only because the constitution exists that the border authorities have any legal basis in doing inspections.

joshka··on Rewriting in Rust
This feels like a really good blog post to write - something I'd really want to read - but the generated AI prose distracts, and makes me lose trust and not want to read this. I'm very AI-pilled, so this is not a criticism of AI as a whole, just this piece.
joshka··on Pi coding agent: config folder is out of place on Linux
This feels like the sort of decision that well meaning folks that manage utilities can disagree on. It's frustrating every time it happens because it's usually a fairly reasonable perspective to ask for XDG / operating system specific support for folders to be respected. (e.g. macOS's ~/Library stuff).

Posting a github issue like this though feels like an easy brigading target, so please don't do that.

joshka··on Ask HN: How do you keep up with HN these days?
https://hckrnews.com/ most days, has a good line which tracks what you saw last. Sometimes filter by top 10/20 when I've been more busy and to catch things I may have glossed over as being more popular.
joshka··on Pareto Front
The current thing that comes up regularly is choosing an LLM setup.
joshka··on Pareto Front
lol same :D
joshka··on Boris Cherny on Trying to Get Claude Code to Rewrite the Claude App
This, but I'd say that there is an engineering perspective that you can apply. What the developer world is trying to discover here is how to encode taste concretely - often this is things like really mechanical design system things (space/padding/margins/relative sizes/color contrast/...).

The hard point is doing that well deterministically in a way that is token efficient and which can be iterated on. I suspect it's difficult to encode that into an AI model of what's good taste.

joshka··on Boris Cherny on Trying to Get Claude Code to Rewrite the Claude App
I've done VHS (terminal recording) rewrite in rust built on libghostty called Betamax [1], and then threw it at creating a TUI for jujutsu. This worked pretty well, but is admittedly a much simpler task than a web ui. The harness was able to build out a feature, confirm it worked, find bugs in what it expected vs saw and fix them with evidence. Web is many more pixels and more nuanced things that have to do with how various elements relate.

I speculate that maybe the OpenAI models have the edge here over Claude's (while still being terrible at web UIs), as the training necessary to handle computer use stuff is heavily image processing based. I wouldn't bet on either being bad for much longer though.

[1]: https://www.joshka.net/betamax/

joshka··on How to Spot AI Writing
Take a look also at https://tropes.fyi/

I've put in some effort to try to help agentic tools avoid these problems: https://www.joshka.net/practice/rules/documentation/docs-avo....

joshka··on 13 Models and 4 Agents on SWE Tasks: Go, Java, Python, Rust, TS
Some agents have specific tools that the models have been trained to use. E.g. diff formats for editing that aren't the same as the standard unified diff format. Access to specific thread / subagent / etc. tooling or the base prompt can perhaps also impact how the tasks are completed.
joshka··on Anatomy of a Frontier Lab Agent Intrusion: A Timeline of the July 2026 Incident
Yeah, what bothers me is that the prompt already said using a different vulnerability didn’t count, and the model did it anyway. We’re starting to assume clear instructions act as real constraints, but here the measurable goal seems to have won out and the rest became flexible. That gets pretty worrying once the agent has enough capability and access to find its own shortcuts.
← PreviousPage 3 of 34Next →