Skip to main content

Cerca

Elementi taggati con: jsxc


 

The rocky road to OMEMO by default



Daniel Gultsch, developer of Android XMPP client Conversations, writes,

Why it took us more than two years to enable End-to-End encryption by default: The first in a series of essays leading up to the release of Conversations 2.0



...
The other big hurdle we had to overcome was the adoption rate in clients. If you send OMEMO encrypted messages by default you should have a reasonable expectation that your contact will be able to decrypt the message. Reasonable expectation doesn’t mean that every single client out there has to support it—In an ecosystem with hundreds of small, badly maintained clients that’s just not feasible—but the major clients should at least have a plugin available.
In March 2018 we finally reached the point where every plattform has one or more clients with OMEMO support. Conversations and Zom on Android, ChatSecure on iOS, Psi and Gajim on the desktop. The up and coming desktop client Dino—despite not having had an initial release—already has support for OMEMO as well. And even the webclient JSXC has a plugin available.
Considering the complexity of OMEMO and the fact that most of these clients are developed by people in their spare time, this is actually quite an impressive adoption rate.
...
Moxie Marlinspike, in his 2016 propaganda piece ignorantly bashing XMPP, had one valid point: Enabling end-to-end encryption in a homogenous environment is easier than introducing it in a heterogenous one like Jabber. Nobody is denying that. However, if something is hard to achieve there are two possible approaches: Either try your best and don’t give up, or put your head in the sand and create yet another walled garden that is no different from other proprietary solutions.
Admittedly it has taken us a while to get to a point where we can enable end-to-end encryption by default, but it was worth the effort in that we ended up with something that is different from WhatsApp in more than just marketing.
#xmpp #omemo #conversations #psi #gajim #zom #chatsecure #dino #jsxc #federation #encryption

 

FreedomBox v0.11.0 Released



From: https://lists.alioth.debian.org/pipermail/freedombox-discuss/2016-October/007656.html

For more information about FreedomBox: https://wiki.debian.org/FreedomBox
Plinth v0.11.0 has been released, and is now available in Debian unstable. It should appear in testing in about 3 days.

One major change in this release is that the #XMPP web client, #JWChat, has been replaced by #JSXC. This one has a more modern appearance, and is being actively maintained.

We have also added a "front page" to Plinth, that has shortcuts to enabled web apps, and displays information about enabled services. Please try out these new features and share any feedback that you have.

Here are some more changes included in this release:
  • Added loading icon for additional busy operations.
  • networks: Add batctl as dependency, required for #batman-adv #mesh networking.
  • users:
    • Fixed checking restricted usernames.
    • Display error message if unable to set SSH keys.
    • Flush nscd cache after user operations to avoid some types of errors.
  • #monkeysphere:
    • Adopted to using SHA256 fingerprints.
    • Sort items for consistent display.
    • Handle new uid format of gpg2.
    • Fixed handling of unavailable imported domains.
  • #minetest: Fixed showing status block and diagnostics.
    • Fixed stretched favicon.
    • Switched base template from container-fluid to container. This will narrow the content area for larger displays.
  • Plinth is now able to run as "plinth" user instead of root user.
  • #ikiwiki: Allow only alphanumerics in wiki/blog name to avoid invalid paths.
Finally, #repro (#SIP server) is back in Debian testing now, and should be installable again.

#FBX #FreedomBox #Debian #FreeSoftware #Plinth

[Freedombox-discuss] Plinth v0.11.0 released