Check whether your BIOS settings show the system clock UTC or adjusted to your timezone.

Windows stores hardware clock time in your local timezone. Other operating systems usually store it in UTC. If you’re dual booting, this could cause issues.

It’s also possible that saving the current time to the hardware clock in silverblue/secureblue is misonfigured in some way.

For backups, see if there’s support in rclone. You can set up encryption in rclone (crypt remote) as an overlay to other storage locations.

Once you encrypt your own backups, the privacy of the cloud storage provider doesn’t matter much. The main things to consider are price, storage capacity, and reliability.

Ubuntu Pro requires users (both individuals and enterprises) to register with Canonical to receive security updates.

Microsoft is the company that approved the software to automatically download and run as admin when a specific device is plugged in. The OEM submitted malware and Microsoft approved it. Both are at fault for letting malware download and run on your device.

In the case of vulnerabilities, MS is fully aware of this happening frequently and has announced they want to do something about it, but hasn’t actually done anything about it.

Monitors don’t need drivers. Your GPU needs drivers, and you might need color correction for your monitor.

Microslop decided that any device that is plugged in might need drivers. They allow device manufacturers to specify an arbitrary program to be downloaded and executed by Windows Update, any time a device they make is plugged in.

The difference isn’t digital vs physical. Either medium can have DRM. It’s whether you own your copy or not.

Physical DRM like the classic dial-a-pirate is owned by you. You can choose to hand someone a copy of the game and the physical DRM, and they can play it. Nobody can take that right away from you.

Online DRM will always have the flaw of someone being able to take away your rights, for any reason. Thus, you don’t own a copy of the game. Since digital games can’t have physical DRM, the only way to truly own a digital copy of a game is DRM-free.

No actually, that would be impressive. The DS is barely capable of decoding video. Getting that to work in real time, over the network, and low latency is a huge technical achievement.

This is just a text input and output connected to a remote machine.

I have a setup similar to this, but not for ddos protection. If I were to get ddossed at a network level, my home connection wouldn’t feel much of it, as my VPS quickly gets overloaded. I have been “ddossed” at an application level though, I hate AI web scrapers. Since the entire line from VPS to my home network is 1gbps, that alongside most of my server cpu resources got oversaturated with fake traffic.

(I say ddosed in quotes, because I’m not sure of the intentions of these AI webscrapers. Thousands of requests per second on a server that’s usually seeing maybe 5 isn’t “normal” traffic either.)

Since this installed a malicious dependency from NPM (and later with bunjs) in the pre install script, it would need at least complex correlation to catch. Maybe building and installing all AUR packages, which would cost far too much for the Arch team.

Individually and automatically scanning only the PKGBUILDs (the stuff actually on the AUR) would likely not have caught this.

That doesn’t mean it’s a bad idea to run a basic scan over every change, but it wouldn’t magically “fix” aur malware.

KDE Connect

This is an absolutely bottom of the barrel machine nowadays. You’ll be able to run Linux on it, but nothing is going to run “fast”. Especially not a webbrowser with modern websites.

If you’re actually considering using this machine, the two most important upgrades you can make are SSD instead of HDD, and a bit more RAM (8GB if possible). With the ~2011-2012 CPU (judging by the release date of the iGPU listed) and the mentioned upgrades, you should have a usable (although slow) workstation for light tasks. Without the upgrades, be prepared to wait for things to load.

Individual AppImages still highly depend on system libraries, I’ve seen them often fail to run on older distros, for example due to an out of date system glibc.

Flatpak is not owned by RedHat or systemd. You can use flatpak while avoiding systemd components.

a solution to a problem most people don’t have

I’d say the timeless problem of “I just want to run this app, why doesn’t it work” is solved with Flatpak. People who can compile software themselves are the exception, not the norm. For an average user, an app store that “just works” is great. And for a developer, only being required to target one common runtime simplifies things.

Hoping for another Moonlight/Sunshine moment! Already running Vaultwarden, rbw, and Keyguard. Just need a simple FOSS browser extension for autofill and editing entries.

For context, Moonlight was created first as a FOSS Nvidea gamestream client. Then Sunshine was created as a FOSS server implementation. Later, Nvidia dropped “official” support, now the two projects are a FOSS stack built atop a formerly proprietary protocol.

Writing this from my Fairphone 5 running postmarketOS (Linux).

Biggest downside right now is no phone calls, but that’s being worked on.

For me it was the inappropriate description on the last post. This is not an NSFW community and I didn’t want to read that.

The point is how expensive it is. For your 1 request, you wait 2 seconds, and the power draw is a minor inconvenience. For the massive botfarm, it adds up to days of CPU time and a significant portion of the electricity bill.

Lets ignore the “is it possible” and imagine what would happen if it was. Whatever entity forks AOSP would start off with (next to) no userbase. The platform “Android” will remain Google’s AOSP, including some proprietary components. Whenever Google decides, they can enforce apps on the Google Play Store to use a new version of the Android system API. This is often a breaking change; apps that update won’t work on older Android. There is nothing stopping Google from creating complex breaking changes that tie into their proprietary components, killing off any attempt at running Google Play Store apps on older or “fully FOSS” Android. Even if a hard fork of AOSP existed, it would not remain compatible with the vast majority of applications.

So even if this could happen, it won’t. Nobody is going to invest in hard forking a project that is going to be killed off by Google’s monopoly.

The much better (long term) option is to stay completely outside AOSP, like with mobile Linux distros such as postmarketOS. Right now, it is underdeveloped and not an option as a daily driver for most. But over time, this is the only feasible option that can give control back to the user.

Heavily leaning towards malware; normal software tends to name itself the same on disk and in ram, this seems to be it trying to hide itself.

Since there’s now nothing to go off of for how this got on your system, the best course of action is to back up your documents and reinstall your system fresh. To avoid malware in the future, stick to the built-in app store and system repositories where possible.

This doesn’t really say much; this could be legitimate software thinking it crashed, or it could be malware trying to hide itself.

Try seeing if sudo find / -type f -name windows tells you anything about where it’s installed. This command searches through / (all files) to find a file (-type f) that is named windows (the same as the process name).