Is there a reason a capability has to be covered by only a single permission? Why not have one accessibility permission that covers all that and then a bunch of individual permissions for non-accessibility apps?
It depends on the process. Argon/CO2 is used for MIG welding, while TIG generally uses pure argon. In some situations that justify the expense, helium is used instead as it allows deeper weld penetration.
I'm working on Lightningbeam (https://lightningbeam.org), an integrated multimedia editor. It's inspired mainly by Macromedia Flash, Apple GarageBand, and Kdenlive. It combines animation, audio and video editing into a single timeline. It's cross-platform, running natively on Linux, macOS and Windows.
I'm currently rewriting the UI in Rust - previously it had a Rust backend and a JS frontend using Tauri, but I ran into bandwidth limitations which prevented it from being really usable as a video editor. It's currently in early alpha.
Doesn't seem to work for me - tried in both Firefox and Chromium and I can see the waveform when I talk but the transcription just shows "Awaiting audio input".
Location: New York
Remote: Yes
Willing to relocate: No
Technologies: Python, TypeScript/Javascript, Rust, Linux
Resume: https://skyler.io/resume.pdf
Email: skyler at skyler dot io
If so, then finding the redacted string would be similar to trying to brute-force a hash (though presumably slower, since text layout algorithms are probably more complex than a single hash invocation).
Location: New York
Remote: Yes
Willing to relocate: No
Technologies: Python, TypeScript/Javascript, Rust, Linux
Resume: https://skyler.io/resume.pdf
Email: skyler at skyler dot io
It would be nice if this told you upfront how many questions there were - after sixteen with nothing changing I figured it was probably endless but apparently there are twenty?
The only reason I use Wayland is display scaling - with a high DPI screen, many apps are blurry or inconsistently scaled under X11. Given the parade of other issues Wayland brings, I wish the development effort were instead spent on improving highDPI support in X11.
Starting at an initial density of air, suppose you descend a distance D such that the air density doubles. Now your air is twice as dense, which doubles the pressure underneath it, meaning if you descend a further D the density will double again. Continue ad infinitum (or at least until the ideal gas law stops being a good approximation).
Gravity changes little over that distance - it's more because of the compounding effect of atmospheric pressure (the deeper you go, the more air you have above you which raises the pressure, raising the density and meaning that pressure increases exponentially faster).
An interesting corollary of this is that if you only have a single sample, it reduces to indicating that your sample is the median value - i.e. if you see one item with serial number N, you can guess that there were roughly 2N produced.
My understanding is that coal/nuclear/gas plants provide a certain amount of stability thanks to the rotational inertia in the turbines. It seems like a relatively inexpensive way to retain that capacity would be to keep the old turbines to function essentially as flywheels, to stabilize the grid, after the plants powering them are shut down.
It sounds like a pitch that you might hear from an airplane propeller, which leads to the question why airsickness exists if the antidote is ambiently present?
They do have accelerometers as well as gyroscopes, so technically they could integrate acceleration twice to keep track of position...but in practice it's way more reliable to just keep it at a constant distance from the head.
Theoretically you could do this in Linux by calling /usr/bin/sl or whatever - but since various distros put binaries in different places, that would probably cause more problems than it could solve.