instead of trying to write out a long commentary about #ThriveMessenger and its growing pains, I'm just going to paste some quotes from one if its "developers":

1. "But here's the thing, your attitude honestly raises the question, if you're so bothered about messages not being seen, does that mean you have something to hide? Like literally, you're freaking out all because there's currently no end to end encryption, like that looks so sus dude."
2. "@... Oh I don't know, looks like there's some fucking idiot who has something to hide otherwise he wouldn't be causing such a scene, oh and he brought up the password drama again, I swear to god some people don't know when to drop it, and its anoying."
3. "if people really wanna know whether AI has helped they can ask, the only problem with mentioning that in the readme is it turns some people off, and I don't wanna contribute to people's mindset of oh its AI, fuck that, mentality."
4. "Dude, no one even accessed those passwords, so you're just making a scene out of nothing, so stop wasting my fucking time and get a grip!"
5. "ahem, Discord doesn't have E2EE, so shut the fuck up!"
6. "I'm not, quote unquote, throwing tantrums. I'm saying this is an early alpha, its right there in the releases, alpha, alpha, alpha."

I work in the music industry and write music for clients. As a result it's sometimes necessary for the client to give me direction. I may not like it, but I'm not paid to like it, I'm paid to do it. I can gently suggest that hey, you might wanna try this or this, but if they say no, the answer's no.
Now when you're making a product that contains sensitive data, *especially* passwords where the habit is often to reuse across various services, and you're unknown, untested and your users are asking questions, you don't shoot them down. You never, ever shoot them down. You explain calmly and carefully that 'Yes I am indeed taking your concerns seriously. Yes, your passwords are safe. Yes, your data is encrypted.'

I'm just gonna leave that here.