I second that about Nvidia GPUs. While Linux hardware support is really good, there is plenty of common, mainstream hardware that never was and never will be supported by Linux, usually due to uncooperative manufacturers. For Nvidia, their non-free driver is terrible and the nouveau driver in Linux is hit-or-miss. (Note, many people use either of those successfully, but the likelihood of success drops rapidly with any of: multiple displays, the need to dynamically change outputs, multi-GPU Optimus hardware or even laptops in general, and fully functional hardware acceleration.)
Dude, you don't just pump the combustion result through your house.
I wrote "LPG or natural gas could certainly contribute to humidity levels in some cases," and was thinking specifically of non-vented gas heaters, which are very common in my experience, and are in some cases used for whole-house heating where there isn't a central air circulation system. In this case, the combustion result is literally released into the house.
While this thread is about gas heating, the article is about gas cooking stoves, which in most cases can be vented only at most very poorly (with a range hood), so the risk being dicussed is literally a result of releasing the combustion result into your house.
I believe hydrocarbon fuels produce water (vapor) as a combustion byproduct, so LPG or natural gas could certainly contribute to humidity levels in some cases.
There may also be a separate effect by which the heat strips in an electric furnace dry out the air versus the heat exchanger in a gas furnace, but I don't know about that.
By not using it.
Seriously though, F-Droid (a Play Store alternative) has a lot of nice apps.
[Can] a patch can kind of be like a hook?
In the free software world, a patch usually describes a file that lists lines to be added to or removed from another file (or multiple files). The most common use for this is probably with actual source code.
Binary (non-text) patches are also possible, and in Windows a software bug-fix "patch" would likely be mostly binary. In the free software world, it's uncommon to use binary patches for updates; instead the source is patched (either in the main upstream project or by a distribution) and a new binary package is built and published.
Where you create a config file that has symlinks to all the executables like you mentioned?
I don't really understand how those two questions relate, so I may not be able to give you a good answer. Often a configuration file has a variable=value
structure, but it would certainly possible to have a list of file paths in a configuration. However, this might instead be implemented as an actual directory (like ~/.config/app/pre-hook.d/
) where each executable file in that directory is executed by the "pre" hook in the app. (Configuration directories often work very similarly also.)
Whether the paths are symlinks is likely to be irrelevant, as this is more a filesystem level feature that would often be ignored entirely by the application.
I hope this is helpful.
From the README at the current published commit:
The current focus is on implementing next-word suggestions, which has become complicated/hit a snag and is taking more time than originally planned. Updates will come when this issue is resolved. Thank you for being patient.
Prior to this, releases occurred quite regularly.
Thanks for posting the GitHub link.
Yes, and it is very annoying. ~~However it does not seem to be happening now with Jerboa 0.0.42.~~
Edit: This is still happening for me too, as of Jerboa 0.0.42, with the AOSP keyboard. It does not happen in any other apps.
I recommend using Molly instead if you need to communicate with Signal users. Note, the Molly-FOSS flavor excludes proprietary Google libraries entirely.
If you are interested in trying an alternative that is unrelated to Signal, I suggest looking at SimpleX Chat.
Just FYI, Signal (Open Whisper Systems) is not FOSS-friendly. The server-side software is not open source, they refuse to federate with other Signal implementations, and they are unfriendly to forks. See:
Codeberg is one option. I think they run Forgejo.