First, this would be a better question to ask in a Linux specific community.
Second, Build time is really subjective to the computer and its hardware. There could be bottlenecks at the cpu/memory from the motherboard that will slow it down. It also depends on whether you’re spinning rust or using an ssd.
There are a lot of factors involved in the whole that makes it hard to definitively say how long something takes to build.
Pretty much the only time we need passports is if we travel outside the U.S. and territories. Those that take cruises or cross borders to other countries would, but generally speaking a majority of Americans don’t have passports.
Money for the most part for a lot of people.
Passports are $400+ USD, then there are the plane tickets, which are hundreds of dollars. Then to top it off you need to have room and board while looking for a job and someplace to live.
Another thing I’ve heard is fear of leaving the known and family.
Right now better than half or government doesn’t know how to govern. They are too busy fighting among themselves and imploding thanks to MAGA.
Walking or asking a friend if they have time, usually at a cost of some gas.
You’re right, it is probably an anti-privacy thing. God forbid they can’t do the telemetry and other nefarious that they do
This is just another attempt by Micro$uck to make everyone use their email services. Micro$uck doesn’t want any competition, they want to rule the computer world
Awesome thanks
I would love to have that wallpaper
One thing to look at is you are self-hosting on a local tower turned server.
If you are using a hosting provider, most of them offer domain name registration through their company.
It’s a KWin scrip called Autocompose. Does endeavour ship it by default?
Endeavour installs a mostly default DE when you make your choice of which one to use, so most of the DE’s come as packaged by the devs. If I’m not mistaken Autocompose is a default script included with KDE.
I say mostly, because some parts of the DE you use is incompatible with the Arch ecosystem and disabled by default. For example, Discover on KDE is pretty much unusable on arch/EndeavourOS because the repos aren’t adequately designed for such a setup.
So do snaps and flatpacks. And they are still consider containerized / sandboxed. Appimages are the predecessors to snap and flatpack. The only difference is unlike Appimages they got it right for the most part.
Generally speaking the Appimages integrate with KDE better than all the other DE’s. The codes for Appimages are still containerized from the OS in general as defined in my last post.
Unlike snaps and flatpaks, Appimages aren’t containerized or sandboxed at all. They are only used to bundle (some) dependencies, so you don’t need to rely on packages provided by your distro’s package manager.
You might want to look up what Appimages are as well as what containerization is. To help I have found the following.
AppImage aims to be an application deployment system for Linux with the following objectives: simplicity, binary compatibility, portability, distro agnosticism, no installation, no root permission, and keeping the underlying operating system untouched.
As stated Appimages are containerized/sandboxed as it prevents needing to install any files on the OS.
Containerized applications are applications run in isolated packages of code called containers. Containers include all the dependencies that an application might need to run on any host operating system, such as libraries, binaries, configuration files, and frameworks, into a single lightweight executable.
Source: https://cloud.google.com/discover/what-are-containerized-applications
As you can see, once again, your info is incorrect as this is another example of what Appimages are.
The thing about snaps and app image is they are containerized. The idea behind that is to help keep the apps separate from the main file subsystem by sandboxing them from each other as well as not cluttering your hdd with different versions of the same libraries to make them work.
Because of the sandboxing, once you close the app it stops running in the background therefore there is nothing to get notifications from.
IMHO, this is why snap and app image programs are not advisable for programs you may need notifications from on a, generally, required/needed basis.
As for superconductivity, the only way around that problem is to download from source, compile it and let it run natively on your system in the background, or add it to you auto startup list so it is running at boot time.
Nothing wrong with that. When I see a re-post from X/twitter, or whatever he wants to name it in the future, I happily scroll right by it.
I say let him go bankrupt trying to save it.
Well he is helping it along with the latest talking point that he is going to make X a subscription only platform, aka you must pay to play.
I dropped it when trump was spewing his bs on it. My feed was 90% Trump bs and re-posts. I actively dumped fb, twitter and a few others back in 2019 and My life has been so much better since then.
Like he cares. He bought it for money and political reasons. And now, because of piss poor decisions, the company has been devalued from $44 billion it is now only worth about $4 billion. What makes it so sad is a lot of online companies are following suit thinking they can do what he couldn’t.
You do realize that X is now it’s official name right? Elon changed the name to X and deprecated the twitter name. At the end of the domain registration, he is not going to re-register twitter.com as the domain name, and because he owns the trademark on it, he is going to sue anyone who tries to re-use the domain name.
I don’t know about gnome, but on KDE you can disable touch support under settings>mouse & touchpad.