• 1 Post
  • 33 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • I’ve been using WinBTRFS for quite some time without issues. It seems a lot of people recommend NTFS. But be aware, if you plan on using it for things like games, NTFS will absolutely break at some point. It is not compatible with Proton and will break things like updates for Steam. It always has for me up until very recently. Valve also says the same about using NTFS for games. I’m not sure this can be fixed with the NTFS driver unless they do workarounds like renaming things automatically because some things Proton does are not compatible with the filesystem spec.










  • Just to clarify, I use Pop!_OS and not Fedora Ublue. I looked at their Wiki because they are the only ones who had documentation on how they made hw accel work with Flatpak and Nvidia specifically. More exaclty I was led there by this Reddit post.

    AFAIK it should work fine with AMD since Firefox can use the VA-API FFmpeg Flatpak to provide hw accel which should work fine with AMD GPUs. This does however not support Nvidia GPUs, which is why you have to expose the driver in the sandbox and force Firefox to try to use it etc.


  • Mesa drivers for opengl, vulkan, etc. are likely already installed, what you need to install are the mesa-va and mesa-vdpau drivers for video acceleration. Other than that, you just need to make sure the GPU doesn’t stay in power saving mode when you play.

    Thanks, I’ll make sure to install those for sure then.

    Btw, video acceleration with Nvidia mostly works if you use this.

    You know, I actually tried, and I couldn’t get hardware acceleration working in the Firefox Flatpak for the love of god. I tried everything, all the guides, looked at the Ublue documentation how they did it etc. and in the end I decided it’s just not worth it because playback worked fine without, just with a wee bit higher CPU usage.




  • I reported basically this issue a few months back with another Lenovo device. Sadly there was no other activity towards resolving this.

    Maybe you can bring in some new information if you can confirm, that you have the same issue.

    In essence the hover recognition distance greatly reduces when touch input is present causing these jumps to happen with the palm because when writing any lifting off the pen will reactivate touch.


  • I don‘t think you understand my point. Let me be a bit more high level. It’s not about the three major outages WhatsApp had this year for like 30 mins. or whatever.

    A perfectly set up Matrix server with more than enough resources allocated has issues decrypting messages when there’s a few hundred people and that’s without federation. This is still happening to today, fully updated server and clients.

    As I said, I know they are working with a lot less resources than Meta. But at the moment the implementation doesn’t even do the most basic thing, deliver messages reliably. I know their new encryption library is supposed to do a better job but it’s just the cold hard truth that it’s not up there with the big messengers yet. Denying that doesn’t do the project any good.


  • Matrix does definitely not have the same reliability as WhatsApp or Signal. I’ve used it for around 3 years now with a group of tech savvy friends.

    It’s still a regular occurrence that we get cannot decrypt errors, sometimes the app doesn’t show new messages in the chat but they are visible in the preview, also the app can be soooo slow.

    Also, I know it’s not user error. If you check the Matrix development and follow their blog posts they already acknowledged the issues and are working on fixes. But for now it’s just wishful thinking when one calls them reliable alternatives for mainstream use. I’m not hating and will keep using the project because I truly think they are doing amazing work.