Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
raggi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
27 ms
·
301.
▲
by
raggi
2y ago
Code wise, probably Fuchsia. I worked up and down the Fuchsia stack regularly, from bootloaders to GUI programs and all over in-between. For a sizeable code base with so many layers and concepts, and regularly moving between these without m
302.
▲
by
raggi
2y ago
Also, the many speaker sound of “aaaaaaaaaaaaah” was delightful
303.
▲
by
raggi
2y ago
Serious Sam was always a killer LAN party game. Not necessarily because it was the sexiest title of the day, or what anyone had planned. Serious Sam won the LAN party because even when every other game died under some driver issue, thermal
304.
▲
by
raggi
2y ago
If that's representative of the order volume I'm quite curious what the motivation/business case is for shifting technology stacks from one slow dynamic environment to another slow dynamic environment?
305.
▲
by
raggi
2y ago
> I fail to see what "risky surface areas" in the kernel you're avoiding. You have more packets going through the kernel network stack(since you're wrapping a TCP connecting in a UDP connection that goes through the k
306.
▲
by
raggi
2y ago
not enough detail here to provide a good answer, but I can tell you explicitly that if you're using SMB you're likely not going to get good performance here even if your network stack is has tons of space to overcome bdp and conge
307.
▲
by
raggi
2y ago
You can have multiple layers of security boundary on most of the customer-exposed surface area, and avoid more risky surface areas in the kernel. Portable is a bit of a weird word here because for many of us with gray beards the word means
308.
▲
by
raggi
2y ago
It's less mature, which shows up in lots of places, such as sometimes having less than ideal defaults (as in buffer sizes shown here), and bugs if you start using more fancy features (which improve over time of course). This is approxi
309.
▲
by
raggi
2y ago
It's great to see this, I know the team went on a long journey through this and the blog makes it almost look shorter and simpler than it was. I'm hoping one day we can all integrate the support for GSO that's been landing in
310.
▲
by
raggi
2y ago
for some definition of portable which is deeply tied to the go runtime
311.
▲
by
raggi
2y ago
fwiw, you technically don't need a privileged container to use tun, you just need suitable permissions on the kernel tun interfaces.
312.
▲
by
raggi
2y ago
hey Ian, long time. Is there any chance y'all could swap out main so that main contains the generated code version? I don't know the status on those export tools these days as I left the company years ago, but if they could sync w
313.
▲
by
raggi
2y ago
true, but then they'll escalate to wanting the real watches, and the next generation i'm sure will get premium pricing now
314.
▲
by
raggi
2y ago
Yup, and far too much spinning going on in the runtime too.
315.
▲
by
raggi
2y ago
Sure you can have a million goroutines, but you’ll now have more scheduler and gc overhead, and this is part of the issue. Calling out to ffi requires preparing both the stack and the runtime for that call. It’s theoretically possible to av
316.
▲
by
raggi
2y ago
cgo is extremely slow, particularly in programs with many active goroutines. I regularly look sad at profiles of production cgo programs where findRunnable is in the top 10.
317.
▲
by
raggi
2y ago
You can just use a local image too though, what is the news here?
318.
▲
by
raggi
2y ago
Yup, scanned through the video, I don’t think the guy authored a single function, just grabbed skel and parts from other code bases, deleted stuff he didn’t want and fixed a little glue and build code
319.
▲
by
raggi
2y ago
Intel USB controllers are extremely forgiving of control software bugs. Extremely
320.
▲
by
raggi
2y ago
Disk encryption is what kills off these kinds of tools, they're useless on encrypted volumes. Some disk vendors themselves still ship specialized tools for smart block image recovery, if you've gone looking for recovery tools and
321.
▲
The furry frustration security strategy – matrix protocol edition
(gist.github.com)
2 points
by
raggi
2y ago
|
0 comments
322.
▲
by
raggi
2y ago
NextDNS _does help_ though by way of being DoH, so while your packets might be traversing a less desirable path they’re not readable.
323.
▲
by
raggi
2y ago
Except in their marketing materials they just say `ssh terminal.shop` Users will fall into the TOFU trap, most users who've sent them cash certainly did. Most users won't put their credit card credentials into a page that they
324.
▲
by
raggi
2y ago
or better yet, don't use ssh for this purpose, it's not good for it. letsencrypt is free, you might hate the browser for many fair reasons, but PKI and the CA/B forum are actually effective.
325.
▲
by
raggi
2y ago
It’s available via ssh and https That shots from my parents balcony in Bermuda
326.
▲
by
raggi
2y ago
Before a bunch of you run off and make more of these “because it’s cool”, they’ll likely lose access to stripe once stripes security team pay attention and realize that this can be trivially man in the middled and doesn’t actually offer the
327.
▲
by
raggi
2y ago
You actually want to verify first or someone will mitm you, e.g. mitm.terminal.shop.rag.pub
328.
▲
by
raggi
2y ago
It largely depends what you mean by "works just fine", if all you want is "high throughput on a low latency link" then sure, whack up the buffer and throw it at the wall, it'll stick - but you can just as well use c
329.
▲
by
raggi
2y ago
It’s a shame that they don’t talk about it in the article but a big part of the drive toward next generation tools is to study the interfaces needed and used by quic implementations which can’t “just be solved by” the flags you’re talking a
330.
▲
by
raggi
3y ago
I threw the code away again in the end. We didn't have that much of a need for non-UEFI targets, but I was experimenting at the time with booting on some cloud x64 machines that lacked UEFI support. If I had to do it again, I'd pr
More ›