Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Safari Cookie-Autodelete #964

Closed
kistanovdev opened this issue Nov 13, 2020 · 3 comments
Closed

[FEATURE REQUEST] Safari Cookie-Autodelete #964

kistanovdev opened this issue Nov 13, 2020 · 3 comments

Comments

@kistanovdev
Copy link

Now that the new version of Safari is able to support a broader range of extensions, is it possible to port cookie-autodelete?
This is the only extension that is stopping me from moving to Safari fully!
I love this extension and consider it essential for my daily internet usage.

Best,

Daniil K

@github-actions github-actions bot added the incomplete Issues/Requests with missing/incomplete template body. label Nov 13, 2020
@github-actions

This comment has been minimized.

@kennethtran93
Copy link
Member

kennethtran93 commented Nov 13, 2020

Long Story Short: Despite the recent bridging attempt by Apple, it is still unlikely at this time.

Until the Apple Developer Program is either free just to develop and publish Safari Web Extensions, or a small one-time fee, it is highly unlikely. Do you think it is feasible that an open-source extension should fork out $99 USD per year to enroll in their developer program just to publish a free extension? We may be able to only if we can sustain at least that amount in donations per year. Also an 'Organization' has to be a registered/legal one, otherwise it would go under one person's name (i.e. Kenny Do). This also means that only he will be able to compile/publish it under his Apple ID.

EDIT: I briefly read over the fee wavier portion, and it applies to non-profits and whatnot. Explicitly states not for individuals/sole-partnerships/etc, but unsure about open source (though realistically only the two of us manages it at this point).

According to this doc, 'porting' our web extension requires wrapping our code into a safari app for publishing to the app store. In addition, at least one function (namely the cookies.onChanged listener) is not supported, so additional code needs to be injected to check and disable that function (which also means that the cookie count may not be up to date at times).

@kistanovdev
Copy link
Author

Thank you for the clarification!

@kennethtran93 kennethtran93 removed the incomplete Issues/Requests with missing/incomplete template body. label Dec 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants