privatelypublic

Nice! But, doesn't negate my intent: warning that .net isn't immune to the binary serialization issues.

I haven't had much of a chance to work with non-framework/mono unfortunately. So, good to see they made the issues explicit. Though, I chuckle at the idea of companies upgrading such to errors via config- but thats an iceberg of "the street is looking better than doing more coding."

Anything that isn't fiber is still frequently nitrogen pressurized.

Side note: as a teen I always wondered why those tanks never got stolen. When I got a car I stopped one day and checked- they were stamped with the teleco name. Writing this I wonder: did they stamp the regulator too?

.Net has similar issues.

The idea that the session ViewState is a static encryption shared across all installs (unless I misread that)... speaks poorly of the software product in general.

This IS the botnet that offers the service.

I expect rolling shutters to be a far larger issue. Haven't read the article a second time, but non-uniform and inconsistent lighting is a huge challenge for this kind of work.

I always thought the shrimp was a random meme. This is even better!

My understanding is There's also studies of "duh!" Things, so theres a paper to cite instead of an assumption.

This doesn't appear to he exclusively anti-evil maid. It takes "build an AMI that doesn't have enough userland to extract the keys" and extends it to "only approved AMI's can access the keys."

Lateral movement of attackers. Shadow IT. People modifying things between test and Prod.

All easy examples that don't require you to trust AWS hasn't backdoored it to still get better security.

Somehow, if you have to use residential proxies, its going to he a TOS break.

Ink is perfectly capable of being a phosphor, in which case it'll up or down convert wavelength X to wavelength Y.

Among other things... having hundreds of calls and texts onramping from the same IP would be a rather large red flag.

I'm a little surprised that a behavioral analysis didn't flag these anyway. Probably did, just the networks don't care as long as they get their cut.

So, at what point does YAML needing magic incantations, wrapping everything in quotes, avoiding any form of templating, etc. stop being less verbose (oops, meant noisy), and "annoying?"

Reality is, clunky XML is badly designed, or simply has no schema attached.

No, there was a vending machine smart lock that if you hitachi'd it right it'd unlock.

And, I phrased it wrong: most people expect to be able to walk into lowes and clone a key. And while it seems assa has been on a buying spree since I last looked at them, I do not associate them with anything you'd be able to find at big box store. When I think assa abloy I think "you better have the key card or you're SOL."

What is so verbose about a cdata directive? Everybody complains about XML being verbose, never once heard complains about HTML being too verbose.

Can't take this seriously if XML isn't listed as an alternative.

Those monitors are useless. Unless they're VERY expensive they only show a change over a short period of time

One of their digital lock designs had a rather cough Pleasing vulnerability. But other than that it's vendor lock-in (heh), and lack of availability in the US.

With most so called locksmiths being drillsmiths in the US, not being able to clone DD and dimple keys.

Puck one. Or maybe the OP is just bitter they can't pick it for their next "belt" after getting chuffed with themselves picking average american garbage.

And the inexperienced. I got hyped over golang a while back because of go routines. Then I discovered any remotely recent .net version already had what I needed. (I'm a c# dev by default)

Python makes me want to pull my hair out though. Full blown virtual machines make running it tolerable, but the language's inconsistencies... though, I keep trying because I'm hoping theres patterns I don't see.

I'm thinking eval's and prototype overloading would make this a permanent cat and mouse game.

Frankly, I don't see how the node ecosystem can ever be secure. It's random-libraries all the way down. With half of them being useless frippery.

Imho, WASM compiled from languages that have strong standard libraries are the way forward for security. And, maybe node will get fixed in 5-10 years.

A good example of a language going "this shouldn't be a library."- Net used to only have a third party json parser (newtonsoft) but microsoft created a first party json parser and deprecated newtonsoft from their examples and templates

Sounds like You're conflating sale of a product prior to filing with "prior art"

Yea, micro reactors sound like a great idea for pollution control. But, given how many ships get seized every year trying to fake inspections and a dozen other things- the only way this works out is a modern version of Clipper ships (with less sinkings). Large premiums for getting your cargo across the ocean faster.

How much faster, is for somebody more knowledgeable than me to answer.

And now politics comes into play: these ships would have to not only have significant permanent armament, but given significant latitude to use lethal force.

Not sure that's possible with JS.

JWST is special in that it needs to avoid radiated photons for its IR images.

Yea, plenty of cameras need precise temperature control too. A laser or LED shifting spectra is just the easiest and most accessible example I could think of.

Highspeed needing it is a head scratcher though. Best I can come up with is the sensor needs relatively low temperatures, that or as the frame gets smaller on the sensor to up the framerate the power density goes nuts.

How do you handle them latching the wrong way and letting out the magic smoke? Built into the chips?

They know where every item is- if not, how do FBA folks get their stuff back?

By far their most useful application is precision thermal control. Need that LED or laser to be within 0.05C to maintain its wavelength? Literally nothing else can do it.

60C is still more than enough to burn you. Just, not the instant you touch it.

Theres foss EEG machines already. $300ish to buy a fully working "same device as The FDA version just sans-certification."

Much less if you want to build it yourself.

Doesn't cloudflare and amazon have this now? Pretty sure CF is developing a closed source player- but theres plenty of FOSS ones (rip the one jellyfin uses out of it- at worst).

And, theres plenty of tutorials on using ffmpeg based tools to make the files. And yes, "oh no, I need to learn something new for my video workflow."