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
    5·
    1 year ago

    Just an FYI that this extension redirects after the initial request is made, due to a limitation the WebRequest API from when the extension was implemented. This means it still reaches the destination before the redirect occurs.

    The developer has been made aware of the declarativeNetRequest API which avoids this issue but he has yet to make any updates.

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

      Okay, so I went and checked out that issue and I spent 20 minutes reading the linked documentation and checking through the codebase. As far as I can tell, implementing this would require a complete re-write to how the extension currently works. This is because declarativeNetRequest is designed as a more secure replacement for webRequest, which is probably why Apple supports it in the first place. It takes the job of writing redirects out of the hands of the extension and gives it to the browser instead.
      In the current codebase, after the browser matches a url, the extension runs a .js file to chop out what it needs, rewrite it and finally trigger the redirection. webRequest would be able to block the domains and still run those .js files. declarativeNetRequest would require all of that to be rewritten as regex and JSON expressions. It also might not even be possible, as I’m not sure you can dynamically change those JSON expressions after the fact, say when you want to change which instance you’re being redirected too.

      Edit: Also the dev was made aware in late March, so if a full rewrite is needed I’m not surprised it hasn’t been completed yet.

      • metaeaux@lemmy.one
        1·
        1 year ago

        Rules can be updated dynamically using updateDynamicRules.

        I wrote an extension that implements declarativeNetRequest redirects to private front ends just using a static hardcoded list. It only took a couple of hours. I’m using it on MacOS and iOS. I don’t think it’s the kind of thing that would take significant investment from the developer, I just don’t think they have any plans or motivation to make it more private than the current implementation.

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

          I think you’re assuming a lot of the developer. It’s just one person, and selling this for a few bucks clearly isn’t their day job. The entitlement of some people on github is real. Like, why not help the dev out, submit a pull request? Instead of whining that they won’t ever implement something.

          Edit: Before you tell me to put my money where my mouth is, before I made this post I submitted a pull request to this repo. Wanted to be able to set my invidious instance with yattee:// at the start so it would automatically open them in app instead. Actually found an issue with someone else requesting the same feature and linked the PR to it.

          • metaeaux@lemmy.ml
            1·
            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.