• jarfil@beehaw.org
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    5 hours ago

    Update: I see the issue now.


    I don’t see the issue:

    1. F-Droid compiles the apps
    2. F-Droid publishes the apps
    3. F-Droid gets registered
    4. F-Droid subclasses app identifiers under its own

    …and things go back to normal.

    You won’t be able to update an F-Droid app with an Obtainium one, but Android is already warning about those, not allowing automatic updates from mixed sources.

    • numeral_paver555@lemmy.ca
      link
      fedilink
      arrow-up
      2
      ·
      1 day ago

      The thing is that changing the app id requires too much patching to thousands of apps, and the users will not be able to migrate from the current f-droid version.

      • jarfil@beehaw.org
        link
        fedilink
        arrow-up
        1
        ·
        23 hours ago

        F-Droid does automated patching already, they often remove “anti-features”. The migration is a PITA, but not the end of the world, Kiwix did that recently (split into Play Store and F-Droid versions).

        • numeral_paver555@lemmy.ca
          link
          fedilink
          arrow-up
          1
          ·
          20 hours ago

          That patch is manually added. Moreover, some apps have hard binding with their id, making the situation more complicated. Kiwi is not on f-droid at all. They host their own version. It might be easier for the app authors to do it. But f-droid maintainers don’t have this capacity.

          • jarfil@beehaw.org
            link
            fedilink
            arrow-up
            2
            ·
            5 hours ago

            My bad, Kiwix is on IzzyOnDroid. You’re right, F-Droid itself might have a tougher time.