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