• Krzd@lemmy.world
        link
        fedilink
        arrow-up
        11
        arrow-down
        3
        ·
        9 days ago

        Nope. They initially added some data scraping parts, and apparently still use some form of telemetry without proper disclosure.

          • fmstrat@lemmy.nowsci.com
            link
            fedilink
            English
            arrow-up
            3
            ·
            8 days ago

            This hasn’t been proven in any way. Original op in link states it could be discovery for email domains.

            • kixik@lemmy.ml
              link
              fedilink
              arrow-up
              6
              ·
              8 days ago

              What they’re saying there is that when trying to auto detect the server configurations, there are unexpected connections to cloudfare IPs, which didn’t usually happen with K9. Who posted the concern associated this to telemetry, but the answers are pointing a different direction. But at this point it just guesses, :(

              I guess some more formal traffic inspection needs to happen to understand if truly there’s unexpected traffic, where it is directed to, and hopefully infer somehow its purpose. The guesses about what’s happening suggest it’s just about the auto connection, but again, just guesses.

              I explored the configurations, and I didn’t find anything about telemetry, and so neither how to disable it. K9 does not have an about:config advanced configuration like desktop Thunderbird does, so if there’s truly telemetry or some other sort of information leakage, then after proving it, perhaps developers realize they can do better. But so far nothing really proving telemetry or information leakage.