So all search add-ons are forbidden? What does “installing” a website even mean? And what’s the difference between loading and launching a website?
I get that this rule is meant to combat spam, but you really should use clear language here.
1 Like
So don’t stress yourself just yet
. Focus on what’s important and have a nice week!
Also your insinuation here is that our extensions are unimportant. Your post was just condescending and discounting our intelligence until then. Adding this sentence rises to the level of being downright disrespectful.
None of us who are talking about http/https and whether self-signed counts as real are talking about the “wide internet.” We’re all talking about talking to a proxy on the localhost which in turn handles requests to a service which is already encrypting the traffic. I’m even offering to unnecessarily switch to HTTPS over I2P/Onion, even though it is redundant, just to make a Mozillan’s job easier. It would be nice if we could get an actual answer instead of being ignored or handwaved off.
Oh man, I’m really sorry, that is not what I meant at all!
I’m just an addon developer like everybody else in this thread and I just wanted to help calm down the situation because I honestly don’t believe this is goona be an issue for any of them (even though I don’t really know).
And when I say focus on what’s important, that means (for me) developing new features instead of trying to fix a problem that doesn’t exist yet.
Again, I’m sorry, if my words sounded disrespectful, that’s really not who I am.
It’s OK I’m not actually mad at you. That said, it’s already been an issue for me(I am the reason that the cookie consent requirement is now conditional). My ire is completely focused on the AMO team right now. There are like 40 questions on this almost 3 week old thread and only one answer. AMO has appeared broken for about a year and they’re not listening at all or telling us anything about what’s going on. We’re forced to look at the evidence surrounding the situation AMO and conclude that spammers(spamming malicious addons) are successfully DOSing legitimate addon developers by exhausting Mozilla’s time. Policy changes aren’t going to make AMO/extension developers harder to attack in this way. Maybe not all extensions are that important but some are extremely important. Snowflake and uBlock Origin are extremely important, for instance.
Hi, everyone - Mike Hoye here, on behalf of the Add-ons team. I wanted to thank you for your questions; I’m collecting them for the team, and we’re going to go over them together shortly.
One of our main goals for this update is that the policy document itself to be able to answer your questions as much as possible. No policy can cover all cases, but in those places (several of them you’ve already mentioned here) where there are difficult edge cases in play or other things that need more clarity and specificity, we’ll try to provide that.
As an aside, when Juraj says, “Nobody wants to take down your addon made with love for users like you!” - that’s true, nobody wants that, but we have a set of standards and policies here that are important for the safety of the whole Firefox community, and they define how the Add-ons team enforces policy, so: the words matter, and we’d like to get them right. Especially for developers making stuff out of love for their users. So, thanks for all of your help here, we’ll have good answers for you soon.
-mhoye
4 Likes
Is there a timeframe when we should expect some clarifications to the questions? Given that there are a couple of them and as I understand you’ll start enforcing the policy in 7 days.
1 Like
Does private add-ons also need to show the consent dialog when collecting technical or user data?
If so how much time we have to implement them?
Will our future submissions be rejected if we don’t implement them?
Given that there hasn’t been any clarifications yet, are you still going to start removing our extensions from tomorrow?
1 Like
Thank you @mhoye for the updated information.
Regarding changes to listings, such as the new mandatory privacy policy, how long do we have to update our entries? Is there any sort of grace period to update existing addons?
This link is 404 now https://extensionworkshop.com/documentation/publish/add-on-policies-dec-2021
So does this HTTPS policy mean we cannot perform GET/POST requests to HTTP? My extensions communicate with my employer’s local web servers which I’ll never be able to get IT to change.
1 Like