Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Piskvorrr
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
61.
▲
by
Piskvorrr
2y ago
Data limit doesn't seem to be the main bottleneck: "Got my 2Tb done in 3 days where it would have taken half a year back home." (emphasis mine)
62.
▲
by
Piskvorrr
2y ago
TLDR: "Let the unimportant (i.e. NOT ME, NOT MINE) perish"
63.
▲
by
Piskvorrr
2y ago
Actually, they do matter. Assembly lines give you GREAT control over where the code is located, how it's lit ( consistently ), and what you do on read error (can't shunt off the passenger to a read error bin, so they don't ho
64.
▲
by
Piskvorrr
2y ago
There was a push for a gated system here, some years ago. The vendor tried to sell it on massive cost savings...and was publicly humiliated by a bunch of geeks with an Excel table. Turns out, installing and running the gates would, at best
65.
▲
by
Piskvorrr
2y ago
Pretty sure you wouldn't want to make two of those in succession. I mean, last time I had to pay a fine for not having The Correct Blessed Type Of Ticket, I did pay a lot of attention to the tickets I bought next. (Wasn't as expen
66.
▲
by
Piskvorrr
2y ago
I have been expecting a range, in which there's a pass that's 30m in height below the average of the ridge : -----_--- (edit: apparently features like that exist, e.g. Roland's Breach)
67.
▲
by
Piskvorrr
2y ago
Meta: "Privacy is dead, we own your data now." EU: "No you don't." Meta: "Uh, ok."
68.
▲
by
Piskvorrr
2y ago
TLDR: work performance dropped.
69.
▲
by
Piskvorrr
2y ago
Betteridge's law of headlines supports this: adding 1/8 cup non-toxic glue will surely bring peace and prosperity. (Sources: made it up myself. But if I just had made it up using a large language model, suddenly it would have be
70.
▲
by
Piskvorrr
2y ago
You would never do that, I wouldn't either, but in machine-to-machine API interactions, this tends to crop up - i.e. a SW stack where this implies "an array of `a` values and a scalar `b` value" sends the data to a SW stack w
71.
▲
by
Piskvorrr
2y ago
ISO 3166-2:XK - self-assigned, in use, but I wouldn't go as far as calling it "stable." I mean, it's been in an explicitly declared unstable state ("about to be assigned an official code") for over a decade.
72.
▲
by
Piskvorrr
2y ago
Not that I'd get about 5 different ISO country code changes (with some flipflopping) just by sitting in this very same spot for a couple of decades. "Stability" in country codes, bah humbug.
73.
▲
by
Piskvorrr
2y ago
And I've been bitten by this design numerous times. The most common bug: literally the birthday paradox, i.e. "these two people have been assigned the same number, and now we need to distinguish them in our database".
74.
▲
by
Piskvorrr
2y ago
It's a mere convention: "a querystring of this type is an array of parameters, the order of which is irrelevant" - this is one of the tautological "valid except when it's not" non-rules (a surprising number of
75.
▲
by
Piskvorrr
2y ago
It's obviously a �. Or perhaps a □ . Maybe an ¾, on odd Wednesdays? (Unicode has its strengths. Making up replacement characters isn't one.)
76.
▲
by
Piskvorrr
2y ago
There's an interstate underneath , which is the reason there's a complicated intersection at all. Building another bridge level might be safer for pedestrians, but also more expensive in construction and maintenance, plus now you
77.
▲
by
Piskvorrr
2y ago
Four crossing points (two with traffic lights, in this case), whereas for a "normal" interchange, you'd get...also four crossing points. diverging diamond: https://www.openstreetmap.org/directions?engine=fossg
78.
▲
by
Piskvorrr
2y ago
Such as...in the Danube river O_O https://phys.org/news/2020-09-brown-danube-belgrade-sewers-t...
79.
▲
by
Piskvorrr
2y ago
That's one of the instances of "built with good intentions" I had in mind.
80.
▲
by
Piskvorrr
2y ago
It's not as if the printer keeps a hidden cache of printed pages. Except maybe it does...even if the feature was created for entirely benign reasons.
81.
▲
by
Piskvorrr
2y ago
If you don't have any 7s in the text (and 1s only - or vice versa!), it's hard to say what they are. I did encounter this multiple times.
82.
▲
by
Piskvorrr
2y ago
Yup. "Try as best as you can (to eventually deliver, not ASAP), but if you can't - well, all content in transit is considered ephemeral." I mean, I do battle with notification-FOMO as much as anyone; if it works, go for it.
83.
▲
by
Piskvorrr
2y ago
E-mail is, at its core, best-effort, respond-maybe protocol. Implementing "quiet hours as seen in IM", means using the wrong tool. If you insist on treating e-mail as a medium requiring immediate response, you'll be going int
84.
▲
by
Piskvorrr
2y ago
That's one side of the issue. The other: where have such takeovers succeeded, and continue undetected, because the attacker did not (yet?) make a 500000-millisecond-blunder?
85.
▲
by
Piskvorrr
2y ago
They seem quite happy to use OSM data. We'll see how this stacks up w/r/t license: from here (and obviously IANAL), it looks very much like "sure, give us all the ODbL data you have, but we're doing a magic trick
86.
▲
by
Piskvorrr
3y ago
I suppose Google being both the browser vendor AND an Analytics provider complicates things somewhat...
87.
▲
by
Piskvorrr
3y ago
To borrow terms from RFC 2119, "having a child makes people more responsible" is a SHOULD, but statistically, turns out to be a MAY. (#survivorBias: people are likely to acknowledge this, if they did turn out to actually be more r
88.
▲
by
Piskvorrr
3y ago
Well if incompetence is cheaper to implement, out come the lawyers to erase whatever perceived savings there were.
89.
▲
by
Piskvorrr
3y ago
Possibly. You don't want to use the older client for anything except connecting to the older system. Keep it somewhere offline (encrypted, whatever: distinctly non-executable), too. (Not that it would solve the issue altogether, se
90.
▲
by
Piskvorrr
3y ago
"search engines didn't exist until google" - you might want to, uh, google that
More ›