Now all of my close friends, with whom I chat regularly, are on #xmpp! I'll be trying to get some more people. I had to distribute the Conversations app directly to them as they were unlikely to install "one more app" (viz. f-droid) to install Conversations.

I try not to mention the word "xmpp", instead I say "Just install Conversations". As hearing the word "xmpp" will probably scare them as well.

#xmpp
in reply to Abhiseck Paira :gnu:

Congratulations, lucky you! 👍🥳
I noticed a unique(?) XMPP feature that some people are interested in is the REAL multi device support (ie being useable after losing ones phone). Unfortunately, most of them use Windows which I don't know any good clients for. Can you recommend a Windows XMPP client that is simple and easy to use and supports OMEMO? Something like Dino but for Windows will probably do. Gajim and PSI+ seem to be a bit too complicated 🤔
#xmpp #windows
in reply to met

@met

Conversations uses encryption by default in private chats. It provides two choices for group chat (i.e MUCs in xmpp terminology, but users will never know they are called that!), "public channel" and "private group chats". Hopefully these names make it clear that they need to choose "private group chat" for e2ee group chat. Conversations takes care of everything for the user. So, I think non techie people will not have any problem.

In Desktop clients, I have only tried Dino and ConverseJS. Dino doesn't encrypt by default but places an open padlock icon right beside the message typing window (and clicking it enables encryption), but starting group chats (MUCs) is very involved.

Group creation with ConverseJS is easier but to get what people are used to with something like WhatsApp, and get encryption, few switches needs to be toggled which will seem unrelated to group encryption.

@met
in reply to Abhiseck Paira :gnu:

The media in this post is not displayed to visitors. To view it, please go to the original post.

@met @dino will soon be able to encrypt by default with a setting fosstodon.org/@fiaxh@mastodon.… Hopefully making this the default soon like Conversations.


Over the last months, we've completely redesigned and rewritten @dino 's accounts and settings dialogs. The dialogs are combined into a single one now, which is adaptive and offers additional features like an option for OMEMO by default. The rewrite also resolves a number of issues and feature requests that were raised with the old implementation. It's still work in progress and will require further polishing.

#dino #xmpp #gtk #libadwaita


@Dino @met
in reply to Abhiseck Paira :gnu:

@cosmin You could send them a diasp.in invite. Though they have to sign up with a web browser and then login with an app for now. Hopefully we can make this easier soon. We are also working on @prav which will combine app + service, but we are still in beta. If using phone number as a username is fine, then Quicksy would be easier for people, it is available on Play Store and they just need to enter phone number and contacts will be discovered automatically.
in reply to Pirate Praveen 普拉文

@cosmin @prav Just adding, we hope to be able to enable sign up by invitation in diasp.in soon. Following blog.prosody.im/great-invitati… and creating a new virtual host on our prosody server (durare.org). Users will be able to generate an invite link and share with contacts. Then just clicking on the link contacts can join XMPP (app and provider will be selected automatically).
Unknown parent

mastodon - Collegamento all'originale

Pirate Praveen 普拉文

@prav @cosmin Quicksy and Conversations should be identical in that situation (only difference in sign up and contacts discovery - otherwise both share the same code). Prav is still in beta and we are trying to fix the SMS problem. May be that is a temporary error due to network issues. Are you still not able to send messages ? If you are still not able to send message, please report a bug.
in reply to Pirate Praveen 普拉文

@prav @cosmin Thanks to @akshay we found out the root cause of SMS not sending - we had configure Prav server to listen only on ipv4 interface so ipv6 requests were going directly to ejabberd (the SMS verification logic is handled by prav server and only prav server can create account in ejabberd after verification). I just confirmed SMS OTP is working on my phone (which was not working earlier). So please try signing up now.
in reply to Kari'boka

@Kari'boka @Abhiseck Paira :gnu: :gnuhurd: I have prosody instead of ejabberd, but I believe it would be similar.

I have ~20 users most of which love cats :D , a strict limit on http uploads (5 MB and they get deleted after 30 days) and mod_mam / mod_muc_mam are configured with the default where messages are deleted after one week.

This was done mostly for privacy (I don't want to keep any personal data for longer than is required for people to download stuff on their multiple devices), but of course has the side effect of keeping the requirements light.

My prosody storage directory right now is 358MB, of which 335MB are in the http_upload directory.

edit: I'm specifying I'm using prosody because I'm using prosody's names for the configurations, but I believe that ejabberd has all of the equivalent features.

Questo sito utilizza cookie per riconosce gli utenti loggati e quelli che tornano a visitare. Proseguendo la navigazione su questo sito, accetti l'utilizzo di questi cookie.