Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Use wildcards in sites blocking options (at least for notifications)

7 views
Skip to first unread message

Camion

unread,
Jan 5, 2019, 2:39:06 AM1/5/19
to
As usual, when one adds new capabilities, one will find trash who abuse it.
This is about the site pshntf.com who will generate random xxxxxx.pshntf.com domain names to repeatedly ask the right to push notifications on your computer.

I solved this problem by blocking the whole domain in my hosts file, but it would be much better if there was a possiblity to specify *.pshntf.com in the site wise notification config list.

Camion

unread,
Jan 6, 2019, 9:51:48 AM1/6/19
to
Finally, blocking the whole domain name in hosts wasn't even sufficient...

Mark Rousell

unread,
Jan 6, 2019, 7:15:47 PM1/6/19
to wish...@lists.mozilla.org
I know this isn't a tech support group but here goes:-

On 06/01/2019 14:51, Camion via wishlist wrote:
> Finally, blocking the whole domain name in hosts wasn't even sufficient...
> _______________________________________________
> wishlist mailing list
> wish...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/wishlist

Does hosts support wildcards subdomains? I suppose it depends on the
operating system. Perhaps some do although I think most do not.

Instead I think you'd need to use a DNS proxy. I've not tested it but
this, https://pi-hole.net/, appeals to me.



--
Mark Rousell




EE

unread,
Jan 15, 2019, 1:27:04 PM1/15/19
to
If you use an ad-blocker, you should be able to add a
wildcard-surrounded domain name to your personal blocklist on there to
block the entire domain. I have done that with every ad-blocker I have
used.

0 new messages