Misinformation was rife as the wildfires spread across Los Angeles last month, and that wasn’t just happening in English language media. For @thexylom, Aorui Pi explains how platforms like WeChat and RedNote served as a vector for fake news, which may have made life harder for Chinese immigrants living in fire-affected areas.

https://www.thexylom.com/post/how-unverified-claims-about-the-la-wildfires-spread-across-chinese-language-media

@deepseek_ai @fdroidorg @exodus There are also a lot of static + dynamic traces of SDKs associated with China such as #wechat / qq and volcengine.com These are disclosed by #DeepSeek in the app code and their website. Here is the machine translated version and original. https://psafe.ly/6xznZm

@MastoDenunzianten @monocles

Natürlich kannste der #Desinformation von #Diensteanbietern glauben, aber dann ist #WhatsApp auch #E2EE weil die #SSL nutzen (und mit der Logik auch #WeChat & #QQ - lol)!

• Ernsthaft, es gibt nen Grund warum #XMPP+#OMEMO & #PGP/MIME bis heute sich halten und proprietäre shice alla #MSN & #ICQ tot ist.

Gerade weil wirkliche #InfoSec & #OpSec sowie #ComSec & #ITsec nur mit #Transparenz geht.

• Ich vertrau' prinzipiell keinem Code oder Anbieter...

@xoron I don't want to discourage you at all - in fact I think your goal is not just noble but also worth aspiring to.

• My recommendation is always to scout out existing solutions, protocols and standards and see if those can be salvaged / used and if not, reason why. #PGP/MIME may seem crusty but a good UI can make it easy. Same.goes for #OMEMO & #OTR...

But whatever you do, please "DO NOT DIY ENCRYPTION!"

• Instead delegate it to drop-in libraries (i.e. crypto++ for C++) that are well, maintained and getting audited.

Prioritize features early on and make a decision what you want and if/how these can be accomplished. If necessary, have different modes / functions one has to context-switch (i.e. videocalling can't work in an airgapped network unless your callers are in the same (W)LAN).

• If possible choose to stay platform-independent in terms of tech, so like #WebCall, #JitsiMeet, etc. you can simply package that up with nw.js... (Except if you need like a minimalist, (n)curses-style TUI tool like #enc)

User-test early on. Espechally with "#TechIlliterates", if you can.

• Focus on a #MVP (minimum viable product) early on.

Write #documentation early on since that'll remove headaches. And I don't just mean #CommentYourCode but go deep and explain in detail why you chose something. This will help not just you.

• In terms of "scouting existing solutions" I'd recommend to take a look not just at #JitsiMeet & #WebCall, but also #Briar, #ServalMesh, @monocles / #monoclesChat, @gajim / #gajim and @micahflee's #OnionShare.

Make yourself a list what you like and dislike from those.

• Same with #Linphone, @zulip / #Zulip, #WhatsApp, #Signal, #Threema and even #WeChat, #FacebookMessenger, #iMessage, #FaceTime and god forbid #Skype, #MicrosoftTeams as well as #Slack.

Don't be afraid if your #App can't tick all the boxes at first release. Rather feel free to slowly ibtegrate them.

Needless to say I do sincerely wish you good luck and only the best in terms of success.

@w7voa I don't think that matters anymore, since everyone can now snap into X and create V (Voltron) except it's going to be more like Superman with a dose of dirty krypto, think #superman3

Haven't you ever heard them fawn over China's #wechat before? This is what it's all about folks. You asked for it!

@kestutisk_ @aurimas @Ovidijus @donceee

10 valandų darbo pas ?

Nes aš turiu porą komunitų iš #wechat'e, tai kada neparašau 24h, visad atrašo per porą minučių. Kartais galvoju, kad ten po vienu asmeniu, gal keli žmogeliukai sėdi Nors yra siuntęs savo šeimos nuotraukas, tipo asmeninė paskyra.