zlacker

[return to ""]
1. e40+(OP)[view] [source] 2023-06-07 14:06:57
It’s a little hard to understand what is going on. Can you explain? Thanks.
2. pyrox+x2[view] [source] 2023-06-07 14:19:21
>>e40+(OP)
Asahi Linux's site previously redirected any site with the Referer header set to 'news.ycombinator.com' to google.com. They did this because they believe that Hacker News' community fosters a hostile environment, and thus it was blocked. Setting `rel=noreferrer` on an `a` tag means that the browser will not submit this header, thus meaning this sort of redirect will not occur. Also(as per Marcan's Mastodon account), this rel tag has only been added to asahilinux.org links, not any other links on HN. This means that the moderators of HN believe that the commentary that has in the past been quite misinformative should be allowed, and they are deciding to bypass the block that was put in place by the Asahi team. Now, as per https://social.treehouse.systems/@marcan/110503331622393719 , they're adding an HTML header to anyone who has submitted a post to HN(or has the submit page in their history), as they have no other way of doing anything, as they no longer have the Referer header.
◧◩
3. 101011+f8[view] [source] 2023-06-07 14:47:01
>>pyrox+x2
This raises interesting moral questions that I'm not sure I have an answer to.

For one, I don't believe this place fosters a hostile environment, although it's definitely a place where people love to tell you how you're technically wrong about something.

For another, I would guess that there are a very limited number of websites that would opt into this sort of anti-traffic behavior. Hacker news could certainly choose to honor it, but it also feels within their right to bypass the block.

I wonder if there's a sort of middle ground, where HN alerts the user of the redirect that would have occurred, but still shoots the user to the desired location.

But now you're getting into user flows and begging the question as to why the redirect is there in the first place.

I'd love to know more about the perceived hostility, even reading up on Mastodon left me with more questions than answers.

◧◩◪
4. sussma+ql[view] [source] 2023-06-07 15:39:53
>>101011+f8
there is constant transphobia against Asahi contributors on display on this site. Every single article that gets to the frontpage will have dozens of vile posts in the deads and a couple sprinkled inbetween. I’m not sure if HN staff doesn’t care about it, agrees with them or simply isn’t aware.

It’s not limited to the Asahi project, either. The site isn’t safe for queer folks.

◧◩◪◨
5. troad+hF[view] [source] 2023-06-07 16:51:19
>>sussma+ql
> there is constant transphobia against Asahi contributors on display on this site

Could you be so kind as to link me to an example?

People have discussed Marcan's anime alter ego, certainly, but I've never seen anything transphobic in the slightest. Maybe it's all flagged before I get to see it, but I honestly can't figure out what you might even be referring to. I enjoy reading Asahi updates when they come up, so I am unsure how I could be missing something so 'constant'.

> It’s not limited to the Asahi project, either. The site isn’t safe for queer folks.

As a 'queer person' myself, I find that statement utterly ludicrous and I reject it completely.

◧◩◪◨⬒
6. asmor+VR[view] [source] 2023-06-07 17:39:18
>>troad+hF
> People have discussed Marcan's anime alter ego

This is pure and poor conjecture, just like the rumor (originating on chan boards and KF) that a person close to marcan had faked suicide. Exactly this sort of rumor mill is what is wrong with HN linking to Asahi developers.

> As a 'queer person' myself, I find that statement utterly ludicrous and I reject it completely.

Are you a cis gay? I remember a few cases where people reached out to have information redacted to dang and it took weeks. While the people mentioned above were digging into private lives. This site absolutely requires you to shut the fuck up about your own life if you are at risk of being turned into a "lolcow" or pedojacked or whatever else these people will come up with. I understand that's not a consideration yet for 'queer people' currently not conscripted to the front of the culture war.

◧◩◪◨⬒⬓
7. troad+yc1[view] [source] 2023-06-07 18:48:47
>>asmor+VR
I can honestly say I've never, ever, heard anyone call anyone else these terms on Hacker News. I don't think I've ever even heard those terms before. It sounds like you might be very online, in a way that seems to be making you unhappy.

Some of my most upvoted comments on here have been from a 'queer' perspective. It helps to assume good intentions and engage with others constructively and in good faith.

I must admit, I feel saddened by your dismissiveness of certain 'queer people'. You have no idea who I am, what my identity is, and yet you so casually dismiss members of the marginalised group you purport to be defending. How callous of you.

Perhaps the reason I can so easily dismiss your hysterical claim that HN is unsafe is that - in my day - 'unsafe for queer people' meant 'reasonable likelihood of getting a brick to the face', and not 'seeing words online you don't agree with'.

◧◩◪◨⬒⬓⬔
8. asmor+dj1[view] [source] 2023-06-07 19:14:33
>>troad+yc1
this is very dismissive for how much you're projecting i'm dismissing you. it's okay if you can't relate to me, just don't assume you understand.

hn is unsafe in the way that it provides zero control over what you have submitted and a perfect history of your posts, mostly set in stone unless you email an administrator. at least reddit lets you self-service delete posts.

those are perfect conditions for a certain kind of group that spend way too much time digging up and correlating info to then start harassment campaigns that exceed 'seeing words online you don't agree with' quite often.

you can of course now go on to scold me and others with this problem about how we need to up our opsec or shouldn't post in the first place. i find such arguments, if you were to make them, entirely unconvincing. being aware of your risk profile is one thing, shifting all the blame for making it harder to retroactively rectify little pieces of information (these people found a place from a blurry 500x500 picture of a parking lot out a window) on the user is just a bad excuse for shitty UX.

◧◩◪◨⬒⬓⬔⧯
9. troad+Ku1[view] [source] 2023-06-07 20:01:37
>>asmor+dj1
> you can of course now go on to scold me and others with this problem about how we need to up our opsec or shouldn't post in the first place

Not at all. I neither think you should up your opsec nor avoid posting. I think you should be unabashed of what you have to say. I also think you should hear out others doing the same, generously and in good faith.

That tiny minority who harass and abuse queer people today? That used to be virtually everybody, all the time, everywhere you'd go.

The only reason queer rights are where they are today is because people weren't afraid to speak up, even when they had every right to be. When coming out meant admitting to criminal acts - proclaiming them in public, no less. Had they not put themselves out there - had they refused to speak to those that didn't already agree with them - this would be a much darker world, and your definition of 'unsafe' would be a lot more visceral.

People used to march, faces out in the open, in their small towns, for their rights, past neighbours who hated them. That's what 'unsafe for queer people' means. I'm just never going to be able to see 'people disagree with me online sometimes' as being in any way comparable.

[go to top]