• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: July 22nd, 2023

help-circle



  • That’s true. Luckily I removed Google Search Fixer from my browser this week, as I finally gave up on Google search (hopefully this time it’s permanent).

    In my opinion its results have been getting so bad (including boolean searches) in the last months that I feel that other search engines don’t provide a significantly worse experience anymore. I was unable to find content on Google that I know I found there before and where I know that it’s still on the internet, as I was able to find it with other search engines. I actually found that for example Bing gave me much more results when filtering by date range, e. g. searching for web content dated before 2005.

    Google’s web DRM project was the final straw for me to finally be serious about trying other search engines again (all my previous attempts eventually failed due to my boolean search requirement) and use as little Google services as possible. I have also tried to lower my usage of YouTube over the last couple of months by primarily subscribing to channels I know from YouTube on PeerTube and by using the Piped frontend more. Since I subscribed to YouTube channels via RSS already, it wasn’t difficult to switch the RSS feed over to PeerTube instead. ;)







  • Eh, I don’t at flatpak or snap unless I have no other choice

    I thought the same until I discovered that Flatpak gives me the power to restrict apps in their permissions, similar to firejail, but less cumbersome. Since then I actually prefer Flatpak over traditional packages (I even switched to Fedora Silverblue), as I have a global override that, for example, revokes permission to access the root of my home directory or to use the X11 display server.

    This allows me to keep a clean home directory, as applications are prevented from writing into my home directory (configuration files then automatically get stored in the Flatpak directory ~/.var instead) or, even worse, into executable files, such as ~/.bashrc. I can also be confident that applications use Wayland, if they support it, and not a less secure display server (X11). Applications that don’t support Wayland yet can either be made to run under Wayland (Chromium / Electron) or I have to grant those applications permission to actually use an X11 server (Bottles / WINE, Steam).

    On the other hand you can also opt into punching as many holes as possible into the sandbox, for example by granting applications the permission to access a local shell. That might be necessary for development tools, such as VSCodium. The thing I like about Flatpak is that it offers this kind of flexibility and you can decide on a per-application basis which system resources the application can or can not access.

    Sure, the permission model isn’t perfect (e. g. D-Bus access), but for my use-case it is a huge improvement and it gives me more flexibility with selecting my distribution, as I can get the very same up-to-date applications anywhere via Flatpak.


  • Eh, I don’t at flatpak or snap unless I have no other choice

    I thought the same until I discovered that Flatpak gives me the power to restrict apps in their permissions, similar to flatseal, but less cumbersome. Since then I actually prefer Flatpak over traditional packages (I even switched to Fedora Silverblue), as I have a global override that, for example, revokes permission to access the root of my home directory or to use the X11 display server.

    This allows me to keep a clean home directory, as applications are prevented from writing into my home directory (configuration files then automatically get stored in the Flatpak directory ~/.var instead) or, even worse, into executable files, such as ~/.bashrc. I can also be confident that applications use Wayland, if they support it, and not a less secure display server (X11). Applications that don’t support Wayland yet can either be made to run under Wayland (Chromium / Electron) or I have to grant those applications permission to actually use an X11 server (Bottles / WINE, Steam).

    On the other hand you can also opt into punching as many holes as possible into the sandbox, for example by granting applications the permission to access a local shell. That might be necessary for development tools, such as VSCodium. The thing I like about Flatpak is that it offers this kind of flexibility and you can decide on a per-application basis which system resources the application can or can not access.

    Sure, the permission model isn’t perfect (e. g. D-Bus access), but for my use-case it is a huge improvement and it gave me more flexibility with selecting my distribution, as I can get up-to-date applications anywhere via Flatpak.