Flatpak has served us well for 10 years and succeeded in establishing a direct distribution model for app developers, independent of the underlying platform....

Warning: the audio is bad and will occasionally get very loud

  • Leaflet@lemmy.worldOPEnglish
    371·
    4 days ago

    Don’t believe so, best that’s currently available is skimming through the video to look at the slides.

    Here’s the bullet points of the presentation

    • Flatpak is stagnant
    • Red Hat is working on a better way to preinstall flatpak apps
    • Flatpak should is slowly moving towards OCI and away from ostree (more tooling available, don’t need to maintain their own tools)
    • Better permission handling that is more backwards compatible
    • Should directly use Pipewire instead of Pulseaudio (WIP)
    • Allow user namespaces in flatpak sandbox (WIP)
    • Move dbus proxying into dbus brokers (wishlist)
    • Improve network sandboxing (wishlist)
    • Improve drivers handling, currently drivers need to be built for each runtime, could cause issues if using EOL app on new hardware (wishlist)
    • Work on portals directly improves flatpak
      • Leaflet@lemmy.worldOPEnglish
        6·
        3 days ago

        Major people of the project had moved on. It’s being maintained, getting security fixes, but pull requests are slow to be merged.

    • drwankingstein@lemmy.dbzer0.comEnglish
      3·
      4 days ago

      Should directly use Pipewire instead of Pulseaudio

      I hope they plan on keeping pulse for the foreseeable future. Pipewire is great and all but pulse is very entrenched, I still maintain quite a bit of systems that are pulse only.