@divyaranjan @fell @256 meanwhile consider #WebCall, #Linphone, #JitsiMeet, #NextcloudTalk, …

@ip6li habe grade auch nen Interview abgelehnt, weil #MicrosoftTeams geb' ich mir nicht!

• Ist ja nicht so als hätte ich denen gleich mehrere Alternativen angeboten von #SIP (#VoIP) über #WebRTC (#WebCall) und hätte im Bedarfsfalle sogar nen eigenen #JitsiMeet-Server aufgesetzt...

@debby #Mumble, #IRC, #XMPP (+OMEMO = @gajim / #monoclesChat) & #Linphone (#SIP / #VoIP) are the better options. #NextcloudTalk also exist and @monocles as well as @Stuxhost offer that.

• #Signal and #Session are #proprietary, #centralized, #SingleVendor & #SingleProvider solutions!

• And #Matrix is just a shittier #XMPP+#OMEMO. Give @delta / #DeltaChat a try instead.

OfC #JitsiMeet and #WebCall are also great!

https://webcall.timur.mobi

@KickDownCH nickt zustimmend

Gibt ohnehin bessere Optionen als #Skype seit langem..

Und damit meine ich nicht die nächste #Enshittification aka. #discord & #zoom, sondern #WebCall, #JitsiMeet, #NextcloudTalk, #SIP / #VoIP (#Linphone) ...

https://infosec.space/@kkarhan/114455612394610051

@theverge @tech-news-theverge yeah...

Meanwhile I recommend migrating to #WebRTC like #JitsiMeet, #WebCall and espechally classic #SIP / #VoIP like #Linphone!

• #Skype fucked up big time, but TBH it was #Microsoft doing #EmbraceExtendExtinguish instead that killed it!

@fuchsiii @puppygirlhornypost2 @kopper granted, #TechIlliterates & #Consoomers are just a bad standard to begin with and aligning with the bottom barrel is always gonna lower one's standard.

People need to realize there's not one perfect app.

• They can have multiple very good options that do their part or one shitty bloatware that does nothing even halfway acceptable.

The former are #IRC, #XMPP+#OMEMO, #WebCall, #OnionShare, #Linphone, #Mumble, …

The latter one are #MicrosoftTeams, #Discord, #QQ, #WeChat, #iMessage, #Signal, #Matrix, …

@ustralien and even then:

Modern #Codecs like #Speex and espechally #Opus really work great on #Mumble and other solutions like #WebCall and #SIP-Clients like #Linphone.

• Unless you're stuck on #Iridium, then #Codec2 is the only thing narrowband-efficient enough to work at all...

@herrorange Already existing options do that better than the old #SILK codec.

• #Linphone (#SIP client) supports #Opus & #Speex, which can do better at narrower bandwiths)

• #Codec2 OFC can work even on #Iridium-level bandwiths

• #Mumble, #WebCall & #JitsiMeet also do fine on #Skype-able bandwiths and don't require a T H I C C install on peoples' devices...

@leguinian_utopia seriously, people pay for #MicrosoftTeams when that shit is flakier than the first versions of #JitsiMeet, #Mumble & #WebCall together?

• WHY?

@Yuvalne consider #NextcloudTalk (included in @nextcloud / #Nextcloud as hosted by @monocles and @Stuxhost ) as well as #JitsiMeet (which is even easier to #SelfHost.

• If you only need 1:1 #Videocalling, consider #WebCall as a secure alternative.

All 3 use #WebRTC and don't require any shitty #Client #Installation whatsoever: They work from any modern #Browser like #Firefox!

@cwebber yes, and we already have options for that:

• #IRC & #XMPP+#OMEMO, #Zulip, etc. for #Chat.

• #JitsiMeet, #WebCall and other #WebRTC-based comms.

• #Mumbke, #SIP and other #VoIP solutions.

• #OnionShare, #Wormhole, #oshi, #BitTorrent & #IPFS for #Filesharing.

• #Nextcloud et. al. for collaboration.

...

@devSJR @raiden_fediverse @kuketzblog dabei sehe ich jene "Features" eher als #Bloat, weil's bessere Alternativen wie z.B. #WebCall für sichere Videotelefonie, existieren.

• Ewas, was alles kann, kann nix richtig!

@MartinaNeumayer @VixenBlu @thelusciouslibra Re: #eMail and #Chat, I'd still recommend to stick with #SelfCustody, and use @monocles #monoclesMail, #monoclesChat , @delta #deltaChat and many other options.

- One nifty option for #VideoTelephony one may want to look at is #WebCall:
https://timur.mobi/webcall/

I got pointed at it since it's very easy to use and unlike #JitsiMeet they don't demand #PII for registration or record stuff and one can #SelfHost it too...

@AdminKirsty @delta nodds in agreement

Add to that there are sufficient tools that allow for #secure, #E2EE #communication.

• Like: Even if they don't like #PGP/MIME there's nothing that prevents them from supporting #XMPP+#OMEMO or having any #secure means to communicate.

I do go out of my way to implement better alternatives to existing bad option...

• For example, #WebCall and #JitsiMeet alongside @zulip / #Zulip for companies that want or need some auditable and archival #Chat solution for internal use...

TBH, #unencrypted and thus #insecure communication should disqualify every #company and #organization as a matter or principle and it's high time #GDPR & #BDSG make support for proper #encryption mandatory, regardless if #2FA or general communications!

@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.

@xoron most of those features have already been implemented in #WebRTC-based solutions like #WebCall and #JitsiMert, abeit like with #XMPP+#OMEMO none does all of those things together, and that is somewhat an acceptable tradeoff...

@Mer__edith that's a #Marketing #Lie as @signalapp / #Signal collects and demands #PII like #PhoneNumbers to this day, and unlike #WebRTC-based options like #JitsiMeet and #WebCall, one cannot #SelfHost Signal!

So please stop such bs claims, because they insult the intellect of everyone who's even halfassing #ITsec, #InfoSec, #OpSec & #ComSec...

https://infosec.space/@kkarhan/113467293263701678

@signalapp Still doesn't come close to #JitsiMeet and #WebCall...