You can have an air gap between two physical items - it doesn't matter if those physical items are air tight or not. Air gapped doesn't mean the items are prohibited to intake air (i.e. air tight), it just means they're prohibited to intake things _apart_ from air.
Historically, we did not have wifi and other radio based new fangled data communications. Data connectivity required wires, physical connections. If there was a gap between the two devices that had no wire, just air, that was air gapped. No comms could happen between the two. It is physically isolated. it used to be called "physically isolated" when we used it in the 80's (?). Some say, we stole it from plumbers but that is hogwash (pun intended, you know the backflow prevention thing). I vaguely recall start seeing it late 1990's to 2K in the public?
Mission Impossible 1996 the computer in the room where tom cruise is lowered into the room. That was an example of 90's air-gapped system.
The name stuck because it sounds cool. In my opinion, there is no such thing as true "air-gapped network" any more. There are too many ways to snoop on systems that are isolated, without "physical" and radio connections in the traditional sense (e.g., listen to the "electricity", sounds, power fluctuation, ground vibration, squirrel squeeks).
Airgapped systems have an air gap between the system and the wider world. The only way to move data to and from them is for someone to walk across the gap with physical media.
There are no communication cables between the host system and the wider world.
* air-gap malware can be designed to communicate secure information acoustically, at frequencies near or beyond the limit of human hearing.
* In 2014, researchers introduced ″AirHopper″, a bifurcated attack pattern showing the feasibility of data exfiltration from an isolated computer to a nearby mobile phone, using FM frequency signals.
* In 2015, "HELLONE", a covert signaling channel between air-gapped computers using thermal manipulations, was introduced. "BitWhisper" supports bidirectional communication and requires no additional dedicated peripheral hardware.
* Later in 2015, researchers introduced "GSMem", a method for exfiltrating data from air-gapped computers over cellular frequencies. The transmission - generated by a standard internal bus - renders the computer into a small cellular transmitter antenna.
The site is up now as far as I can tell. We were doing some updates a couple of hours ago which might have been when you tried it. Please have another go.
Just looked through the list. Some of them are sort of interesting, but they seem to be on the extreme - either its a large open source projects like PyTorch etc., or .. its a hobby android app.
Not yet. I'm writing it because of a new 7800 cartridge type somebody is working on and that work needs an emulator. I'm waiting for him to complete his half of the project before releasing it. If I release it now, it'll let the cat-out-of-the-bag too soon :-)
I have a fully working 2600 emulator that's publicly available. That'll give you an idea of what I'm aiming for. https://github.com/JetSetIlly/Gopher2600 Because the 2600 and 7800 are so similar, I plan to merge the two projects together in the future.
Much of it is usual stack. React, TypeScript, tailwind, d3 for viz, vite for packaging, sqlite for storage, Evolu for schema & sync, firebase for auth, and may react libraries. There is a small sync server (which handles synching of encrypted data), but apart from that, rest of it is front-end code.
Something is always on to handle power button, tender battery, as well as USB. NFC payment has to be compartmentalized for security, as a tangential.
At that point you might as well fuse those features into one companion computer and let it handle NFC payments under certain conditions, so people can take a safe ride home with a dead phone.
completely correct, but I dont think thats where OP is coming from or what the article intends to suggest either. Its recommending that you try multiple things, get a feel for whats technically feasible & if it looks interesting to the customer and push that forward. Its very well applicable to indie devs & also applicable to large companies to some extent. This philosophy is great to identify the feature/product you want to spend meaningful time on.
In fact, one could wager that the situation you described is directly a consequence of not adhering to what OP is suggesting.
