• 0 Posts
  • 13 Comments
Joined 4 months ago
cake
Cake day: August 26th, 2025

help-circle



  • There’s a note on the Flathub page that it requires permission to your home folder, so this should be granted automatically. Maybe they made an update since you had the issue?

    In most cases the sandboxing should not require user intervention. Apps can either use the native file picker (which gives them access to selected files) or list which directories they want to access in their manifest. If an app tells you to select a file by path-in-text-input or homemade file picker, but doesn’t have permission to the relevant directories, that’s a config issue on the packager’s side.



  • They probably gave up on preventing cheat entirely, and are just trying to reduce the amount of cheaters by making cheating as annoying as possible.

    I do actually believe them when they say that cheating on Linux can be made significantly easier and more comfortable than on Windows. I think it’s a real fundamental issue for Linux, multiplayer games with toxic playerbases can be unplayable due to users being able to do what they want. They would have to make systems to allow for playing in smaller human-moderated servers, or rely purely server-side solutions








  • Hey so, is this a normal thing in meta analyses ?

    We identified 46 studies for inclusion in our analysis. Of these, 27 studies reported positive associations (significant links to NDDs), 9 showed null associations (no significant link), and 4 indicated negative associations (protective effects).

    27+9+4 is 40 I think ? What happened to the 6 other papers ? I’m always confused by the whole “we ignored half of the studies and we won’t tell you why”, if they can also ignore some of the 46 studies they selected, what does the 46 number mean ?


  • If you already have the correct version of the flatpak installed, you can try flatpak build-bundle.

    flatpak build-bundle LOCATION FILENAME NAME where

    • LOCATION is the path of the repo on disk. Run flatpak info -l org.kde.arianna, and copy the part before /app
    • FILENAME is the output file name, preferably .flatpak. Eg: arianna.flatpak
    • NAME is the name of the app, here org.kde.arianna

    The generated file can be installed with a double-click, or with flatpak install <file>

    This is the equivalent of an Android .apk. It contains the app but depends on a runtime. If you want to install it in a few years, odds are the runtime will no longer be available. You can backup the runtime the same way with the --runtime option.

    flatpak build-bundle --runtime LOCATION FILENAME NAME where

    • LOCATION same as earlier
    • FILENAME eg arianna-runtime.flatpak
    • NAME is the name of the runtime, which you can get with flatpak info --show-runtime org.kde.arianna

    This takes a while, for some reason. Maybe it’s compressing stuff?

    The runtime is installed the same way as the app: double click or flatpak install.


    Note: I only did this once, and not specifically on Arianna. Hope it works.