I think you got hit hard by Poe’s Law here. Except it’s more like people couldn’t tell if you were jokingly or genuinely getting your math wrong… Even after you explained you were joking lol

I would encourage people to code switch rather than adhere to one style of language over another in every case. Imho, it’s kind of problematic that language itself has become racialized in America to the point where people can actually be criticized or made fun of for speaking in the “wrong” style associated with their perceived ethnic background.

I think they’re great for giving OEMs extra incentive to ensure that Linux runs well on the hardware and providing consumers a slightly cheaper option. If I knew I wasn’t going to need Windows at all, I’d definitely go the Ubuntu route, but there’s software I use that doesn’t run on WINE, so I’d personally be more inclined to get a laptop with a Windows license bundled in.

By that logic, there’s nothing guaranteeing iMessage on iPhones is secure or private either because it’s closed source. If you don’t want to trust Beeper mini, you’ll be free to run their iMessage bridge on your own Matrix stack when they open source it at some point, which they’re promising to do (and you still won’t know that Apple isn’t scraping your messages on the iOS side). When I decide to trust a company, it’s because I look at what they’re transparently communicating to their end users. Every indication is that they are trying to get out of the middle of handling encrypted messages. Their first move to make this happen was allowing people to self host their own Beeper bridges (which you can still do with Beeper Cloud if you prefer and you will know that your messages are always encrypted within the Beeper infrastructure). They aren’t going to release the source for their client ever because that’s the only way they make any money.