Oh yeah, there's no shortage of reasons not to use SF6. Even in conventional waveguides, as far as I know most designs these days prefer nitrogen or dried atmospheric air.
You don't need a significant flow of argon, just enough to keep unwanted gasses out of the waveguide.
It's possible there exists a material that is transparent to mm waves, airtight, and can survive the conditions at the bottom of the hole. In such a case they could cap the waveguide and prevent any gas leakage.
I'm quite sure Quaise is well aware that Argon isn't cheap and are already exploring multiple avenues for reducing its usage.
It is interesting that they have to use Argon instead of the more typical Nitrogen or SF6. A waveguide with such a significant pressure differential is decidedly unusual and a unique challenger for what they are doing.
Nobody is questioning the value of unconstrained mass surveillance on solving crimes.
Unfortunately it also enables a good deal of more heinous crimes against the people its supposed to protect, by the people who are supposed to be protecting them.
The user wants the website to work in IE6, developing and testing only against IE6 to the detriment of other browsers is not generally regarded as a healthy state of affairs.
The standard exists, it is the responsibility of both the producer and consumer of ePUB files to adhere to the standard.
Yes, for the ones I've owned rooting is very easy. KOReader and Plato are both popular (amongst the community of eReader rooting people) alternatives to the OEM software.
I feel like building an nLab would be a far more valuable learning experience then using one.
The caveat being not just as a DIY soldering kit but as a full "course" in the design and construction of it.
Its got a power supply, an MCU, analog I/O, digital I/O. Learning the theory of how to read a 100kHz analog signal is far more valuable then a device that can read a 100 kHz signal.
They're presenting it as a "intro to electronics" device. I think they've missed though, as far as I'm concerned, learning to build a "nLab" equivalent device from a bare AVR MCU would be a far more informative and useful introduction then yet another "Babies First blink.c" kit.
Even worse, a fully formed lesson plan, parts, and prerecorded lessons could actually be worth $200. Unlike this widget, which is not worth half that.
The spec page says 100 kHz BW on the oscilloscope, the FAQ says 400 kHz. In either case calling it an "oscilloscope" is a stretch, its the ADC channels on an MCU.
I find it curious that all their promo shots seem to only show the back of the board. I couldnt find any of the component side, or any information about what components are used. My guess would be:
- a very small dual rail supply
- AVR or STM MCU
- Signal generator is PWM through an RC low pass filter
- Oscilloscope is potentially just the input through a resistor network to shift +/- 5V to 0-5V, maybe a buffer to keep input impedance high.
I just don't see $170-200 of value here, or anything close to that.
A company operating above board would be sure to carefully document the state of the rental before and after whatever work they were doing. Any tradesperson/installer/technician/repair person will have tales of how they were accused of stealing grandmas wedding ring from the bottom of the sock drawer while repairing a leak in the kitchen.
So either Bot Company damaged property and is trying to pretend they didn't. Or they are incompetent and failed to document the state of the property or handle the owners complaints appropriately.
Given that their training robots and would therefore be collecting as much data as possible, including camera data, I'm leaning towards malice instead of ignorance.
You are technically correct, the best kind of correct. However! That would be a terrible UX/UI experience. While showing distances on a linear scale is accurate, it fails to capture all the information a person in an interstellar ship may wish to see.
Something like logarithmic distances would better capture information like "Am I about to crash into the star or enter a nice orbit" while still showing the full picture of where you are in relation to where you're going and where you came from.
No idea of that's what happened here, just a thought, I'm not an expert in starship computer interface design.
For something like a transfer between Starships you can resolve a lot of those problems by (very) gently spinning the 2 craft. It won't take much force for the liquids to settle at the bottom of their respective tanks where you would presumably put the intakes.
Assuming you are talking about real physical dice and not an imaginary function that generates perfectly random die rolls.
They are actually pretty poor random number generators. For starters, dice are chaotic, not random, the outcome is based entirely on initial conditions. For humans rolling dice, the space of initial conditions can become surprisingly constrained, especially if the human wants to achieve specific outcomes.
Alice runs many services and has a rather large attack surface. I don't want Alice to persist those secrets, only to have them briefly at startup (think joining tokens). Bob however has exactly one job, verify that Alice-1 to Alice-N are in a trusted configuration before granting them access to the cluster.
Very recent events in the Linux kernel prove that it isn't safe to assume "0600 root:root" is sufficient to protect secrets from a misbehaving container.
Sadly, the problem isn't the TPM or Remote Attestation. It's Google et al choosing to only talk to devices and software they like without concern for what the user wants or trusts. Compounded by everyone else just going along with it.
A TPM where the device owner can't take ownership of the root key is worse then no TPM at all.