Comment on F-Droid and Google's Developer Registration Decree

Deebster@infosec.pub ⁨3⁩ ⁨days⁩ ago

• 87Six@lemmy.zip ⁨2⁩ ⁨days⁩ ago

  … Why are you being downvoted for pointing it out wtf…

  source

  • Deebster@infosec.pub ⁨2⁩ ⁨days⁩ ago

    Yeah, I was confused too. Perhaps they didn’t see any problem and instead of realising the page had been edited after I commented they just downvoted.

    Back to that article, I wonder if they were trying to add links into their footnotes and that broke stuff. They seemed to have fixed it by deleting them all, but that’s quite a lot of content gone.

    E.g. after pairing up the broken footnotes with their endings that stayed in the main text you can see these:

    How many F-Droid users are there, exactly? We don’t know, because we don’t track users or have any registration. “No user accounts, by design”: https://f-droid.org/2022/02/28/no-user-accounts-by-design.html

    ‘> “Sideload” is a weird euphemism that the mobile duopoly came up with; it means “installing software without our permission,” which we used to just call “installing software” (because you don’t need a manufacturer’s permission to install software on your computer).’ — Pluralistic: Darth Android: https://pluralistic.net/2025/09/01/fulu/

    source

    • 87Six@lemmy.zip ⁨2⁩ ⁨days⁩ ago

      Yea the rich editor probably broke on an update or something. I’ve dealt with that before. Those rich text editors like ckeditor are amazing, until they break one day or a plugin becomes unsupported and you either fix it, or it messes up loads of your content… Caching saved us more than once with that sort of thing. We just used the cached pages and lelft the original completely broken, it just couldn’t be edited anymore but it showed up fine.

      source