I found a decent safari extension for iOS for redirecting links to privacy focused frontends: Privacy Redirect

If you’re self-hosting a private instance that’s not secure you’ll need to put http:// at the start of the URLs specifically.

  • metaeaux@lemmy.ml
    0·
    1 year ago

    Who’s whining? I haven’t even contacted them. I paid for their app, but didn’t use it because the implementation didn’t meet my needs. So I wrote my own. 🤷🏻‍♂️

      • metaeaux@lemmy.ml
        2·
        1 year ago

        Not yet. I’ve renewed my developer account recently. I’ll try to get the code cleaned up and submit it. 🙂

      • metaeaux@lemmy.ml
        2·
        1 year ago

        You’re inferring a lot more emotion and tone in my comments than what I have felt as I wrote them. As such, your responses are making it an unpleasant experience to share knowledge with a community.

        • Norah - She/They@lemmy.blahaj.zoneOP
          1·
          1 year ago

          You mean how you inferred a lot more intention from the dev in your comments, and made it unpleasant to share a resource with a community?

          It’s fair enough to share that it currently isn’t fully secure. But you complained the dev would never fix an issue they’ve known about for a few months. Then you went on about how you just coded an app yourself. Well then go put it on the app store so there’s a secure one if you think the dev won’t ever fix it. Or, contribute back to the open source community. Or, don’t cast aspersions about what other devs do with their time.

          Edit: The dev’s also a human being. They might have had a significant life event happen during that time.

          • metaeaux@lemmy.ml
            1·
            1 year ago

            The app might be GPL, but it’s a paid app. I see no reason to submit a PR to do the work for the developer. I am also a customer of his, so I don’t think it’s unreasonable that I had hoped he would make his app fit for purpose. If I raise a PR to help his LLC sell apps, I have no control over whether he will actually accept changes or submit changes to the App Store, either. I don’t intend to give my time away like a charity to an LLC.

            I wrote my own app to determine whether Safari had implemented enough of the properties of the declarativeNetRequest API to allow for redirects. It turns out that it does, and in this way, it avoids reaching destination servers and avoids cookies they may set or analytics they run, and counts towards MAU. It also works with DNS blocks to target sites.

            If I release it on the App Store, it will be free.

            In any case, I said nothing bad about the developer except that they are aware of the new API but have not shared plans or shown motivation to adopt it. That’s not a negative comment and does not detract from the possibility of significant life events etc. It’s simply an observation.

            It seems like you’re crafting a straw man out of a few words I shared about a privacy app.