Privacy Badger v1.0 incompatible
Moderators: Lootyhoof, FranklinDM
Re: Privacy Badger v1.0 incompatible
One can only dream...
-
CharmCityCrab
- Banned user
- Posts: 638
- Joined: 2015-06-25, 00:47
Re: Privacy Badger v1.0 incompatible
Alright, one of the devs behind Privacy Badger was kind enough to answer a few questions I had.
To summarize briefly in my own words:
1. Privacy Badger will not develop for Pale Moon unless their (PB's) circumstances or priorities change, *but* they will accept a patch to make it work with Pale Moon if anyone wants to volunteer one, and would likely give it official branding.
2. Privacy Badger will at some point be switching to Firefox's web extension API. At that point PB will not maintain a "legacy" version for Pale Moon support and would have to have someone step up and do it themselves (I did say something about the use of the word legacy in this context and that it probably wasn't applicable to Pale Moon, but I just sent that off now).
What I make of that is:
1. If an interested party with the skills were to step up, they'd probably cooperate and give it official branding. So, one wouldn't have to do a true fork and go the IceWeasel route, but could actually work with the devs and keep the Privacy Badger name and potentially get it advertised and distributed through their channels.
2. They aren't going to do it themselves. Someone needs to volunteer if it's to be done.
3. Seems like there is an option there for someone to just submit a one-time patch to make PB compatible with PM until the API change, but after that they'd need a full time person to write a PM version or discontinue support, because they won't be supporting the API PM uses once Firefox drops it.
Also, just a couple generally vaguely off-topic points:
- They'd like to support Firefox for Android, but don't have enough development time right now.
- The impression I'm getting, and this is just me, not anything the dev told me, is that Pale Moon might want to seriously consider adopting the new web extension API in addition to (Rather than instead of, as with Firefox) the APIs it already supports. I get a sinking feeling that 95% or more of extensions are going to decide that that they don't want to write their extensions twice, and given the choice will follow the marketshare and write for Firefox. There will be exceptions, of course, where devs would rather maintain an add-on for a 1% share type browser that requires minimal changes rather than write it again from scratch for a 20% share type browser, but we may be left without a lot of add-ons as most will choose to follow the users unless we cache static unmaintained old copies which could pose a security risk and wouldn't be adapting to Pale Moon's own changes, leaving the potential for them to be broken by future Pale Moon updates.
To summarize briefly in my own words:
1. Privacy Badger will not develop for Pale Moon unless their (PB's) circumstances or priorities change, *but* they will accept a patch to make it work with Pale Moon if anyone wants to volunteer one, and would likely give it official branding.
2. Privacy Badger will at some point be switching to Firefox's web extension API. At that point PB will not maintain a "legacy" version for Pale Moon support and would have to have someone step up and do it themselves (I did say something about the use of the word legacy in this context and that it probably wasn't applicable to Pale Moon, but I just sent that off now).
What I make of that is:
1. If an interested party with the skills were to step up, they'd probably cooperate and give it official branding. So, one wouldn't have to do a true fork and go the IceWeasel route, but could actually work with the devs and keep the Privacy Badger name and potentially get it advertised and distributed through their channels.
2. They aren't going to do it themselves. Someone needs to volunteer if it's to be done.
3. Seems like there is an option there for someone to just submit a one-time patch to make PB compatible with PM until the API change, but after that they'd need a full time person to write a PM version or discontinue support, because they won't be supporting the API PM uses once Firefox drops it.
Also, just a couple generally vaguely off-topic points:
- They'd like to support Firefox for Android, but don't have enough development time right now.
- The impression I'm getting, and this is just me, not anything the dev told me, is that Pale Moon might want to seriously consider adopting the new web extension API in addition to (Rather than instead of, as with Firefox) the APIs it already supports. I get a sinking feeling that 95% or more of extensions are going to decide that that they don't want to write their extensions twice, and given the choice will follow the marketshare and write for Firefox. There will be exceptions, of course, where devs would rather maintain an add-on for a 1% share type browser that requires minimal changes rather than write it again from scratch for a 20% share type browser, but we may be left without a lot of add-ons as most will choose to follow the users unless we cache static unmaintained old copies which could pose a security risk and wouldn't be adapting to Pale Moon's own changes, leaving the potential for them to be broken by future Pale Moon updates.
-
Morgoth
Re: Privacy Badger v1.0 incompatible
What I still don't get after all:
1.0.1 is recommended for pale moon here: https://addons.palemoon.org/resources/incompatible/
Indeed I find a settings menue in the properties, where I can check or uncheck some options, so it seems to work just fine.
But does it actually have any effect, meaning does it block trackers? Does not look like it, when I read this thread. So why is it still recommended?
I had Firefox compatibility mode turned on, so I did not realize that there are problems with PB in Pale Moon at first. This was version 1.0.5 from EFF's site. And with that version I did not have the opportunity to change the options (in contrast to version 1.0.1).
So my question is: Does version 1.0.1 has any effect at all, when using it in Pale Moon? Or are both useless, 1.0.5 and 1.0.1?
1.0.1 is recommended for pale moon here: https://addons.palemoon.org/resources/incompatible/
Indeed I find a settings menue in the properties, where I can check or uncheck some options, so it seems to work just fine.
But does it actually have any effect, meaning does it block trackers? Does not look like it, when I read this thread. So why is it still recommended?
I had Firefox compatibility mode turned on, so I did not realize that there are problems with PB in Pale Moon at first. This was version 1.0.5 from EFF's site. And with that version I did not have the opportunity to change the options (in contrast to version 1.0.1).
So my question is: Does version 1.0.1 has any effect at all, when using it in Pale Moon? Or are both useless, 1.0.5 and 1.0.1?
-
dark_moon
Re: Privacy Badger v1.0 incompatible
You better use another addon to block trackers because the addon dev say they didn't give any pale moon support: https://github.com/EFForg/privacybadger ... -155566212
Anyway privacy badger isn't a good tool (just my opinion)
Anyway privacy badger isn't a good tool (just my opinion)
Re: Privacy Badger v1.0 incompatible
Privacy Badger is not really compatible with other add-ons like Disconnect or Ghostery. It works by analysing the behaviour of sites that may track you. If you already block tracking sites with a different add-on then installing Privacy Badger is pretty pointless as it simply can't do the job it was designed for.