movim

from https://github.com/movim/movim/issues/63 >"edhelas commented Nov 26, 2021 As OMEMO is now part of Movim master and that the main working features are working I'm considering this ticket as solved. There is still a lot of small things to fix but the main is done. It took 6 years but Movim is finally having end to end encryptio edhelas commented Nov 26, 2021 As OMEMO is now part of Movim master and that the main working features are working I'm considering this ticket as solved. There is still a lot of small things to fix but the main is done. It took 6 years but Movim is finally having end to end encryption."

Damn React is complicated. I added Dark mode in my app in a few lines of CSS (https://github.com/movim/movim/blob/master/public/theme/css/...) and used the variables across the whole code. I just have to toggle a class on the body and boom, it works. Guys, you don't need all that JS, seriously. It's slow, it's useless most of the time. And in the end you have to spend hours for something so simple. Theming the colors of your website is the role of one tech: CSS. That's it, you don't needs layers and layers of Javascript to change that. Let's go back to server side rendering, a bit of HTML + CSS and JS and we're done.

XMPP is a lot like email. There is no money in it and it has warts simply due to the fact that it is a widely implemented standard. You use it mostly because it is a well developed standard with lots of support. I don't know what it would mean for it to become "popular". How would you tell? All you can know is what your friends are using. An IM protocol is a silo... There is a lot of interesting XMPP stuff happening right now with respect to the currently hot topic of privacy which could affect XMPP popularity. There are over a hundred known public XMPP servers last I looked. Due to Let's Encrypt those servers are now encrypting the server to server and client to server links in a meaningful way. The encryption from Signal has been integrated into XMPP with OMEMO. This suddenly makes XMPP a lot more interesting in terms of privacy. The cl

Any XML parser that I know can parse XML in a stream, that's all you need to handle an incoming XMPP stream. Just an example, here is the XML parser that I wrote in PHP https://github.com/movim/movim/blob/master/lib/moxl/src/Moxl... (127 lines), it basically handle the stream as an input and fire SimpleXML (can also be DOM XML) on the other hand. This can handle thousands of XMPP messages (called stanza) per second :)

I've created a ticket for it https://github.com/movim/movim/issues/738.

This message was initially added more than 5 years ago and not really changed since then :) The related ticket has been fixed and master is now having a better wording for this message https://github.com/movim/movim/issues/737.

A ticket is now open for it :) https://github.com/movim/movim/issues/737 Will be fixed in the next release.

What bothers me the most with the current on-premises chat solutions is the lack of a true alternative for jabber/xmpp with OTR (or equivalent e2e encryption) support. I honestly hate that in 2018 there is no way to move away from Pidgin/Adium if you want to keep this functionality. - RocketChat - OTR breaks very easily, and https://github.com/RocketChat/Rocket.Chat/pull/10094 has been open for months - Matrix / Riot - Last I tried it had the most complex and unusable interface - Mattermost - At first glance seems to include E2E, but when reading a little bit more...not really, just at rest encryption - https://mattermost.atlassian.net/browse/MM-669 - Zulip - nop - https://github.com/zulip/zulip/issues/6096 - Movim - nop - https://github.com/movim/movim/issues/63 ...