What if in addition to Slack, you also want Discord, Visual Studio Code, Signal Desktop, and Spotify? Should you install all of this in your template even if you only need these apps in a single qube? But this means you'll also have Slack installed in every other qube that's based on fedora-34, and you might not want this. If you have a work qube that's based on fedora-34 and you want to install Slack in it, you need to first install Slack in the fedora-34 template, and then you'll be able to run it in work. Each qube is based on either a Fedora or Debian template. It's a simple graphical wrapper around flatpak that lets you install, run, and update apps inside a single qube, giving you easy access to everything available in the Linux app store Flathub, and installing it all in your private storage so you don't need to constantly fiddle with your templates. Now that I'm back on Qubes, I decided to write a little utility called Qube Apps that helps make it a little less cumbersome. In Qubes, I could do this in a disposable, networkless qube so that if it did try to hack me it wouldn't have access to any of my data, or even the internet. Was it just a glitch, or did I just get hacked? Ugh, this is why I should be using Qubes. One of them was in a strange format I wasn't familiar with, but I found an open source tool that could load the document, so I installed that and then opened it. I downloaded documents from an anonymous person on the internet that I was interested in looking at. Qubes is great, but it can be cumbersome to use.īut then I did something silly. I have a Qubes laptop that I use for specific high security tasks, but my daily driver the last few months has been Ubuntu or Pop!_OS (I really like the tiling windows and the design), and sometimes macOS. I really like Qubes but I haven't been using it a lot lately. Qube Apps: a Flatpak-based app store for each qube
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |