I wonder how they're throwing up that banner. I'm unable to access the blog post even when I navigate to it from their main page now. At least Firefox's Reader Mode seems to do the trick! That, and archived links.
I wonder how they're throwing up that banner. I'm unable to access the blog post even when I navigate to it from their main page now. At least Firefox's Reader Mode seems to do the trick! That, and archived links.
1. JS loads from https://cdn.asahilinux.org/.h which contains a list of "blocked browser history entries". It's likely that this code will be used again for future HN posts. Interestingly, this is very generic and this code can be used by anyone to put up customised block lists based on browser history. This can be circumvented by using private browsing, disabling `mix-blend-mode` on `:visited` links, or `:visited` partitioning.
This JS code is used to automatically generate the main anchor element seen in the sibling comment.
2. According to MDN [1]:
> In addition, even for the above styles, you won't be able to change the transparency between unvisited and visited links, as you otherwise would be able to using the alpha parameter to rgb() or hsl(), or the transparent keyword.
So :visited links are not supposed to affect transparency. How did they do it, then? Using `mix-blend-mode`. The background uses `multiply` (also an anchor) is #FFF for normal visitors (transparent) while #000 for blocked visitors (opaque black). The text uses `lighten`, #000 (thus transparent) for normal visitors, while #fff (thus white text) for blocked visitors.
[1] https://developer.mozilla.org/en-US/docs/Web/CSS/Privacy_and...
<a aria-hidden="true" tabindex="-1" class="hnsucks hnsucks2" rel="nofollow" href="https://news.ycombinator.com/item?id=36971867">Hi! It looks like you might have come from Hacker News. We've consistently found large numbers of comments containing blatant harassment, abuse, and bigotry directed at multiple Asahi Linux developers in HN comment sections, which go unmoderated for long periods of time or indefinitely. These abusive comments rank highly in search results for our project and the names of our developers, and continue to do so to this day.<br><br>In addition, we find that only a tiny fraction of HN comments (often less than 1%) actually engage with the substance of our articles, with the majority being off-topic, misinformative, repetitive, or otherwise of low quality, making the overall value of HN exposure overwhelmingly negative for our project.<br><br>We have tried to raise the issue of rampant abuse and low-quality discussion with HN mods, but instead of replying they added <code>rel="noreferrer"</code> to links to our site (specifically), to make it harder for us to block HN traffic. We sent a further email and explicitly pointed out a thread with multiple severe instances of directed, explicit harassment at one of our developers (including multiple allegations of mental illness, direct insults, misgendering, and transphobic dog whistles, all unmoderated and publicly visible and indexed). Some of these were removed weeks later (after being up for months), but they stopped responding after we pointed out even more instances of abuse.<br><br>At this point, we are forced to conclude that Y Combinator and Daniel Gackle are actively choosing to platform hate and harassment against open source developers, and further are actively working to evade blocking of this harassment by those targeted. For this reason, we are not interested in traffic or commentary from HN. Please move on to the next story.<br><br>To Dang: Do better.</a>While I applaud them for explaining their position clearly, it comes off as small, childish, and unprofessional. They're only drawing attention to the issue and making it worse.
Get over it. People posting comments on HN are not the real world. People write ugly things about CloudFlare, Adobe, and a hundred other companies and projects on HN all the time. You're not special. You ignore it and move on. It's called being an adult.
To Asahi: Do better.