Are those USB naming schemes, or edgy usernames from 2000s like xXx_31Gen3x1HardCore_xXx?

I am so sorry, man. No one deserves this.

I scream silently everytime.

And then there’s .net classic and .net core. Making up two entirely separate names shouldn’t be difficult for marketing executives.

That’s true. They must have gained access to the phone itself somehow.

Perhaps they simply took out the sim card and inserted into another phone, giving them access to contacts (that could have been saved into the chip instead of the original phone)?

iddqd was a well known cheat code from the era, not exactly obscure if not contemporary.

And to think, the Q shit started on these sites.

What about XFCE users?

Come on. What are you, fifteen?

I support democratization of PRC and justice for all activists suffering under CCP’s opression. That doesn’t mean I’ll join a lynch mob after an internet comedian who dared to protect his own life and of his family.

Sure, everyone must become a martyr for the noble cause and sacrifice their entire career so you can conveniently upvote and move along to the next meme. Fucking A+ 5/5 gr8 b8 m8

In a similar situation as you (entire society revolves around whatsapp). I came to this conclusion:

1. Others won’t share my view on personal privacy at all will happily give out any metadata or data. No matter what secure channel we use, the destination (people) will always leak.

2. Because of (1), consider all communication with others as public, no matter the inferred intimacy, no matter the platform or its security.

3. Consider (2) as true even if they somehow used Signal or any secure platform, because of (1). (E.g. “Hey, did you hear about $familyMember? Yes, the weird kiddo who forced me to use some strange blue shit for chat. He got positive on blood exam for $badCondition. Go check on him”)

As for whatsapp itself, i use Android and isolate it in a separate profile, also frozen until opened. I also used a burner phone number for account registration, not my actual number.

People are more receptive of whatsapp accounts with “alternate” numbers when you explain you “got hacked in the past” or any plausible reason.

In Korean we have these conjugated forms. They both sound the same:

1. 나아 [na.a] (from 낫다) be/become better
2. 낳아 [na.a] (from 낳다) give birth (to a baby)

So when given A as an example:

(A) 감기에 걸렸어요. I got a cold.
(B) 빨리 나으세요! Hope you get better soon!
© 빨리 낳으세요! Hope you give birth soon!

For some reason Koreans across all ages write C instead of B by mistake. It became a national joke at this point and some do it ironically on purpose. I used to teach Korean. Imagine my face every time.

There are more but I’m on my phone. Will do more later.

Confusing between hay‐ay is at least understandable (forgetting the letter). Confusing between hay-ahí is what makes my blood boil.

I would have loved this as a drunk college kid at 2 am.

Its the same for all East Asian countries as well, but I guess slapping JAPAN on it means fast upvotes, like that "Place, Japan" meme.

What if I use Debian but with backports and flatpak for apps that need fast updates?

I see. The authorized-app-only approach was deal breaker in my case, as I needed imap/smtp. Hope it works for you well.

Remember that banking and finance is full of regulations, and have moving speed of snail. Opposite of IT. When asked for something like this (open source or cross compatibility or anything nerdy) the first question is “who will be liable for losses and damages when something breaks?”.

Liability is probably the biggest factor. When something isn’t working properly, they want to be able to point fingers at someone and blame them. The vendor then blames someone else. Open source tends to be the polar opposite, which means huge red flags - hippie stuff, no payment, no liability, no pointy-blaming game.

Or so I’ve heard from people working in that sector. For places as conservative as them to deploy FOSS solutions, you’ll need the government branches cooperating with clearly worded laws and regulations, dragging them kicking and screaming into adoption.

And that’s assuming no one will lobby against in the process.

There shouldn’t be, but that doesn’t mean it cannot be enhanced. Hopefully a popular feature from an extension can become integrated into official web clients.