Installed Fedora KDE Plasma 42 Beta early this morning as my primary driver, and it's glorious.
The ProtonVPN Linux app is for GNOME, so it looks like I'll need to manually config that for a while since the Flatpak is not an official app and generally not recommended by Proton if you have other options—no big deal.
Now, it's time to have some fun finishing the setup and diving deeper into customization.
One thing I am immediately impressed with is the integration of KDE Connect...
"(Some) Features
• Shared clipboard: copy and paste between your phone and your computer (or any other device).
• Notification sync: Read and reply to your Android notifications from the desktop.
• Share files and URLs instantly from one device to another.
• Multimedia remote control: Use your phone as a remote for Linux media players.
• Virtual touchpad: Use your phone screen as your computer's touchpad and keyboard.
All this without wires, over the already existing Wi-Fi network, and using TLS encryption."
It naturally requires a lot of permissions to do all of this useful stuff, but it's open source and does not collect or share any data.
"KDE Connect never sends any information to KDE nor to any third party. KDE Connect sends data from one device to the other directly using the local network, never through the internet, and using end to end encryption."
https://f-droid.org/packages/org.kde.kdeconnect_tp/
#IKITAO #Linux #Tech
Is it best to download apps from the default Fedora repos or use the instructions from apps websites (I.e. mullvad & brave) to install their own app repos to download?
If the latter, how are future DNF updates handled? Will it update from the default repos or the apps repo?
Got a thinkpad on the way and will be the first time running Linux is a daily.
Congratulations on your new machine and on running Linux as your daily driver.
Best practice is to follow the install advice of the devs. Some devs only release through terminal/downloads, others prefer to release an app image for wider compatibility and OS integration, others have an official Flatpak. Some Flatpaks and Snaps have reduced functionality, others do not.
Distro repos can be slower to get updates, but it depends on the devs preferred release channels.
Sometimes there's no choice if the app isn't available for your distro but to either compile it yourself, use it in a VM running the compatible distro, or use a third-party Snap or Flatpak.
If you have to use an unofficial third-party Flatpak, then Flatseal is your friend. It helps you manage Flatpak permissions.
If you really want to dig in to a Snap or Flatpak but you can't read code, then copy the contents of the code into GPT or Claude etc and ask it to search it for malicious code from the files.
Updates will happen differently depending on how you installed the software. Traditional repository packages will update when you run system updates (like sudo dnf upgrade), but Flatpaks and Snaps have their own independent update systems.
Flatpaks update through the "flatpak update" command, while Snaps are designed to auto-update by default. Many Linux users create simple scripts that run all update commands together, or use software centers like GNOME Software or KDE Discover which can handle updating all package types through a single interface.
