As long as AI is advertised as being a unique selling point, I'm not interested.
If you think of specific problems it is better to point them out and try think of solutions, not reject the technology as a whole.
Yes. There a problems with the Gnome desktop environment. Without looking at the issue tracker, I can assure you that AI is not the solution to any of them. Even if AI may be a possible solution to a problem, it would probably not be the best one.
Adding to what other people said, I want to suggest using the Blue Oak Model License. It is comparable to the MIT license (so no copyleft) but much more readable and easier to understand.
The Typst compiler is available under the Apache License 2.0.
The web app at https://typst.app is proprietary but also completely optional. You can use Typst with only a text editor supporting the LSP (VSCodium, Kate, Atom, ...), typst-lsp (Apache-2.0 OR MIT) and the Typst compiler.
Actually, most of the guests are VMs (instead of LXCs) because many services I host are most easily deployed via Docker Compose and Docker in LXCs requires workarounds I don't fully understand thr implications of.
Great technology is invisible.
As long as AI is advertised as being a unique selling point, I'm not interested.
Yes. There a problems with the Gnome desktop environment. Without looking at the issue tracker, I can assure you that AI is not the solution to any of them. Even if AI may be a possible solution to a problem, it would probably not be the best one.
There's Protectli, which, while I do not know where they produce, is a german company.
fre:ac is pretty similiar to EAC.
I'm pretty sure it isn't.
Adding to what other people said, I want to suggest using the Blue Oak Model License. It is comparable to the MIT license (so no copyleft) but much more readable and easier to understand.
The Typst compiler is available under the Apache License 2.0.
The web app at https://typst.app is proprietary but also completely optional. You can use Typst with only a text editor supporting the LSP (VSCodium, Kate, Atom, ...), typst-lsp (Apache-2.0 OR MIT) and the Typst compiler.
Because it's free for the time being.
Depending on what you're trying to do, Node-RED might be an option.
For maps, there is already OpenStreetMap and its ecosystem. I particularly like OrganicMaps which is available for Android, iOS and Linux (beta).
It’s even abbreviated that way in the official documentation: https://nginxproxymanager.com/advanced-config/
To throw in another alternative to SSH tunnels and WireGuard: rathole
The screenshot looks awesome! I'm currently on vacation and will definitely try it out.
From the ESPHome documentation:
There is Fountain which is basically Markdown for screenwriting.
They have a list of apps supporting the format: https://fountain.io/apps/
With Compose apps I actually never had this problems yet.
I always recognize Flutter apps on Android as being non-native and avoid them because of this.
I think it is because they seem to never use the system font but Quicksand instead and all the animations feel slightly off.
Other people already answered the question, I just want to say that this question was incredibly well asked.
Danke, ich denke, ich verstehe jetzt, was du meinst.
Ich verstehe nicht, inwiefern die zweite Hälfte deines Kommentars meine Frage beantwortet.
Actually, most of the guests are VMs (instead of LXCs) because many services I host are most easily deployed via Docker Compose and Docker in LXCs requires workarounds I don't fully understand thr implications of.