Signal feed
Post
Remote status
The only reason infosec.exchange isn't defederated is from grapheneos.social is because it's too big to fail.
infosec.exchange has very consistently failed to address rampant libel and harassment directed towards our team from their instance.
At one point, the admin of the instance publicly posted we'd reported harassment with details and asked for feedback which acted as a rallying cry for people engaged in these attacks. None was addressed. We stopped filing reports of harassment to them.
Replies
7@GrapheneOS federation social media failed and you are prime example of it. You see libel and harassment everywhere and you want to isolate almost from everyone.
Fediverse is a bunch of servers that claim they want to communicate with others, but use defederation banlists or shadow bans to remove anyone with different views.
This results in bunch of small isolated bubbles moderated by people with extremist views, where it is impossible to follow everybody you want to follow.
@RyszardD infosec.exchange has a massive instance blocklist far larger than ours. The admin of the instance responded to a valid report about someone calling our founder insane and delusional clearly in reference in harassment content by publicly posting about it asking for input and then being supportive of people linking harassment content. He also leaked our private messages to the person we reported. We want those nasty replies removed and for them to be asked to stop, that's all.
@GrapheneOS "someone calling our founder insane and delusional".
1. That is just a stupid opinion, not harassment. It's very mild. Just ignore it. It's not a valid report of harassment.
2. Everybody knows that it's you Daniel, you write most of the stuff using the main gos accounts.
3. Most of this stupid opinions would go unnoticed, but you boost it by responding to it and creating drama.
@RyszardD It is harassment and infosec.exchange defederates instances for permitting much less than that. It's part a bunch of libel and harassment directed towards us from their instance and elsewhere. Reporting one case of it led to the admin of the instance publicizing it and taking feedback which involved people sharing a bunch of fabricated stories and harassment content. The moderation action they claimed to take was actually undone and our private DMs were leaked to the person doing it.
Its very hard not to see the blatant double-standard against @GrapheneOS here.
I can't help but notice there is a noticeable trend of "mainstream tech privacy spaces" essentially working to memory-hole gOS in a time where few projects are capable, nevermind willing to put up a fight against world wide legislative attacks on digital privacy and independence.
I'll just say that the behavior while regrettable, fits a pattern I've seen in people under (actual) attack. Eventually it escalates to the point where the person can't distinguish friend and foe, which reliably creates a pretty ugly doom spiral.
But what stands out to me is that because of this and other things he is 'fair game' to be targeted with tactics the same people would never tolerate against other 'fellow travelers' and certainly not other tech projects.
In short I don't think the solution to (justified or totally imagined) persecution complexes is to reinforce them with retaliation.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
