/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.

@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.

This!!!

I'd add that I've recently unfollowed GOS precisely because almost every single interaction of theirs seems to have been negative. Even if it's correcting misinformation.
Now every time I see a GOS toot I think to myself "great, GOS drama again." I don't need that in my life.

@[email protected]'s suggestions were on point. I suggest you take them to heart.

P.S.: thanks for making GOS :)
~happy GOS user

CC: @[email protected] @[email protected]

@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.

Mastodon is a microblogging platform so it somewhat makes sense for it to enforce a character limit. That being said, I agree that 500 characters is not a lot, especially for what GOS does.

Well, there are Mastodon forks, like glitch-soc or hometown, which do indeed have a modifiable character limit. And it seems that migrating to one isn't too difficult.
So there's a solution. Either GOS is unaware of it, or they chose not to go this route.

CC: @[email protected]

@me @GrapheneOS

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.