• 10 Posts
  • 316 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2024

help-circle



  • Alk@sh.itjust.workstoPop!_OS (Linux)@lemmy.worldFlatpak Issues
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    2
    ·
    edit-2
    13 hours ago

    I’ve never had an issue with flatpak. But if you do I recommend installing flatseal which can manage permissions for any flatpak app and give extra permissions if some are missing by default.

    Keep using flatpak. Pop OS Deb packages are often updated slowly or just out of date permanently, and flatpak are very rarely out of date. (see lutris for my latest example)

    It’s good to sandbox apps. Not every app needs that much access to your system, it’s great for privacy and security.

    I also don’t use the pop shop anymore. It’s slow and bloated. I just use the flatpak or apt commands. Very simple and quick.


  • you can assign independent applications > I know you can do this in windows without needing an extra sound controller it’s in ‘Settings>system>Sound>Volume Mixer’

    Yeah, but separate physical controls are beneficial when you have full-screen apps, are busy, don’t want to lose your place, or if you need to do it more frequently and quickly than the sound mixer allows.

    Linux largely has this too, but in both OS’s it’s less convenient than reaching over and quickly pressing a button or sliding a slider in many scenarios.

    Of course if you just need to edit these infrequently then that’s a perfectly good solution and there’s no reason to spend any money at all.





  • If you have a desktop and not a laptop, it’s always a great idea to get a separate sound controller. Either a dac/amp for nice headphones, volume controls on a wireless headset, or even buy a sound mixer like the rodecaster duo so you can assign independent applications to each physical slider on the mixer. I do that last one and it’s such a quality of life improvement if you use your PC a lot.

    All of these options can’t be seen from Spotify.






  • Yeah that’s a good point. The joke is mostly for my own enjoyment or any random user who happens to forget the jellyfin. subdomain.

    I have had a few hits to /wp-admin, but cloudflare actually blocks those for me (I don’t use a tunnel but I do use them for the domain name which helps a bit). I might just shut down the main page then.


  • While technically not strictly necessary, it adds more robust authentication methods, and makes it easier to build out other apps if you want to in the future without having to re-do the sign-in process for all of your users. You can have things like 2fa and other things that make it harder for bots to get in and easier for users to stay in. It also makes it easier to keep track of login attempts and notice compromised accounts.

    Edit: There are also alternatives like authelia that may be easier to implement. I don’t really trust most web apps to be ultra secure with internet-facing sign-in pages so it just feels like “good practice” to hide behind an auth service whose sole purpose is to be written and built securely. Plus once you learn how to set up fail2ban with an auth service, there will be no need to re-learn or re-implement it if you add a 2nd app/service. Very modular and makes testing and adding new things much easier.

    Another benefit is that it has a nice GUI. I can look at logins, add services, stuff like that without touching config files which will be nice for those who don’t like wading through text files to change config.