Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
camgunz
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
49 ms
·
721.
▲
by
camgunz
2y ago
I remember working on homework for "Discrete Computational Structures" (had to look it up ) in undergrad and having to come up with that sum of sequence of odds is the sequence of squares trick (it becomes clear if you visualize 4
722.
▲
by
camgunz
2y ago
Willpower is essentially made up: https://www.vox.com/science-and-health/2018/1/15/16863374/wi...
723.
▲
by
camgunz
2y ago
Aren't most of these spoofed addresses anyway?
724.
▲
by
camgunz
2y ago
I'm a little behind where you are (bad assembly knowledge) and I've always thought my next steps were learning about SPI and I2C, if that helps.
725.
▲
by
camgunz
2y ago
Microservices require Kafka (or a Kafka equivalent)
726.
▲
by
camgunz
2y ago
I don't have any experience with them, but you could maybe use Google's postmaster tools to debug.
727.
▲
by
camgunz
2y ago
Ah so you were a bulk sender. Yeah that's pretty fraught; AFAIK for Gmail you have to follow their bulk sender guidelines [0], which is a pretty long list of things to do. Not impossible though. But, again most people aren't sendi
728.
▲
by
camgunz
2y ago
I don't want this to turn into a big support thread, but I'm always surprised by this stuff. It's not like the algorithm has some case for small services like this, like Google's spam detection is heavily based on "
729.
▲
by
camgunz
2y ago
Online grooming is obviously very bad, but it doesn't seem like it's happening very much. Hope for Justice reports ~8,600 cases in 2022 [0], but there were 72.5 million kids in the US that year [1], so that's just .01% of kid
730.
▲
by
camgunz
2y ago
IME you generally don't need to worry about this if you: - Use DKIM, DMARC, and SPF [0] - Always send at least a text/plain version of your email - Don't send from an IP previously used to spam - Don't send gobs of mostl
731.
▲
by
camgunz
2y ago
I think the general premise is housing can't both be so cheap that people with nearly no net worth can get it, but so valuable that it can serve as a substitute for retirement savings. This is from first principles true, but it's
732.
▲
by
camgunz
2y ago
Maybe this'll come off as snarky, but I would build Excel! It would spread 10 million requests across the 10 million users, be totally immune to network outages, and my users could rest assured I wasn't thumbing through their data
733.
▲
by
camgunz
2y ago
I just finished the Security Cryptography Whatever episode [0] about this and when Eric Rescorla is going on about how they almost threw the Web PKI overboard for a blockchain but it was too slow I was like, "just use a layer 2 like Li
734.
▲
by
camgunz
2y ago
I (of course) wanna plug Vim again here. Vim comes with a great terminal, you can arrange the windows however you want, you can save the layouts in your sessions, and the keybindings for doing all of it are real straightforward. I used to u
735.
▲
by
camgunz
2y ago
"Worse is better" comes from an ancient story where the Lisp folks were trying to design an elaborate system for resuming interrupted syscalls, and the UNIX folks just returned a "we fucked up" error to the caller instea
736.
▲
by
camgunz
2y ago
This has been a thing for a little while: https://calmtech.com/
737.
▲
by
camgunz
2y ago
Yeah that's probably too much of a slog. It's probably the case that very few things would break if you just snuck the validation out the back door and added like u8str (or whatever) that did the validation for people who want tha
738.
▲
by
camgunz
2y ago
I'm pretty well convinced at this point that specifying an encoding for a system language's string type is probably too constraining--and like you point out, often commits the sin of requiring unnecessary processing. Your CSV exam
739.
▲
by
camgunz
2y ago
I'm doing some NNTP-related work and hadn't looked seriously at Nostr until just now. It looks like the main benefit is just that it signs events, is that right?
740.
▲
by
camgunz
2y ago
The Go thing (+ invalid sequence conversion) is a really good point. If OP's point was "don't validate just convert invalid sequences when you need to" or "think twice before forcing validation into your primitive s
741.
▲
by
camgunz
2y ago
> But that only applies to the region of the pattern in which Unicode mode is disabled. Yeah I mean, fair but I'm not impugning bstr or byte-based regexes. Broadly my worry here is people will say, "I'll be cool; I'll
742.
▲
by
camgunz
2y ago
> I'm the author of Rust's regex engine. Treat me as an oracle. What is your specific concern? I know and I'm terrified haha. That's a very generous offer; I don't disagree w/ your post or OP's basic p
743.
▲
by
camgunz
2y ago
I'm referring to #2 there: "In ASCII compatible mode, Unicode character classes are not allowed." > Pretty much all string processing I've built up in Rust over the past ten years is based on the idea of not validatin
744.
▲
by
camgunz
2y ago
Maybe! Or maybe another tool is like, "oof that's some junk in there, let's pop that out"
745.
▲
by
camgunz
2y ago
"\033[31;1;4munderlines\033[0m" is (again) no worse than a stream of vertices or a stream of object code. Everything is a stream of bytes (well, a stream of bits anyway). Do you want CSS? Lipgloss is not too far off [0]. I read yo
746.
▲
by
camgunz
2y ago
> Regex engines neither know nor care what a character is. They match bytes. I think this is mostly not true, for example there's some interesting behavior in POSIX-compliant engines: "Other than POSIX-compliant engines part of
747.
▲
by
camgunz
2y ago
You need to know about Unicode to use Unicode regexes; if you want to pass invalid UTF-8 into these engines you have to give up Unicode regex support; i.e. how would you match "\p{East Asian Width:Narrow}" on an invalid UTF-8 stri
748.
▲
by
camgunz
2y ago
>> - You can't just skip stuff if you run any kind of normalization > - delay validation until normalization You probably want to normalize if you want to use them as keys in a hash table, which is pretty common. Or serialize
749.
▲
by
camgunz
2y ago
You do have to validate UTF-8 strings: - You can't just skip stuff if you run any kind of normalization - How would you index into or split an invalid UTF-8 string? - How would you apply a regex? - What is its length? - How do you deal
750.
▲
by
camgunz
2y ago
There are libraries and frameworks that abstract this for you: ncurses, bubbletea, etc. At some point, every interface is low-level: GPU geometry is a stream of vertices, a program is a stream of bytes. This isn't some terminal-specifi
More ›