Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Groxx
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
33 ms
·
751.
▲
by
Groxx
1y ago
I'm under the impression that CORS largely solves it? which is still much too new to be able to shut down the PSL of course. but maybe in 2050.
752.
▲
by
Groxx
1y ago
mentally adding this to my "obviously a problem in retrospect" list. hadn't thought of it before though. OTOH, do you think a diagonal-lined-background on the removed side would work better? like striped light and dark red,
753.
▲
by
Groxx
1y ago
agreed, though I can see it making some sense in those specific situations, e.g.: > PCL reduces cost by 86% on interior curved lines layout at Vancouver airport for random bits of complicated-shape fashion in a giant flat open area, I c
754.
▲
by
Groxx
1y ago
does that actually matter much on anything except dirt-bike tracks, or trying to go 40mph on a horrifically bumpy track? minus some comfort advantage, of course. like technically, sure, it's obviously true. but for performance it o
755.
▲
by
Groxx
1y ago
I'm not really seeing how re-emphasizing Google's involvement implies a reduced chance of abandonment. Google's kinda famous for that.
756.
▲
by
Groxx
1y ago
> As an additional complexity, although string literals are UTF-8 encoded, they are just aribtrary collections of bytes, which means you can technically have strings that have invalid data in them. In this case, Go replaces invalid UTF-8
757.
▲
by
Groxx
1y ago
you seem to be reading that backwards, that's the content that was removed . it now just says "if LLM, banned": https://github.com/twpayne/chezmoi/blob/master/.github/CODE_...
758.
▲
by
Groxx
1y ago
they're even more blatant in some other articles: https://quasa.io/media/indie-filmmaking-flees-los-angeles-cr... I think we can just immediately write this site off as "probably complete-trash blogspam"
759.
▲
by
Groxx
1y ago
their LLM probably didn't suggest it
760.
▲
by
Groxx
1y ago
how many lines of code is it though? or how many tokens? we need something we can measure if we're gonna fire people!
761.
▲
by
Groxx
1y ago
could have, absolutely. should not have been in any commit , which is basically necessary to prevent this case, almost definitely not. it's normal, and requiring all data to be generated just means extremely complicated generators
762.
▲
by
Groxx
1y ago
ah, yes, this is one I remember seeing early on! thank you! I couldn't find much past the blogspam this time :/
763.
▲
by
Groxx
1y ago
committed files with carefully crafted bad data is extremely common for testing how your code handles invalid data, especially with regression tests. and lzma absolutely needs to test itself against bad, possibly-malicious data.
764.
▲
by
Groxx
1y ago
mostly no, from my reading - it was a multi-stage chain of relatively normal looking things that added up to an exploit. helped by the tests involved using compressed data that wasn't human-readable. you can of course come up with w
765.
▲
by
Groxx
1y ago
mostly Go, because that's at work. for a variety of reasons, I have helped troubleshoot at least 100+ teams' projects, many of which have had concurrency issues either obvious in nearby code, or causing issues (which is why I was
766.
▲
by
Groxx
1y ago
it's pure waste-generation, but hashcash is a fairly old strategy for this, and it's one of the foundations of Bitcoin. there's no "proof of payment to any beneficial recipient", sadly, but it does throttle high-vo
767.
▲
by
Groxx
1y ago
looks fantastic, and rust is probably a great language for this since ownership restricts effects - even if you add it to python, you can't really trust it, because at runtime you can just run up a call stack and modify memory at any
768.
▲
by
Groxx
1y ago
yep. it's suddenly more-obviously valuable, so it's getting done.
769.
▲
by
Groxx
1y ago
also training data quality. they are horrifyingly bad at concurrent code in general in my experience, and looking at most concurrent code in existence.... yeah I can see why.
770.
▲
by
Groxx
1y ago
> Our estimates of the total surface partitioning capacity are much larger than if the reservoirs are taken to be thin organic films on smooth, impermeable surfaces. ... so is "smooth, impermeable surfaces" the current begrudg
771.
▲
by
Groxx
1y ago
this is true for any kind of error branch - if the cause is persisted, it's going to still be there on the next iteration.
772.
▲
by
Groxx
1y ago
outside political definitions, I'm not sure "crash and restart with a supervisor" and "don't crash" are meaningfully different? they're both error-handling tactics, likely perfectly translatable to each o
773.
▲
by
Groxx
1y ago
Made even easier by almost everyone running their local network off the ISP's hardware. Before they get cut off, have the router take a snapshot of what's using what ports, then go hunting.
774.
▲
by
Groxx
1y ago
You can solve just about any distributed systems problem by accepting latency, but nobody wants to accept latency :) ...despite the vast majority of latency issues being extremely low-hanging fruit, like "maybe don't have tens of
775.
▲
by
Groxx
1y ago
"dim" implies "there is something normal there that is just not emitting light". "dark" in this astronomical sense means essentially "dim and completely transparent " which is not what you get with
776.
▲
by
Groxx
1y ago
Not really? At best it's "DDOS prevention sellers are having trouble" and "ISPs say they're doing fine". The vast majority of the article is talking about the various kinds of malware causing this, and how so
777.
▲
by
Groxx
1y ago
Yes, you generally see this kind of thing start from the pain-feelers and move up the chain to the pain-causers. So why hasn't that happened? These are clearly damaging to many, and ISPs are apparently doing next to nothing to prevent
778.
▲
by
Groxx
1y ago
I'm honestly kinda curious why nobody's blocking these IPs from sending data near the source. Like, I can come up with plenty of possible reasons, and reasons why it could potentially be very bad if ISPs started cracking down on
779.
▲
by
Groxx
1y ago
a fairly large number can be unlocked, yes. Google's devices have just generally been the most visible because they've always been easy to target, and they have the biggest possible name behind them. for a lower bound, check a re
780.
▲
by
Groxx
1y ago
people have been gluing other languages on top of languages practically forever - it's a DSL. no single language is ideally suited for every situation, it's not inherently a sign of failure that someone makes a DSL. and since anno
More ›