[windsurfer]

It's interesting how this site gets around the ``rel="noreferrer"`` added to the link from HN. The banner uses a :visited CSS attribute to selectively show/hide the banner client side if your browser has been to the URL https://news.ycombinator.com/item?id=36971867. With how many other browser history privacy leaks have been released lately using :visited hacks, I wonder how long it will be until browser vendors disable :visited support across domains entirely.

[cbarrick]

Interesting that it only checks for the comments page. If you (like me) read the article before coming to the comments, then you'll not see the banner.

That feels like a typical user flow, which should make the banner fairly ineffective.

I feel for the developer, even if I am annoyed by the banner. It sucks to know that folks on HN have been so mean, when on a technical level, Asahi is a great project.

[twiss]

I typically open both the article and comments in tabs, and then read the article first (promise! :)), but I did see the banner.

[twiss]

There is indeed a proposal to partition :visited links: https://github.com/kyraseevers/Partitioning-visited-links-hi...

[fotta]

I’m not seeing the banner when coming from the comments on iOS Safari. Maybe it just doesn’t show on mobile though.

[cosmojg]

Nah, I'm getting it on mobile via Firefox. Sounds like a Safari thing.

[CaptainFever]

I find it creepy that websites have a way to access my browser history. Luckily it seems like iOS Safari isn’t vulnerable, as is Tor (which I guess solves it by being in permanent private browsing mode?)

[throwawaylpsa1]

You can get around the banner with this uBlock custom rule:

    asahilinux.org##[aria-hidden="true"]