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

help-circle

  • I’ve had no problems with the Discord flatpak and updates. I use a KDE variant of UBlue and the package manager prompts me to update all flatpaks when I start the computer (whenever there are updates available), which I do with one click.

    For a new user, i would think that individually managing package updates is probably not a desired workflow.




  • You’re getting a lot of flack in these comments, but you are absolutely right. All the concerns people have raised about “AI” and the recent wave of machine learning tech are (mostly) valid, but that doesn’t mean AI isn’t incredibly effective in certain use cases. Rather than hating on the technology or ignoring it, the FOSS community should try to find ways of implementing AI that mitigate the problems, while continuing to educate users about the limitations of LLMs, etc.





  • Maybe I’m misunderstanding this, but their FAQ specifically says:

    By default, your documents are stored inside the docker volume paperless_media. Docker manages this volume automatically for you.

    It also says that documents are removed from the consumption directory, renamed, and put into a folder that you shouldn’t modify.

    And that’s my problem with the project. I want to be able to keep my file name and organizational structure.






  • Thanks for the additional reading and information. Maybe it’s just me, but I feel like I hear about a security vulnerability in “processor microcode” or packages or other software basically every day. As a relatively non-technical user, it’s always very difficult to tell how much these things actually matter for normal users. Flatpaks are incredibly convenient because they “just work” and are easily compatible with immutable distributions. For better or worse, I suspect many people are not going to be dissuaded from using them by hypothetical/abstract security risks.



  • It’s hard to explain until you’ve used it, but in my experience I think this is much different than a traditional Linux distro. Every other distro I’ve tried has (to some extent) dependencies that can get out of whack, configuration drift that makes it hard to get things to work sometimes, random codecs or drivers or other things you need to install to get a system working as it should, etc. In the “cloud native” model, all the packages, drivers, etc. are built and tested in the cloud. So when they arrive on your machine, they “just work” and updates are handled automatically - it’s great. Maybe not great for tinkerers, but great for regular users who just want to use their computer.