The solution is to get open source into schools early. Idk how tech education is across the EU, but here in the US kids are usually introduced to computers as early as elementary school (but I think today they might be using ipads or chromebooks instead). In my highschool, we were required to get Microsoft office certification before we'd even be allowed to graduate, which pissed me off even back then.
entwine
What's wrong with it? I haven't watched the new season (yet?), but I enjoyed the parts I did watch. It's no game of thrones, but it's very entertaining.
I think this is an unrealistic concern. If that happened, every single person fired will sue the federal government for first amendment violation in addition to other things a real lawyer could probably point out. It'd be like the Kimmel situation x100, and remember that even some prominent Republicans pushed back against that.
Matrix is a bit of a dumpster fire with a good idea, terrible execution. There was a blog post recently by someone pointing out all the problems, but don't have the link.
I would avoid it.
Signal is centralized, on the Signal foundation. It went down because Signal put all their eggs in one basket (data center). This is a (arguably) reasonable and common business decision/practice, and there's no way to predict outages. However, all users of the Signal app are at the mercy of these business decisions made by the Signal foundation. Whether or not Signal is using a distributed architecture internally is irrelevant.
Compare Signal to Delta Chat, which uses standard Email servers as well as custom optimized chat relays to implement the chat network. That is truly decentralized. It doesn't matter if all of AWS goes down, delta chat users will still be able to communicate using other email servers.
Everyone involved in this is not a good person (incl the streamer), but for the purposes of public safety, has anyone identified the individual that did it? Was he at least arrested? You don't do something like this without being dangerously fucked in the head.
Wtf is clash verge? Just use wireguard directly. Set it up in the KDE network manager app and it'll automatically apply to all software on the system
Most light themes I've encountered don't seem to grasp the concept of 'contrast'. I bet if you were to survey light theme users, you'd find that most of them have nonstandard/weird settings on their monitors. Chrome dev tools, Xcode, and Visual Studio's light themes are all great though, as they have proper contrast and don't look like rainbow vomit.
But one other issue with light themes is that for some people (myself included), it makes 'eye floaters' stand out more. I'm fortunate that my case isn't terrible, but I can see it being a serious problem for some people, especially older developers.
You can, and should do that. Here's what that looks like: toolbox run -c <toolbox-name> <command>
All of my development tools are in a toolbox, including my IDE (Sublime Text). I created a standard .desktop file so that I can launch it like any other application, and it works perfectly, with a proper Icon and everything. Example:
[Desktop Entry]
Version=1.0
Type=Application
Name=Sublime Text
GenericName=Text Editor
Comment=Sophisticated text editor for code, markup and prose
Exec=/usr/bin/toolbox run -c devel /opt/sublime_text/sublime_text %F
Terminal=false
MimeType=text/plain;
Icon=/home/user/.local/share/applications/SublimeText.png
Categories=TextEditor;Development;
StartupNotify=true
StartupWMClass=sublime_text
To run something on the host from inside a toolbox, you can use flatpak-spawn:
$ toolbox enter ...
$ flatpak-spawn --host <command> <args>
You can even use that to (awkwardly) run something in another toolbox using the same command above:
flatpak-spawn --host toolbox run -c <other-container> <command>
Sublime text specifically has support for custom build commands. Sometimes, I'm using it to develop something in a different toolbox than the one sublime is installed in. So in my custom build script for the project, I add a check to enter the correct toolbox before executing the build. Here's what that looks like:
TARGET_TOOLBOX=example
source /run/.containerenv
if [ "$name" != "${TARGET_TOOLBOX}" ]; then
echo "SWITCHING CONTAINER $0 $@";
flatpak-spawn --host toolbox run --container ${TARGET_TOOLBOX} /usr/bin/env zsh -c "$0 $@";
exit 0;
fi
#proceed with build...
This container/toolbox workflow is far superior to anything else, as it makes it trivial to quickly test whether your code works on a different distros/versions. It all just works with your existing tooling/local workflows once you learn how to work with the tools. There really is nothing you can't do.
...and that's for development, which is the most difficult scenario for this type of thing. For regular every day users, immutability just works without requiring people to learn anything new besides reaching for flatpak instead of apt/dnf/pacman/etc.
Wtf is þ and why is it invading your comment?
Audio on Linux, like all things, is a deep deep rabbit hole. Whatever you want to do, you can. Whether it'll be easy, or accessible through a GUI, or if you'll have to write your own scripts, who knows. Everything is on the table.
The best way to get answers is to ask directly in the community for your chosen distro. A lot of people just lazily post in generic linux/tech communities, like /r/linux on reddit, and get lazy replies from people who don't know, but feel compelled to post anyway. Don't do that.
You can write a python script that procedurally generates email addresses for a given domain, tries emailing them, and if the server doesn't return an error saying the account doesn't exist, add it to the database.
It may take a couple of centuries/millenia, and you might have to deal with anti spam measures, but you'll save $165/mo