Earlier quoted context omitted.
No but you need telemetry to find out how users react to abusive notifications and how they interact with websites where they do genuinely want notifications from. You can't just guess that.
>you need telemetry to find out how users react to abusive notifications You need telemetry to find out how users react to abusive notifications? Wow. I know that A/B testing is in vogue, but can’t they just use some common sense? People despise abusive notification prompts. People despise abusive location prompts. People despised abusive popups to the point that every browser blocks them and websites started emulati…
Common sense doesn't work here because everyone has a different perception of when these prompts become abusive or unwanted. Mozilla uses the data collected to determine how they can establish a rule to distinguish between abusive prompts and non-abusive prompts.
How users react to them is a good indicator if the prompt was abusive or not, most people will decline abusive prompts and accept good ones.
A simple "wait until first DOM interaction" will likely be not sufficient since a simple click on a text would then create the prompt. With more data you can determine a better rule.
That people despise these prompts is fairly obvious and exactly why Mozilla is collecting the data; they want to help people by establishing a good common ground rule for these notifications to be automatically blocked.