I based that on seeing the BBC Science TV series (and books) Connections by science historian James Burke. If it's been updated since, then I stand corrected. Regardless of the specific example, my point was that sometimes modern standards are linked to long-outdated historical precedents for no currently relevant reason.
Awesome. I've just designed and built my own z80 computer, though right now it has 32kb ROM and 32kb RAM. This will definitely change on the next revision so I'll be sure to try it out.
I don’t know, that looks like a lot more than just a stall. There was a ton of flame that looked like it was coming out of the front or top of the engine, rather than just something shooting out the back.
I think you're looking at the left wing (number 1) engine; GP is talking about either the tail or right wing engine. (I think tail is number 2 on MD-11.) There's a brief explosion visible through the smoke at about 1-2 seconds in, to the right of the engine visibly on fire; that's probably what he's talking about.
Yup makes sense. Now seeing photos of the entire left engine on the ground by the runway and the implication that however it failed it might have damaged the tail engine.
The rotation already exacerbates the flow into that engine. Change in flow geometry gets more smoke in its way when it's already eating turbulent air.
We don't know if it just had a disruption or a full-blown stall, but give the way it made it to takeoff speed and then just gave out, stall seems likely.
I would say it does not, in fact, look like a compressor stall. It looks very much like an uncontained disassembly, presumably from fan blades that suffered a catastrophic failure and broke up in a way that exceeded the limits of the engine's containment.
Obviously impossible to tell from some cell phone type videos. Being struck by something is also possible. But it sure does look like an uncontained engine failure.
There was once an application, long gone and probably short lived, that let you ring payphones for free over the internet. Me and my mates had a great time phoning up times square, a pub in Australia and other places chatting to randoms.
Oh I thought I couldn't hate them anymore and I learn this. My leg currently has large hives on it from multiple bites, the antihistamines I have are doing bugger all.
I'm currently testing for alternatives of minio on my homelab. Ceph was nice, lots of bells and whistles, built in support for virtual IPs is excellent, but on my aging hardware it was using 10-15% CPU in my VM while idle. Currently benchmarking garagefs, scales very well with core count and multi node set up is a breeze.
Dan Kaminski popularized this in 2007-8 or so. Not that it didn't exist here and there, but he made the perhaps first public version of a dns tunnel (ozyman). he inspired iodine and others and was a fairly well known guy.
Dan passed away in 2021, rip.
if you search for it its hard to find. his blog is down (hea dead...), and many companies and people talked about it on his behalf to drive traffic (hi duo sec..), so you can see the internet forget, rediscover, and rewrite some history even in a few years.
I haven't used iodine, but this seems simpler. Iodine wraps requests with actual DNS requests. In this case that wasn't needed, because port 53 wasn't filtered at all. So all they needed was a simple proxy on port 53.
iodine automatically checks several modes a "simple" proxy on port 53 being one of them. If you're trying to sneak traffic through this kind of block, it is really the first tool to try.
This is repeated often and simply isn't true.