“Support” here probably means “we’re testing jQuery for compatibility on those web browsers” - likely Safari from iOS 16 still runs this version of jQuery just fine. However, running automated test suites or support bugfixing for those clients is a lot harder than spinning up some Microsoft-provided VM with IE11 on it.

Also, mobile phones get upgraded/upcycled much faster than desktop.

Fair point.

Mark Rutte is more of an administrator than truly the head of NATO. A spokesperson. NATO is a committee.

> The developers who get displaced are the ones doing purely mechanical work that was already well-specified.

And that hits the offshoring companies in India and similar countries probably the most, because those can generally only do their jobs well if everything has been specified to the detail.

At work we’re incrementally rewriting a legacy Javascript Electron application in Blazor / C# WASM. The biggest issue we’ve run into as far as WASM interop goes is that it is not really possible to pass objects between WASM and JS. It requires some form of serialization to JSON or a different blittable format. Since the data we work with in the application is quite large, this has caused some headaches.

But why are you? Unless it requires interfacing with a JS library or some JS operation on the DOM, the goal of a Blazor app is to write in C#, not JS. What's your JS code doing that it requires passing C# objects to it? (That said, Blazor supports JS Interop, see https://dev.to/rasheedmozaffar/intro-to-js-interop-in-blazor...)

I think HTTP web sockets would be an interesting tunneling protocol.

Tor has a transport using exactly that.

https://blog.torproject.org/introducing-webtunnel-evading-ce...

You don't need websockets, just Connection: Upgrade to anything you want. You can upgrade directly to ssh protocol and just pass on decrypted data from https socket to local port 22 from then on with no further processing.

Proper DPI can tell that wouldn't be acting like a typical HTTP stream, encrypted or not.

Hehe true, SSH traffic is so characteristically obvious that the packet size and timing can be used as a side channel to leak information about a session.

Tangential: but I recall reading about a similar technique used on SRTP packets to guess the phonemes being uttered without needing to decrypt the traffic.

I guess you would need to either mimic a protocol that always uses a fixed packet size/rate (like a MPEG-TS video stream or something), or artificially pad/delay your packets to throw off detection methods.

would not be able to tell from websockets uses

I think most websockets do not sustain large amounts of bidirectional traffic for prolonged periods, so IMO this would immediately be suspicious.

My typical ssh session does not either.

Interesting - why did they chose to rebuild the menu system of Doom 3 OG?

I doubt you learned anything as all your posts are em-dashes LLM outputs about lightning.

Well, at least I learned a thing or two from this, or more like, to keep in mind for my next time messing with lights.

On diffusing them, I've had lamp shades that were adequate on paper but still didn't feel right; one eye would hurt and a headache would start (it has its own cause, after getting lasik a decade ago, I still see great but uneven light triggers a migraine) couldn't pinpoint until I started playing around this, rather than just limiting myself to intensity, temperature and the standard diffusion.

SSH using GPG Yubikeys and git signing using GPG was quite a process to set up on Windows a few years ago. Not something I'd want or know how to repeat. Hopefully things have improved in the mean time.

You can use SSH keys for signing now, so you don't need GPG at all.

Apple iPad Pro 2021. It replaced a failing aging Microsoft Surface tablet but is so much less powerful. It is really just a phone with a keyboard. It becomes real powerful used as a remote desktop client to my Windows computer though.

If this analysis is sound, I wonder if it can be mitigated by using tools instead of structured outputs.