Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aktau
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
aktau
6mo ago
“What do you get if you multiply six by nine?” (One) source: https://www.reddit.com/r/Fedora/comments/1mjudsm/comment/n7d...
32.
▲
by
aktau
6mo ago
Why does one need the second (old-ish) Fritz!Box? Doesn't the first one already have DECT? Also, does this not require a landline number?
33.
▲
by
aktau
6mo ago
> Agree on mullvad, buy giftcard on amazon. I've heard this before. Is this just to add another hop in the chain to make it harder for someone to track the user down? Apart from someone needing to order Amazon to pony up the details
34.
▲
by
aktau
7mo ago
Any LLM-based code review tooling I've tried has been lackluster (most comments not too helpful). Prose review is usually better. > So we run dozens of parallel CLI agents that can review the code in excruciating detail. This has co
35.
▲
by
aktau
7mo ago
For Go, there is https://pkg.go.dev/gvisor.dev/gvisor/tools/checklocks . There are some missing things from C++ Thread Safety annotations, but those could be added.
36.
▲
by
aktau
7mo ago
Can't wait! Do you have any idea how far along this is? Is it likely to be months, quarters, years? (Funny expression, that. I'll wait, of course. It'll be a happy day when this works again and I can slowly make progress RE&#
37.
▲
by
aktau
7mo ago
Thanks for the note. Your corruption frequency anecdote matches mine. I don't have the mental werewithal to deal with that. I won't go back to radare2 until they change their project file stability somehow.
38.
▲
by
aktau
7mo ago
+1 I once tried learning how to RE with radare2 but got very frustrated by frequent project file corruption (meaning radare2 could no longer open it). The way these project files work(ed?) in radare2 at the time was that it just saved all t
39.
▲
by
aktau
8mo ago
Sorry about that, I can no longer edit my comment. Do you have any relation with the project apart from working at the same company?
40.
▲
by
aktau
8mo ago
More links with discussion: Reddit discussion: https://www.reddit.com/r/linux/comments/1qw4r71/microsofts_n... Project lead James Morris announcing it on social.kernel.org: https://social.kern
41.
▲
Microsoft open-sources LiteBox, a security-focused library OS
(github.com)
390 points
by
aktau
8mo ago
|
215 comments
42.
▲
by
aktau
8mo ago
From the GitHub page: LiteBox is a sandboxing library OS that drastically cuts down the interface to the host, thereby reducing attack surface. It focuses on easy interop of various "North" shims and "South" platforms. L
43.
▲
by
aktau
8mo ago
This is great. I'd love to do something similar for Ground Control (2000, https://en.wikipedia.org/wiki/Ground_Control_(video_game) ). Do you have a writeup of how you did it? Both (regular) tooling (radare2? rizin
44.
▲
by
aktau
8mo ago
> I changed read/write_file to put contents in the state and presented in the system prompt, same for the agents.md, now working on evals to show how much better this is, because anecdotally, it kicks ass. Can you detail this a bit
45.
▲
by
aktau
8mo ago
That matches what I recall too, back when I ran a very cheap integrated intel (at least that's what I recall) card on my underpowered laptop. I posted a few days ago with screenshots of my 2009 setup with awesome+xcompmgr, and I rememb
46.
▲
by
aktau
8mo ago
Perhaps worth mentioning: https://github.com/stapelberg/rsync-over-grpc .
47.
▲
by
aktau
8mo ago
I still have some screenshots in my GitHub repository of what my ArchLinux with AwesomeWM (X11) looked like in 2009. Those screenshots also contain the RSS, as luck would have it. 34MiB when on the desktop (clean), running X.org, AwesomeWM
48.
▲
by
aktau
8mo ago
> They were using tori primitives for the chain mail, and curve primitives for the clothing. (I.e., the clothing was actually woven out of curve primitives for the threads.) That sounds mind-blowing. Is this documented anywhere?
49.
▲
by
aktau
9mo ago
This is new to me. Can you elaborate please? Perhaps a link to somewhere showcasing this (and contrasting this to other solutions).
50.
▲
by
aktau
10mo ago
(I agree with other commenters' assessment about the importance of the authors complaints, and recommend others checkout the Go memory regions proposal.) For those interested, here's an article where Miguel Young implements a Go a
51.
▲
by
aktau
10mo ago
It's not the original source, but https://github.com/dpjudas/SurrealEngine is an active reimplementation of UE1.
52.
▲
by
aktau
11mo ago
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
53.
▲
by
aktau
11mo ago
Those commands are a (1) harder to grok and (2) do not actually use the memoized result (tmpfile.zst) to speed up a subsequent run. Can you give a more complete example of how you would use this to speed up developing a pipeline?
54.
▲
by
aktau
11mo ago
Yes, I know. I should've taken a different example. But it's also realistic in a way. When I'm doing one-offs, I will sometimes take shortcuts like this. I know awk fairly well, and I know enough of jq that I know invoking j
55.
▲
by
aktau
11mo ago
The name of the memo is the command that comes after it: $ memo my-complex-command --some-flag my-positional-arg-1 In this invocation, a hash (sha512) is taken of "my-complex-command --some-flag my-positional-arg-1", which
56.
▲
by
aktau
11mo ago
up(1) looks really cool, I think I'll add it to my toolbox. It looks like up(1) and memo(1) have similar use cases (or goals). I'll give it a try to see if I can appreciate its ergonomics. I suspect memo(1) will remain my mainstay
57.
▲
by
aktau
11mo ago
Glad you like it. Hope you get as much use of it as me.
58.
▲
by
aktau
11mo ago
The default storage location for memo(1) output is /tmp/memo/${USER}. Most distributions either have some automatic periodic cleanup, and/or wipe it on restart. Separately from that: - The invocation contains *memo*
59.
▲
by
aktau
11mo ago
Another thing I built into memo(1) which I forgot to mention: automatic compression. memo(1) will use available (de)compressors (in order of preference: zstd, lz4, xz, gzip) to (de)compress stored contents. It's surprising how much dis
60.
▲
by
aktau
11mo ago
I have a bunch, but one that I rarely see mentioned but use all the time is memo(1) ( https://github.com/aktau/dotfiles/blob/master/bin/memo ). It memoizes the command passed to it. $ memo curl ht
More ›