danhakimi

whatsapp for family, because that's where family is.

nobody uses facebook to connect with family, they use facebook to connect with people from high school they haven't seen in 15 years and don't care enough about to actually keep in touch.

wait, is "buddy" gendered?

I like to mix it up. but language is context dependent. "buddy" is a go-to of mine, and feels entirely gender neutral.

"my people" is good for plural.

"friend" is good as long as you have the right rhythm with it. Like, you know, in the second person, like "hello, friend."

"bro" obviously doesn't work, but I have casually referred to trans friends as "broham" and they didn't seem to mind. I don't do it often, but sometimes mixing in a good bro pun is more fun that way... go a little over the top, call somebody brobrahk brobrahma, nobody's going to be thinking that you're implying gender, it's an equally ridiculous term to call anybody by. Similarly, although context dependent, there are implicitly feminine words you can use, although some of them can be degrading in the wrong context. "Gurl," "bitch," and "slut" can work, as long as it's ridiculous enough in context not to be taken seriously. I'm a guy, I've had friends call me these. "Gurl" might not be the best for a nonbinary friend or a trans man friend, so be careful with it.

I don't know, I only have a few nonbinary friends, I guess, and I mostly refer to most of them by their names.

in addition to you being an asshole, you're also wrong in practice about how HR teams work. If they hear about shit like this, they really do try to do something about it. Sometimes they can't really accomplish anything, and they're just bureaucratic about it, but no, they do not think of the person making the report as a problem, they think about the person actually causing the actual problem. Hostile work environments are unproductive, are bad for employee retention, and have a heightened risk of law suit. Only shitty businesspeople think the problem doesn't exist as long as it's not on paper.

OP's better off if their employees steer clear of them—that much is obvious, isn't it?

op mentioned the DSA...

well I said "would." It's not a moral issue, it's just confusing that people find this compelling. It doesn't quite seem like a collaborative artistic experience. It seems more like just bad tech.

I don't understand why this would exist over noscript + using the websites you actually want to use. If you want to spend time on minimal websites, there's no reason you can't use html and http to do it.

it looks like this was a college student's weekend hacking project and some people took it way too seriously and now have this social idea about how intentionally inferior tech is going to revolutionize... devolutionize? the internet. This is not snapchat. This is cave painting.

why?

I'd say the spiderverse movies are significantly better than the original trilogy.

If you are willing and able to enter a partnership like Samsung, you can do it fully (including encryption support etc).

Samsung can interoperate. We cannot. We cannot enter into partnerships with Google. We are people, Samsung is a massive corporation. You understand the difference, right? Google will not let us access their servers. They're not making it difficult, they're not making it possible at all.

you don't just need to support the protocol, you need a server to communicate with your client, and Google is not here to federate its RCS service with Bob's summer Github project.

Matrix is the federated messaging network. It's also end to end encrypted, although people have pointed out issues with server security and with metadata—which is why they're working on peer to peer tech.

RCS is not similar to any federated technology at all. It's operated exclusively by Google in the US and most other countries. The technology was created, from the ground up, for carriers. But even carriers couldn't actually make it work in practice, so they asked Google to take over. It's a fucking albatross. We, as a society, need to drop it.

Google is the exclusive RCS provider for all carriers in the US and many other countries. The desire for an AOSP android API is for developers to be able to write clients the way they do SMS clients, not to replace Google's servers—that's a pipe dream. IIRC, Google actually helped Samsung develop RCS support in their app. I'm not sure why it's so difficult to implement.