That is indeed the current workaround, but IMO still unwieldy and inefficient. I find that the hotkeys alone allow you to fly around the comments and scan them way faster.
Appreciate the feedback! Agreed that on HN, even collapsing at L2 would be a significant improvement.
I'll keep brainstorming with the UX for the next version. I appreciate your perspective on how all the data disclosed on first load might be disorienting with unclear relationships. I'll play with either some sort of animation cue, colored or bordered visual indicators, or a default null selection as you've suggested.
I've been using bkt (https://github.com/dimo414/bkt) for subprocess caching. It has some nice features, like providing a ttl for cache expiration. In-pipeline memoization looks nice, I'm not sure it supports that
I was not aware of bkt. Thanks for the link. It seems very similar to memo, and has more features:
- Explicit TTL
- Ability to include working directory et al. as context for the cache key.
There do appear to be downsides (from my PoV) as well:
- It's a rust program, so it needs to be compiled (memo is a bash/zsh script and runs as-is).
- There's no mention of transparent compression, either in the README or through simple source code search. I did find https://github.com/dimo414/bkt/issues/62 which mentions swappable backends. The fact that it uses some type of database instead of just the filesystem is not a positive for me, I prefer the state to be easy to introspect with common tools. I will often memo commands that output gigabytes of data, which is usually highly compressible. Transparent compression fixes that up. One could argue this could be avoided with a filesystem-level feature, like ZFS transparent compression. But I don't know how to detect that in a cross-FS fashion.
I will never use Gemini for this reason. The enshittification of Search is so treacherously disgraceful and user-hostile, that I have no faith that the same fate won't occur with Gemini as well.
Absolutely not. People are not asking for dark patterns to engineer their behavior to maximize retention. This is like locking a kid in a room full of candy, and then blaming them for gorging themselves.
Well, I don't use a google account and use invidious and piped as proxies, so that's a no go for me.
It shouldn't be this hard to find something this specific on a video host with the worlds most powerful search engine bedded into it. It's gotten to the point where I archive and store links for anything I might want to find later, but I found this before I was of that mindset and I've wanted to share it with people. When search rot is worse than link rot there's a big problem.
