In any case, North Koreans are not taught that South Korea is just like any other part of North Korea. The idea that the North Korean people and leadership are all buffoons who make the weirdest of lies possible is already Orwellian enough.
People want a lot of stuff in Firefox. However, people also seem to neatly bin all features into either "obviously necessary part of a web browser" and "obviously extraneous nonsense" when what they really mean is "things I personally want" and "things I personally don't want".
In Germany it could be computer fraud, which criminalises entering incorrect data into a computer system for financial gain. I don't know if "watching a different set of shows on Netflix" would qualify.
Sure there are examples of websites using XSLT, but so far I've only seen the dozen or maybe two dozen, and it really looks like they are extremely rare. And I'm pretty sure the EU parliament et. al. will find someone to rework their page.
This really is just a storm in a waterglass. Nothing like the hundreds or tens of thousands of flash and java applet based web pages that went defunct when we deprecated those technologies.
Those had good rationale for deprecating that I would say don't apply in this instance. Flash and Java applets were closed, insecure plugins outside the web's open standards, so removing them made sense. XSLT is a W3C standard built into the web's data and presentation layer. Dropping it means weakening the open infrastructure rather than cleaning it up.
> This really is just a storm in a waterglass. Nothing like the hundreds or tens of thousands of flash and java applet based web pages that went defunct when we deprecated those technologies.
Sure, but Flash and Java were never standards-compliant parts of the web platform. As far as I'm aware, this is the first time that something has been removed from the web platform without any replacements—Mutation Events [0] come close, but Mutation Observers are a fairly close replacement, and it took 10 years for them to be fully deprecated and removed from browsers.
They are definitely rare. And I suspect that if you eliminate government web sites where usage of standards is encouraged, if not mandated, the sightings “in the wild” are very low. My guess would be less than 1% of sites use XSLT.
If there were that many, why do people only list the same handful again and again? And where are all the /operators/ of those websites complaining? Is it possible that installing an XSLT processor on the server is not as big a hassle as everyone pretends?
Again: this is nothing like Flash or Java applets (or even ActiveX). People were seriously considering Apple's decision to not support Flash on iPhone as a strategic blunder due to the number of sites using it. Your local news station probably had video or a stock market ticker using Flash. You didn't have to hunt for examples.
> If there were that many, why do people only list the same handful again and again? And where are all the /operators/ of those websites complaining?
I've spent the last several years making a website based on XML and XSLT. I complain about the XML/XSLT deprecation from browsers all the time. And the announcements in August that Google was exploring getting rid of XSLT in the browser (which, it turned out, wasn't exploratory at all, it was a performative action that led to a foregone conclusion) was so full of blowback that the discussion got locked and Google forged ahead anyway.
> Is it possible that installing an XSLT processor on the server is not as big a hassle as everyone pretends?
This presumes that everyone interested in making something with XML and XSLT has access to configure the web server it's hosted on. With support in the browser, I can throw some static files up just about anywhere and it'll Just Work(tm)
Running a script that interprets a different script to transform a document just complicates things. What do I do when the transform fails? I have to figure out how to debug both XSLT and JavaScript to figure out what broke.
I don't have any desire to learn JavaScript (or use someone else's script) just to do some basic templating.
What does one do when transform fails right now? You have to debug both XSLT and a binary you don't have the source for; debugging JavaScript seems like a step up, right?
I used to be able to load the local XML and XSLT files in a browser and try it. When the XSLT blew up, I'd get a big ASCII arrow pointing to the part that went 'bang'. It still only kind of works in FireFox
XML Parsing Error: mismatched tag. Expected: </item>.
Location: https://example.org/rss.xml
Line Number 71, Column 3:
</channel>
--^
Chrome shows a useless white void.
I enabled the nginx XSLT module on a local web server serve the files to myself that way. Now when it fails I can check the logs to see what instruction it failed on. It's a bad experience, and I'm not arguing otherwise, but it's just about the only workaround left.
It's a circular situation: nobody wants to use XSLT because the tools are bad and nobody wants to make better tools because XSLT usage is too low.
And a WiFi connection even though it goes 'through the air' is not an airgap.
The same for BT and any other kind of connectivity.
An airgap is only an airgap if you need physical access to a device to be able to import or export bits using a physical connection, and the location of the device is secured by physical barriers. Preferably a building that is secure against non-military wannabe intruders.
> firewall exception to get to the air gapped system
Any system accessible with a firewall exception is not "air-gapped" by definition.
A level below that is diode networks, which are not air-gapped but provide much stronger system isolation than anything that is accessible with a "firewall exception".
Far below either of these is vanilla network isolation, which is what you seem to be talking about.
Definitely! I've worked on the design of these types of systems, there is more subtlety to the security models than people assume. Some of the designs in the wild have what I would consider to be notable weaknesses.
The most interesting subset of these systems are high-assurance bi-directional data paths between independent peers that are quasi-realtime. Both parties are simultaneously worried about infiltration and exfiltration. While obviously a misnomer, many people still call them diodes...
The entire domain is fascinating and less developed than you would think.
And even if you do get it right, there is always that one guy that takes a USB stick and plugs it into your carefully air-gapped systems. And cell modems are everywhere now, and so small even an expert could still overlook one, especially if it is dormant most of the time.
Yes, it is underfunded for sure. I have been underwhelmed by what academia has managed to produce, funding aside. It is a solvable problem but you have to give the money to the people that can solve it in an operational context, which rarely seems to happen.
It is a genuinely fun project for someone with sufficiently sophisticated skill but I suspect there is relatively little money in it, which colors the opportunity and outcomes.
The absence of clear commercial opportunity gives the domain a weird dynamic.
Probably. We keep watching all kind of stuff after getting baited into it. AI slob is annoying, but we do want to know what chefs do about sticky pizza dough, or what that secret in the pyramids is, or how the kid reacted to what the cat did, or (insert your guilty pleasure here).
on some platforms I try to be really good about hitting the "Never recommend this channel/page/whatever again" whenever the algo serves me the bottom-tier gutter trash videos, such as the "idiotic life hack that obviously won't work" engagement bait. It's a small drop in the ocean, but at least that one channel will never be served to me again.
Replaced them with App stores, why one code base when you can have N code bases: web sites, ios, android , tv …
cheaper, privacy-oriented and more secure lol obviously not, doesn’t help the consumer or the developer.
Xslt is brilliant at transforming raw data, a tree or table for example, without having to install Office apps or paying a number of providers to simply view it without massive disruption loops.
This would need to be tested. There's a lot going on already during normal take-offs. Now you're in a situation where the engine fire alarm is going off, probably a few other alarms, you got so many messages on your display that it only shows the most urgent one, you're taking quick glances at 50 points in the cockpit already.
And how would the cameras even work? Are the pilots supposed to switch between multiple camera feeds, or do we install dozens of screens? And then what, they see lots of black smoke on one camera, does that really tell them that much more than the ENG FIRE alert blaring in the background?
Maybe this could help during stable flight, but in this situation, when the pilots were likely already overloaded and probably had only a few seconds to escape this situation - if it was possible at all - I can't imagine it being helpful.
You know how the tail camera works on the new planes? Something like that, which can be far away from the wings, but get the full picture. Am I saying it's the solution for everything? No. But after you go through the memory committed items during an emergency, you can take a look outside and be like "ah, I see better what the problem is".
If we don't try to see how it goes, we won't know if it is a good idea or not.
It'd certainly need more thought put into it than just showing the camera view from the entertainment system. Either just one camera on the tail pointed forwards, so you have one single camera that can show the whole plane, or two cameras in the front, one pointed at each wing. Two cameras is worse than one, but they are less likely to be affected by smoke or blood splatters or whatever. Maybe give each pilot one of the camera feeds. And you'd have to fit a dedicated screen for the video feed so pilots don't need to switch through screens in an emergency.
It'd take lots of testing and engineering. But especially in cases where you have multiple warnings going off I imagine that a quick view at an exterior camera can often give you a clearer/faster indication of the situation
reply