this post was submitted on 14 Nov 2021
2 points (75.0% liked)

AndroidApps

1433 readers
1 users here now

Community dedicated to Android apps and software.

Related Communities:

Rules:

spoiler0. Use common sense.

  1. No distribution of APKs from unknown sources or direct downloads. You are only allowed to share from GitHub (no direct links, repo only), Play Store, F-Droid, or Aurora Store.
  2. No piracy. This includes hacking, cracking in-app purchases or bypassing forms of DRM. YouTube (Music) Vanced are allowed exceptions to this.
  3. No rooting apps allowed. This also includes hacking software or tools.
  4. No apps that require root to function. This also includes Magisk and Magisk-related software. However: If the app features extra functionality that is available if you are rooted, but it is not required to use the app it is then okay. I.e. YouTube Vanced does not require root, but it features stuff that works only with root.
  5. No software that requires ADB or patching system files. Exceptions are well-known debloaters such as UAD and other manually approved stuff. Otherwise, ADB is not a user-friendly or safe tool and discourage its usage here.

These rules are subject to change at any point in time with or without user notice.

founded 3 years ago
MODERATORS
 

crossposted from here: https://lemmy.eus/post/10482


I believe that XMPP is one of the best protocols for chat communications there is, and I stand up for it. However, the clients that there are, are not comfortable for most people out there used to apps like Telegram, Whatsapp or whatever.

One can defend current XMPP clients saying that quoting with "> " is the traditional way, or that swiping to quote a message is not worth developing; I have plenty more examples like this.
Well, if you think so, OK, use those clients for yourself, but become aware that many people won't use XMPP for just this reason.

After saying all this, I want to tell that I am willing to develop a new, modern looking and comfortable client for XMPP. I think of a client for Android in first instance, but I would have no problem on going further.

However, I don't know programming, so I'm searching programmers who would like to get involved in this.
Although I'm not programmer, I have experience developing software projects, from internationalization to documentation, including ideas about features, testing and all other work there can be.

Will you help me spreading the word? :)

top 6 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 1 year ago (1 children)

There is already such a project you might want to contribute to rather: https://moxxy.org/

Conversations is also getting a major UI overhaul right now and the new version should be released later this year.

[–] [email protected] 0 points 1 year ago (1 children)

Wow, this looks great! Thank you!! I didn't know Conversations was getting an UI overhaul, lets see it

The client-sync issue, also with encryption, wouldn't get solved with these news, right??

[–] [email protected] 0 points 1 year ago (1 children)

I don't have any such sync issues. Maybe a problem with your XMPP server?

[–] [email protected] 0 points 1 year ago (1 children)

Oh, many people around me have them! I didn't consider the server could be the problem. Using Dino on the computer and Conversations on the phone, the are usually problems either with sync or more frequently with de-encrypting

[–] [email protected] 1 points 1 year ago (1 children)

e2e encryption could be more user-friendly indeed, but it is nearly always an user-error and not anything wrong with the clients or the servers. It also largely boils down to expectation management. The way e2ee is implemented in XMPP is trying to maximize security and not usability. So some things people get annoyed about like not being able to decrypt old message history on new devices is a security feature.

IMHO people need to also realize that e2ee is largely snake-oil by the large centralized providers like Signal and WhatsApp to pull the blanket over the the eyes of users that it does not really prevent the meta-data collection on centralized systems. If you communicate via a trusted server then TLS encryption is usually fully sufficient and much less prone to user errors or other issues.

[–] [email protected] 1 points 1 year ago

You're totally right, the problem is with e2ee, and it is so by design. Great answer, thanks a lot