Yes. And no. The affected users usually have no control over the situation, so if the site owner cares at all that those people can't access it, then it is effectively their problem as they can potentially do something about it.
If neither party cares enough, then it is nobody's problem.
> The affected users can stop using brain damaged systems.
Often not, because as I said in what you replied to:
> The affected users usually have no control over the situation
The affected users are usually on devices controlled by others or on their own devices connected through networks controlled by others: at work, in schools, in libraries, etc. The affected users and the those configuring the "new site" block (or leaving it on by default) are not the same set in many cases.
My work users such a filter, there is nothing I can do on their laptop to get around it¹, though my phone newer connects to their network so I can just look at things that way if I care to.
--------
[1] OK, there are things I could do, but they would be an abuse of the admin level access I have on the machine, because some things needed for my job don't work properly without that, and it isn't worth that arguement if noticed!
They likely won't change anything. The consensus is that brand-new unclassified domains can be a risk (used for phishing purpose and such) so wait until it is classified otherwise or has been around longer. Of course old domains are a phishing risk to as they can so easily change hands, but they are much less likely to have the “looks a bit like that new trending name” property that can make new domains valuable to scammers.
That's pretty much it. I wouldn't have mentioned it if not for the fact that it's easy to fix and for users it just looks like the site is down, which is not uncommon for small projects posted to HN.
I guess some people thought I liked cloudflare or something... that's definitely not the case.
"easy to fix" is relative. This "new domain equals bad" thinking has spread in the IT security world. My corporate anti-virus blocks them too and I see it a lot while browsing HN on the job.
The only real solution, as a "holder of a young domain" is to wait 30 days before you use it.
Or somehow get it reclassified. But waiting is probably fine for most purposes, give you might have to make the classification effort in several places.
Well, it's certainly a dumb situation that I don't like that's created by my employer (and many others with similar setups), but it takes only two clicks to pick a category to make it available to folks behind these firewalls.
I went ahead and chose "blog" because it sounds like it's a blog. Apparently the "newly seen domains" category goes away on its own after 30 days, so that would have fixed itself, though then it would have been "uncategorized" and still blocked.
https://radar.cloudflare.com/domains/feedback/naturalsystems...