adgjlsfhk1 (u/adgjlsfhk1)

adgjlsfhk1 commented on U.S. government takes 10% stake in Intel cnbc.com/2025/08/22/intel... · Posted by u/givemeethekeys

ac29 · 2 days ago

> It's the only chip manufacturer "left" in the US

Global Foundries, Micron, and Texas Instruments all come to mind

adgjlsfhk1 · 2 days ago

GF hasn't gone past the 12nm node. TI is at 45nm. Micron is on relatively recent processes, but they make RAM, not logic (which are totally different processes). Intel is the only chip manufacturer left that is working in logic at anything like the leading edge.

adgjlsfhk1 commented on How much do electric car batteries degrade? sustainabilitybynumbers.c... · Posted by u/xnx

connicpu · 7 days ago

I think the biggest hurdle to just doing that is who pays for the electricity. Sure right now it's a nice perk you can provide your EV owning visitors that probably won't cost too much, but in a world where 10%+ of cars are EVs the costs will add up even at level 1, so you'll need to go for capital-C Chargers that come with payment infrastructure.

adgjlsfhk1 · 7 days ago

one answer would be to make the parking spaces expensive enough to account for electricity. parking meters are pretty widely adopted.

adgjlsfhk1 commented on Electricity prices are climbing more than twice as fast as inflation npr.org/2025/08/16/nx-s1-... · Posted by u/geox

dehrmann · 7 days ago

It's not just the generation; it's also the maintenance. If you own your own rooftop panels and a few go out, it's relatively expensive to bring someone out to replace them...if a mechanically and electrically equivalent replacement exists in 5 years. At utility scale, you're always replacing panels, so you have dedicated staff doing it.

adgjlsfhk1 · 7 days ago

solar panels last 25-40 years. mechanically equivalent means "sits on a roof". electrically equivalent just means "connects to a wire".

adgjlsfhk1 commented on Modern Cars Wreak Havoc on Radar Detectors thedrive.com/news/modern-... · Posted by u/PaulHoule

stefan_ · 8 days ago

Its like the dumbest product manager meme. “Humans use eyes for this right, why can’t our gadget?” “It must work at night? Oh we will just use a thermal camera” “Pixels in an image are not all from the same time instant? We will just pay 10x for a global shutter camera”

The list goes on and on and on. No, they will not just be replaced by whatever is producing loose AI facsimiles of the real world in a smartphone.

adgjlsfhk1 · 8 days ago

you can also just use a normal rolling shutter camera at a higher frame rate and blur the frames together.

adgjlsfhk1 commented on Rust in 2025: Targeting foundational software smallcultfollowing.com/ba... · Posted by u/wseqyrku

codys · 8 days ago

When you say "modern GC", which particular implementation(s) of GC are you referring to?

adgjlsfhk1 · 8 days ago

Java has an excellent GC, but a horrible runtime. .net is probably the best GC integrated into a language with decent memory layout ability. If all you want is the GC without a language attached, LXR is probably the most interesting. it's part of MMTK which is a rust library for memory allocation and GC that Java, Ruby, and Julia are all in the process of adding options for.

adgjlsfhk1 commented on Princeton NuEnergy's battery recycling tech recovers 97% of lithium-ion material energy-reporters.com/envi... · Posted by u/jbotz

zaphar · 8 days ago

It was my understanding that battery fires don't go out because they are basically self fueling. You would be better served having a way to contain it until it burned itself out.

adgjlsfhk1 · 8 days ago

it's self catalyzing, but only above a certain temperature. if you dump enough water on it, it goes out

adgjlsfhk1 commented on HTTP/1.1 must die: the desync endgame portswigger.net/research/... · Posted by u/sprawl_

mittensc · 10 days ago

> It's not correct to attribute all bugs to carelessness

Sure, just the bugs in the link.

Content-Length+Transfer-Encoding should be bad request.

RFC is also not respected: "Proxies/gateways MUST remove any transfer-coding prior to forwarding a message via a"

Content-Lenght: \r\n7 is also a bad request.

Just those mean whoever wrote the parser didn't even bother read the RFC...

No parsing failure checks either...

That kind of person will mess up HTTP/2 as well.

It's not a protocol issue if you can't even be bothered to read the spec.

> The post makes the case that HTTP/2 is systematically less vulnerable than HTTP/1 to the kinds of vulnerabilities it's talking about.

Fair enough, I disagree with that conclusion. I'm really curious what kind of bugs the engineers above would add with HTTP/2, will be fun.

adgjlsfhk1 · 9 days ago

I think the main point is that these sorts of parsing mistakes shouldn't be so easily exploitable and the problem is that the length is non trivial to parse, so if you mess up the parsing of that it escalates the security of a ton of other bugs.

adgjlsfhk1 commented on Thai Air Force seals deal for Swedish Gripen jets scmp.com/news/asia/southe... · Posted by u/belter

cm2187 · 9 days ago

My limited understanding is that the F135 is massively over-powered to be capable of VTOL + push through the bulky shape of the F35, resulting in a disappointing range. I don't know that it would make sense to use it on a different platform.

adgjlsfhk1 · 9 days ago

That just means it's the right size engine for a bigger plane without vtol.

adgjlsfhk1 commented on NIST Finalizes 'Lightweight Cryptography' Standard to Protect Small Devices nist.gov/news-events/news... · Posted by u/gnabgib

adrian_b · 11 days ago

That classification has more steps.

Some things must be encrypted well enough so that even if NSA records them now, even 10 years or 20 years later they will not be able to decipher them.

Other things must be encrypted only well enough so that nobody will be able to decipher them close to real time. If the adversaries decipher them by brute force after a week, the data will become useless by that time.

Lightweight cryptography is for this latter use case.

adgjlsfhk1 · 11 days ago

The hard part is that anything designed to be breakable in a week is only ~150x away in strength from being broken in an hour. That means you need to be incredibly confident about how strong your algorithm is. It's much easier to eat a little bit of cost such that you think it's invulnerable for thousands of years because that way you don't need to worry about a factor of 2 here and there.

adgjlsfhk1 commented on NIST Finalizes 'Lightweight Cryptography' Standard to Protect Small Devices nist.gov/news-events/news... · Posted by u/gnabgib

tptacek · 11 days ago

I am way out of my depth both on power consumption and leakage, but presumable Ascon does better on both counts than Chapoly.

adgjlsfhk1 · 11 days ago

Realy ChaCha seems trivially implementable without leaking anything.