I'll also throw a vote out that I do not see the value in having a public feud over whether one specific site is allowed to block HN traffic. I actually agree with stripping referrer headers from all posts (for user privacy reasons), but in
addition I think it's clearly the right move to block links to asahilinux.org
It would:
A) not ban people from talking about Asahi Linux and would not prevent links about Asahi Linux from being shared.
B) be at least somewhat of a gesture of goodwill that the HN community is not trying to force itself into other communities (which we shouldn't be doing anyway).
C) not force HN to build a generic "anyone who wants to get blocked can get blocked" system.
HN moderation regularly takes context into account when making decisions (and in fact, the moderation would be much worse if it didn't). Yeah, of course the NYT should not be able to ask HN to stop linking to articles. But that's not the current situation. Regardless of whether or not HN is obligated to block links to asahilinux.org from being posted, it would be a low-impact move for the HN community that would go a long way towards both diffusing the controversy and would (from the sound of things) be a high-impact positive change for the Asahi Linux community.
And regardless of whether people think the Asahi Linux community is being reasonable or not, if there's an easy way to accommodate people who have a concern and it's not forcing us to do something drastic or high impact -- we should do it. If it becomes a problem in the future, if tons of sites start doing this and it impacts the community's ability to have conversations about current events, then change the policy. You're not locked into anything.
In the meantime, why not try to accommodate someone who feels harassed by certain HN users? It just seems like a very simple way to show some kindness towards another community.
---
To the point that users might misinterpret those blocks as hostile, I know that HN tries to make very minimal code changes, but no matter how hard I try I also do not understand why it wouldn't be possible with minimal code changes to show/redirect to an error that explained the situation.