@GrapheneOS It's great you're taking time to clear up factually incorrect claims, whether they're made out of maliciousness or naivety. Constructive community engagement is great!
But please, for the love of god, this information only belongs A) in the threads where factually incorrect claims are being made and B) on your website in the FAQ section.
I know it's not intuitive, but pushing conflict into everyone's face again and again makes your project seem *less* trustworthy, not more.
@GrapheneOS
> We're aware it results in /e/ and Murena doubling down on attacks. We're also aware that it results in their supporters doubling down on attacks. These will be addressed with additional posts.
I.. don't know if attempting to fight fire with fire is a reasonable investment of the team's time. It's not your goal to find every instance of a false claim to debunk it, right?
@GrapheneOS If you must reply to individual threads yourself, you could probably save lots of time by having an evergreen section on your website dedicated to debunking FUD and just linking to that. There's little point in formulating individual responses on very similar topics repeatedly. Either a person is open to look at new information without prejudice, or they're not.
You have more important work to do.. and you know it :P
Not trying to be harsh, I want you guys to succeed!
Those who spread misinfo make individual posts and shove it in peoples faces. GOS is allowed to make posts about topics that pertain to them, especially if they are to point out harm and abuse.
@me @tastyraspberry @GrapheneOS
What a horribly apathetic thing to say. They wouldnt respond to abuse if they werent being abused.
@HybridStaticAnimate @me @tastyraspberry @GrapheneOS
The same here, I only scroll my home feed till the first of 30 posts clarifying again that eOS is bad. This should be considered spam. I don’t even know what is GOS referencing at this point. Is it new eOS attack every time? Is their CEO constantly posting shit about GOS?
@dwaem @me @tastyraspberry @GrapheneOS
Its really hard to cram technical refutation into Mastodons comically small default word limit, thats all.
GOS has long-form posts on Twitter. Mastodon should make an easy way to increase the limit.
A lot of projects do, unprovoked, make attacks at GOS. Its not drama or beef, its malice. This is what causes GOS to defend themselves. Its very unfortunate GOS is subjected to this abuse and it should stop.
They choose not to for various reasons including expanding trust and consuming more resources, and this method currently works anyway. But they would change it if Mastodon unified the value and made it easy to change.
@richlv @dwaem @me @tastyraspberry @GrapheneOS
The issue is that puts the corrections and refutations in a place people are explicitly being conditioned to avoid with the misinformation. A mix of both a post on the GOS discussion forum and refutations on Mastodon seem to work the best. But writing up a huge response on the forum takes a lot of time, and many replies have to be context specific.
@richlv @dwaem @me @tastyraspberry @GrapheneOS
Lying is so much easier than telling the truth. Its also easier to trick someone than to convince them they have been tricked. Large posts are needed because much of what GrapheneOS does is very technical and/or very involved, on the tech side, or an issue needing a ton of context and evidence on the community/social side. There isnt much of a choice other than huge post.
@richlv @me @dwaem @tastyraspberry @GrapheneOS
GOS regularly posts evidence with their claims.
https://grapheneos.social/@GrapheneOS/116388159407099477
Heres more info.
/e/ and Murena have been been promoting their products by misleading people about GrapheneOS for years. This has turned into an all out war on GrapheneOS by their company and supporters. We began regularly debunking their inaccurate claims and they try to frame it as aggression.