User's banner
Avatar

metaeaux

metaeaux@lemmy.ml
Joined
1 posts • 5 comments
Direct message

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.

permalink
report
parent
reply

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

permalink
report
parent
reply

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.

permalink
report
parent
reply

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. 🤷🏻‍♂️

permalink
report
parent
reply

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.

permalink
report
reply