Slashdot Mirror


Mozilla Will Run Two Experiments This Month With Firefox To Explore Ways To Fight Push Notification Permission Spam (zdnet.com)

Mozilla said this week that it intends to run two experiments over the course of this month to determine the most adequate way of dealing with push notification spam, a growing problem that is slowly deteriorating the web experience for everyone. From a report: The experiments will run in Firefox Nightly (v68) and Firefox Beta (v67). The Firefox Nightly experiment will run from April 1 to April 29. During this time, Mozilla said Firefox Nightly would only allow websites to show a push notification permission only after the user has clicked or pressed a key while on a website. All attempts to show a push notification permission request before a click or key press will be blocked by default. [...] In the last two weeks of the experiment, Firefox will show an icon in the URL bar, but with no visible popup on the page. Users can click this icon and accept any push notification permission requests if they wish so. Further reading: Mozilla and Scroll Partner To Test Alternative Funding Models for the Web.

6 of 98 comments (clear)

  1. Solution by Rockoon · · Score: 4, Insightful

    Stop allowing websites to pop up anything, every. Seriously. For fuck sakes.

    Why is this hard to understand?

    --
    "His name was James Damore."
    1. Re:Solution by nmb3000 · · Score: 4, Insightful

      Stop allowing websites to pop up anything, every. Seriously. For fuck sakes.

      Why is this hard to understand?

      I have to assume it's because everyone working on the HTML5 stuff is too young to have learned anything from the first time around. In a lot of ways HTML5 is just version 2 of alert(), confirm(), and the embed tag. Throw in a little blink and marquee for good measure (and don't forget object and applet with WebAssembly).

      It turns out that most of these were just abused a lot more than they were used for anything worthwhile. Is anyone surprised that HTML5's allow-by-default or ask-by-default notifications, video, location, camera, microphone, canvas, etc are being abused in the same ways, by the same actors? Only the 20-somethings writing the specs, I guess.

      --
      "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
      /)
  2. Re:You can turn them off by Luthair · · Score: 5, Insightful

    Because its not a good experience if every single website you go to shows an asked for popup about showing you notifications, asking your location, etc. etc..

  3. No problems here by renegade600 · · Score: 3, Insightful

    I don't have too much of a problem with push notifications, it is those videos I want stopped. some you have to wait for it to download before you can do anything with it, some you have to look for on a page because you hear it and not see it, some blocks what you are trying to read because it won't close.

    Then there are those sites that constantly bomb you with their subscription popups. how about stopping those too. maybe if they stop the notification ones, it will stop those.

  4. Take 'push' notifications out of the browser by BitZtream · · Score: 3, Insightful

    Problem solved. See how simple that was? Do you need notifications in your browser: No, not unless you're trying to use a browser as an application engine, which is your first mistake; Everything after that is just more calamity.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  5. We need to stop the HTML5 madness by xack · · Score: 1, Insightful

    Stop adding bloat to the specification that just adds more ways for advertrackers to steal your hardware resources. If I was in charge I would go back to HTML4 with just the video tag added.. All this bloat makes browser engines complicated which is why everyone is just cloning chrome instead of making their own engines.