-
-
Notifications
You must be signed in to change notification settings - Fork 118
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
premium features #3804
Comments
How would payment be handled?
Paywalling mirrors of public filterlists might get people mad. |
TBD. Preferably as privacy-respecting as possible, but honestly it would probably be some 3rd-party like Stripe.
Yeah, I agree. I thought maybe there would be some value of hosting mirrors just for historical purposes in case a list ever dies / goes offline. But, I certainly wouldn't suggest that people rely on FilterLists mirrors for daily use. Yeah, I'll probably scratch this idea. |
No, I think the historical filterlists would be awesome (license abiding), though I personally wouldn't pay for it. I'm just unsure how filterlist maintainers would react. |
At least in uBO, only a handful of lists are non-commercially licensed and even then, those are being used in commercial context such as AdGuard or Brave, and still no reaction from the maintainers. |
Brainstorming some ideas for premium features for a potential paid feature set down the road. The core information will always be freely accessible, but there are some advanced features I'd love to add that would require revenue to support.
Before any of the features below are started, #372 has to be the priority.
FilterLists-hosted mirrors (license-permitting) FilterLists-hosted mirrors #464bonus: historical versions of listsFeedback is welcome on any of these ideas. Would these features or others be worth paying for for you?
The text was updated successfully, but these errors were encountered: