Jonkman Microblog
  • Login
Show Navigation

  • Public

    • Public
    • Network
    • Groups
    • Popular
    • People

Notices tagged with omemo, page 2

  1. TomaTuOrdenador (tomatuordenador@gnusocial.villanos.net)'s status on Thursday, 05-Apr-2018 02:34:47 EDT TomaTuOrdenador TomaTuOrdenador
    • An XMPP and Jabber related group
    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 https://gultsch.de/omemo_by_default.html?utm_medium=Newsletter&utm_source=xmppnewsletter

    !xmpp #OMEMO #Conversations
    In conversation Thursday, 05-Apr-2018 02:34:47 EDT from gnusocial.villanos.net permalink
  2. Rafael Bonifaz (rbonifaz@mastodon.social)'s status on Sunday, 01-Apr-2018 17:29:04 EDT Rafael Bonifaz Rafael Bonifaz

    De a poco voy entendiendo la diferencia entre #OTR y #OMEMO.
    1)OTR es independiente de lo que hay en el servidor
    2) OMEMO usa el protocolo de Signal que a su vez es una versión modificada OTR.
    3) Entre otras cosas OMEMO y signal funcionan mejor que OTR en chats asincrónicos

    In conversation Sunday, 01-Apr-2018 17:29:04 EDT from mastodon.social permalink
  3. Masoud Abkenar (masoud@aleph.land)'s status on Wednesday, 14-Mar-2018 17:55:55 EDT Masoud Abkenar Masoud Abkenar

    Moxie Marlinspike, in his 2016 propaganda piece ignorantly bashing #XMPP, had one valid point: Enabling end-to-end encryption in a homogeneous environment is easier than introducing it in a heterogeneous #Jabber. Nobody is denying that. However, if something is hard to achieve, 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.

    The rocky road to #OMEMO by default
    https://gultsch.de/omemo_by_default.html

    In conversation Wednesday, 14-Mar-2018 17:55:55 EDT from aleph.land permalink
  4. Klaus Jónsson Zimmermann (kzimmermann@quitter.se)'s status on Wednesday, 28-Feb-2018 02:05:49 EST Klaus Jónsson Zimmermann Klaus Jónsson Zimmermann
    • Privacy
    Dis my next project: http://qttr.at/22fq !privacy #OMEMO #XMPP
    In conversation Wednesday, 28-Feb-2018 02:05:49 EST from quitter.se permalink

    Attachments

    1. Invalid filename.
      ReneVolution/profanity-omemo-plugin
      from GitHub
      profanity-omemo-plugin - A Python plugin to use (axolotl / Signal Protocol) encryption for the profanity XMPP messenger
  5. Guillaume (postblue@herds.eu)'s status on Tuesday, 20-Feb-2018 19:42:47 EST Guillaume Guillaume
    • ❤ Bram ❤
    @bram RAM utilisé par Firefox avec un seul onglet sur riot.im et mes extensions qui ne servent à rien pour ce genre de navigation: ~500Mo. Riot Desktop: ~280Mo en comptant les deux processus Electron, et chez moi une impression de manque de réactivité du client (et ça trigger mon ventilo mais c'est une autre histoire, mon PC me fait beaucoup chier là dessus pour le moment). Pidgin ouvert avec un compte #XMPP et le plugin #OMEMO Lurch: 28Mo. Dino ouvert avec un compte XMPP et diffusion de mes clés GPG et OMEMO: 27Mo. J'ai vite choisi.
    In conversation Tuesday, 20-Feb-2018 19:42:47 EST from herds.eu permalink
  6. Klaus Jónsson Zimmermann (kzimmermann@quitter.se)'s status on Monday, 12-Feb-2018 20:42:48 EST Klaus Jónsson Zimmermann Klaus Jónsson Zimmermann
    • Today I Learned...
    Oh snap, !TIL that #Pidgin now also supports #OMEMO https://developer.pidgin.im/ticket/16801 Great that more messengers are adopting it!
    In conversation Monday, 12-Feb-2018 20:42:48 EST from quitter.se permalink
  7. GCU Prosthetic Conscience (gcupc@glitch.social)'s status on Tuesday, 16-Jan-2018 09:14:02 EST GCU Prosthetic Conscience GCU Prosthetic Conscience

    Are we OMEMO yet? Tracking #OMEMO support in #XMPP clients.

    https://omemo.top/

    (I wonder what the remaining issue with ChatSecure is? The tracking ticket is closed, apparently successfully.)

    In conversation Tuesday, 16-Jan-2018 09:14:02 EST from glitch.social permalink
  8. Muto 👁 (muto@social.tchncs.de)'s status on Saturday, 09-Dec-2017 06:19:23 EST Muto 👁 Muto 👁

    Finally, with the release of #Conversations 2.0 #OTR will be removed on March 24th, 2018

    https://twitter.com/iNPUTmice/status/939171488942436352
    #XMPP #OMEMO

    In conversation Saturday, 09-Dec-2017 06:19:23 EST from social.tchncs.de permalink
  9. Muto 👁 (muto@social.tchncs.de)'s status on Thursday, 26-Oct-2017 02:02:45 EDT Muto 👁 Muto 👁

    #ChatSecure v4.2.0 released
    improved group chat, performance and reliability
    https://chatsecure.org/blog/chatsecure-v42-group-chat/
    #xmpp #omemo

    In conversation Thursday, 26-Oct-2017 02:02:45 EDT from social.tchncs.de permalink

    Attachments

    1. File without filename could not get a thumbnail source.
      ChatSecure v4.2.0 - Group Chat
      from ChatSecure
      Free and open source encrypted chat for iOS.
  10. Bob Jonkman (bobjonkman@gs.jonkman.ca)'s status on Sunday, 15-Oct-2017 04:49:37 EDT Bob Jonkman Bob Jonkman
    This may be interesting: #Kontalk, based on !XMPP and encrypted https://www.kontalk.org/ I'm curious what they're using for E2E encryption, since #OMEMO is still being considered for addition.
    In conversation Sunday, 15-Oct-2017 04:49:37 EDT from web permalink
  11. rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk (rugk@gnusocial.de)'s status on Sunday, 08-Oct-2017 05:11:28 EDT rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
    The #xabber devs may get into legal trouble with Russian authorities when implementing #OMEMO support in their #XMPP client. https://github.com/redsolution/xabber-android/issues/540 https://gnusocial.de/attachment/4372134
    In conversation Sunday, 08-Oct-2017 05:11:28 EDT from gnusocial.de permalink
  12. Timur Demin (tdemin@mstdn.jp)'s status on Wednesday, 04-Oct-2017 11:17:18 EDT Timur Demin Timur Demin
    • ❦ Billy Blaze ❦

    @ckeen and thinking like this is the main reason folks won't use #XMPP with you. Having a client that does #OMEMO well just isn't enough😉
    https://tdemin.github.io/posts/2017-06-07-legacy-and-ux
    That's the reason I wrote this post.

    In conversation Wednesday, 04-Oct-2017 11:17:18 EDT from mstdn.jp permalink

    Attachments

    1. File without filename could not get a thumbnail source.
      How Legacy Compatibility Kills User Experience in Decentralized Environments
      from Timur Demin's Blog
      Moxie Marlinspike once said this is the nature of federated networks of being stuck in time. Is it the problem of the protocols, or is the problem underlying somewhere deeper?
  13. clacke (clacke@social.heldscal.la)'s status on Sunday, 24-Sep-2017 04:21:00 EDT clacke clacke
    • maiki
    Found "Are we OMEMO yet?", which illustrates the progress of and links to tracker issues regarding #OMEMO implementation in 41 #XMPP clients.

    https://omemo.top
    In conversation Sunday, 24-Sep-2017 04:21:00 EDT from social.heldscal.la permalink

    Attachments

    1. File without filename could not get a thumbnail source.
      Are we OMEMO yet?
      from Are we OMEMO yet?
      ?OTR:AAIDAAAAAAEAAAACAAAAwL2V…
  14. maiki (maiki@mastodon.sdf.org)'s status on Monday, 18-Sep-2017 18:43:49 EDT maiki maiki

    And #OMEMO is every important to me, as a user, but more so as a sysop!

    If I give my friends all the neat features, like synced messages and archives, I need to store it in a database. That means I can read the messages, and I don't like that.

    My peeps deserve to have private conversations without the wizard in the party being able to read it all.

    In conversation Monday, 18-Sep-2017 18:43:49 EDT from mastodon.sdf.org permalink
  15. Kontalk (kontalk@quitter.se)'s status on Sunday, 03-Sep-2017 16:52:11 EDT Kontalk Kontalk
    • Hans R. Logen
    @hanlo This is a minor version bump, one step at a time! For more on #OMEMO implementation, have a look at this post: http://qttr.at/1xnk
    In conversation Sunday, 03-Sep-2017 16:52:11 EDT from quitter.se permalink

    Attachments

    1. Invalid filename.
      Looking back to 2016. Leaping forward into 2017
      from Kontalk forum
      I’m currently seeing a lot of arguments in the XMPP mailing lists about the future of OMEMO/whatever-its-name-will-be. There are disagreements on which encryption protocols to use, even I don’t have a completely clear idea of what that all is about, there is something about licences and interoperability… anyway what is clear to me is that the community (and the XSF itself) is not really stable on this yet (and it’s not really their fault actually), and I’m a bit worried about it. In the end, I’...
  16. ziggys (ziggys@bobinas.p4g.club)'s status on Saturday, 26-Aug-2017 18:37:50 EDT ziggys ziggys
    • Privacidad en la era digital
    • XMPP en Castellano
    Con los clientes xmpp también se puede "chatear con uno mismo" y si tenemos #omemo o #gpg configurados, la cosa va cifrada !xmppes !privacidad
    In conversation Saturday, 26-Aug-2017 18:37:50 EDT from bobinas.p4g.club permalink
  17. Klaus Jónsson Zimmermann (kzimmermann@quitter.se)'s status on Sunday, 16-Jul-2017 02:29:42 EDT Klaus Jónsson Zimmermann Klaus Jónsson Zimmermann
    • Today I Learned...
    !TIL that there's an alternative to #Gajim for those who wish to use #OMEMO on the desktop: #Dino https://github.com/dino/dino/ #XMPP
    In conversation Sunday, 16-Jul-2017 02:29:42 EDT from quitter.se permalink

    Attachments

    1. Invalid filename.
      dino/dino
      from GitHub
      dino - Modern Jabber/XMPP Client using GTK+/Vala
  • After
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.

Switch to desktop site layout.