To be fair, that's a server-side error that will probably always occur (so the site is effectively permanently down), not like the original client-side error caused by users configuring their browsers in a way that site owners might consider hostile or otherwise not worth supporting.
It's not considered hostile by the site owners https://news.ycombinator.com/item?id=10959363
in fact it's already fixed. My original comment was in the spirit of helping a fellow programmer find a possible bug. On the other hand I found themartorana's comment to be particularly snarky wrt a large proportion of web citizens that are increasingly worried about their privacy.
The fact that his own website doesn't seem to work at all is just very ironic.
I do see that these particular site owners don't mind their users using Ghostery and uBlock. Some may not go out of their way because they see it as their users denying them ad revenue or analytics (the user is "hostile".) A similar situation happens with NoScript, where some site owners view Javascript as a basic, easily-met prerequisite to using their site, and will do nothing to help users who don't want to enable JS.
I presumed that's what themartorana was referring to about why they might not bother to fix it, and why I thought it would be useful to point out that according to the error message you got, themartorana's site is broken in a different, more fundamental way.
