Updates tagged with omemo on Jonkman Microblog!
goffi: It is with a big pleasure and a sort of relief that I announce you the release of "Salut à Toi" v0.7.0 (La Commune). Salut à Toi is a libre and decentralized communication ecosystem/The release announce is to be read there: https://www.goffi.org/b/N29CuUQS4U4TK36JFuTQ5Q/salut-commune#salutatoi #decentralization #xmpp #instant_messaging #OMEMO
goffi's status on Wednesday, 24-Jul-2019 19:00:42 EDT
It is with a big pleasure and a sort of relief that I announce you the release of "Salut à Toi" v0.7.0 (La Commune). Salut à Toi is a libre and decentralized communication ecosystem/ The release announce is to be read there: https://www.goffi.org/b/N29CuUQS4U4TK36JFuTQ5Q/salut-commune #salutatoi #decentralization #xmpp #instant_messaging #OMEMO
hexmasteen: @ludman1 #Matrix hat voice und video chat. Das wären die Gründe dafür. Dagegen spricht für mich, dass sie #e2ee noch immer nur optional anbieten (moderne #XMPP clients machen #OMEMO by default). Außerdem verwendet #riot #electronJS. Und mit #riot kann ich nicht mehrere Accounts/Identitäten verwenden.Allgemein würde ich behaupten #XMPP ist in der Praxis dezentralisierter und tiefer in der Community verwurzelt.
hexmasteen's status on Wednesday, 17-Jul-2019 05:13:10 EDT
@ludman1 #Matrix hat voice und video chat. Das wären die Gründe dafür. Dagegen spricht für mich, dass sie #e2ee noch immer nur optional anbieten (moderne #XMPP clients machen #OMEMO by default). Außerdem verwendet #riot #electronJS. Und mit #riot kann ich nicht mehrere Accounts/Identitäten verwenden. Allgemein würde ich behaupten #XMPP ist in der Praxis dezentralisierter und tiefer in der Community verwurzelt.
clacke: framapiaf.org/@debacle/1016213… ♲ @debacle@framapiaf.org: #OMEMO is a big fish 🐠 in the upcoming #Debian 10 release (#buster) bowl. It hopefully will feature five #XMPP clients with this modern #e2e #encryption: #Gajim, #Dino, #Psi+ (all graphical), #jp (command line), and #primitivus (console), the latter two part of #SalutAToi or #SaT
clacke's status on Tuesday, 16-Apr-2019 04:27:24 EDT
framapiaf.org/@debacle/1016213… ♲ @debacle@framapiaf.org: #OMEMO is a big fish 🐠 in the upcoming #Debian 10 release (#buster) bowl. It hopefully will feature five #XMPP clients with this modern #e2e #encryption: #Gajim, #Dino, #Psi+ (all graphical), #jp (command line), and #primitivus (console), the latter two part of #SalutAToi or #SaT
clacke: inhibited exhausted pixie dream boy 🇸🇪🇭🇰💙💛
debacle: #OMEMO is a big fish 🐠 in the upcoming #Debian 10 release (#buster) bowl. It hopefully will feature five #XMPP clients with this modern #e2e #encryption: #Gajim, #Dino, #Psi+ (all graphical), #jp (command line), and #primitivus (console), the latter two part of #SalutAToi or #SaT
debacle's status on Tuesday, 19-Feb-2019 18:14:27 EST
#OMEMO is a big fish 🐠 in the upcoming #Debian 10 release (#buster) bowl. It hopefully will feature five #XMPP clients with this modern #e2e #encryption: #Gajim, #Dino, #Psi+ (all graphical), #jp (command line), and #primitivus (console), the latter two part of #SalutAToi or #SaT
strypey: @noorul There's no shame in re-evaluating software choices based on new information, in fact it's something to be proud of. We all make strategic decisions about what apps and services to use, based on what options are available, and what information we have about them. For all its flaws, Signal is a better choice than WhatsApp or Telegram (because Signal publishes source code for its client *and* server software). Before #OMEMO, it was arguably a better choice than #XMPP. It's always a toss-up.
strypey's status on Thursday, 10-Jan-2019 04:16:08 EST
@noorul There's no shame in re-evaluating software choices based on new information, in fact it's something to be proud of. We all make strategic decisions about what apps and services to use, based on what options are available, and what information we have about them. For all its flaws, Signal is a better choice than WhatsApp or Telegram (because Signal publishes source code for its client *and* server software). Before #OMEMO, it was arguably a better choice than #XMPP. It's always a toss-up.
strypey: @z428 there are various ways to address this. OWS doesn't let clients older than 3 months connect to their servers. A secure chat federation protocol could include refusing to connect to another server that hasn't been updated for more than 3 months. There are all sorts of systems you can use to ensure security across a federated network (ask Mike from #Hubzilla / #Osada / #Zap about it). The only main problem with XMPP is that until recently security wasn't a design goal, but now #OMEMO exists.
strypey's status on Sunday, 06-Jan-2019 16:23:37 EST
@z428 there are various ways to address this. OWS doesn't let clients older than 3 months connect to their servers. A secure chat federation protocol could include refusing to connect to another server that hasn't been updated for more than 3 months. There are all sorts of systems you can use to ensure security across a federated network (ask Mike from #Hubzilla / #Osada / #Zap about it). The only main problem with XMPP is that until recently security wasn't a design goal, but now #OMEMO exists.
strypey: @kawaiipunk > Signal is the best of a bad situation.I'm still not sure why you think that.> All of these criticisms of Signal are addressed by XMPP and OMEMO?Many of the more urgent ones are already addressed by Wire. Another set will be when Wire rolls out server>server federation. If we can get them to use #OpenStandards like #XMPP and #OMEMO, that would address another set. @gentoorebel @noorul
strypey's status on Sunday, 06-Jan-2019 15:24:07 EST
@kawaiipunk > Signal is the best of a bad situation. I'm still not sure why you think that. > All of these criticisms of Signal are addressed by XMPP and OMEMO? Many of the more urgent ones are already addressed by Wire. Another set will be when Wire rolls out server>server federation. If we can get them to use #OpenStandards like #XMPP and #OMEMO, that would address another set. @gentoorebel @noorul
paulfree14: Which #OMEMO encrypted desktop compatible #xmpp chat can ppl advice? Will #SàT (#SáT) get that level of encryption somewhen not to far in future? (social network that runs on xmpp)
paulfree14's status on Saturday, 03-Nov-2018 05:35:58 EDT
Which #OMEMO encrypted desktop compatible #xmpp chat can ppl advice? Will #SàT (#SáT) get that level of encryption somewhen not to far in future? (social network that runs on xmpp)
infosechandbook: An opinion on the future of OMEMO:http://blogs.fsfe.org/vanitasvitae/2018/09/07/future-of-omemo/– some users/developers consider forward secrecy needless – OMEMO's trust management sucks – OMEMO only protects the message body – OMEMO isn't a standard and further development came to a standstill – Messaging Layer Security (MLS) is an upcoming attempt to create a new encryption standard#omemo #xmpp #mls #infosec #cybersecurity #security
infosechandbook's status on Wednesday, 31-Oct-2018 02:39:41 EDT
An opinion on the future of OMEMO: http://blogs.fsfe.org/vanitasvitae/2018/09/07/future-of-omemo/ – some users/developers consider forward secrecy needless – OMEMO's trust management sucks – OMEMO only protects the message body – OMEMO isn't a standard and further development came to a standstill – Messaging Layer Security (MLS) is an upcoming attempt to create a new encryption standard #omemo #xmpp #mls #infosec #cybersecurity #security
colegota: @lonko @aab es que a partir de un nivel de confidencialidad requerido lo que no hay que usar es tecnología. Aún en el caso de que consiguiéramos una mensajería que de por sí no enviase nada que pudiera delatarnos, los teléfonos, ordenadores y la propia Internet son inseguros. Como lo son las personas que al final acaban siendo el eslabón más débil de cualquier cadena. Si algo te preocupa, deberías hablarlo de viva voz y en entrono confiable, si eso existe. Mientras tanto, podemos escoger herramientas más confiables sabiendo hasta donde podemos llegar. Pero el concepto ese de que a todo le encontramos alguna pega y entonces no lo usamos no lo comparto. Si la necesidad de !privacidad llega hasta puntos de que el #OMEMO, por poner un ejemplo, no te es suficiente, no usemos teléfono ni nada conectado a Internet. !xmpp
colegota's status on Wednesday, 24-Oct-2018 01:55:45 EDT
@lonko @aab es que a partir de un nivel de confidencialidad requerido lo que no hay que usar es tecnología. Aún en el caso de que consiguiéramos una mensajería que de por sí no enviase nada que pudiera delatarnos, los teléfonos, ordenadores y la propia Internet son inseguros. Como lo son las personas que al final acaban siendo el eslabón más débil de cualquier cadena. Si algo te preocupa, deberías hablarlo de viva voz y en entrono confiable, si eso existe. Mientras tanto, podemos escoger herramientas más confiables sabiendo hasta donde podemos llegar. Pero el concepto ese de que a todo le encontramos alguna pega y entonces no lo usamos no lo comparto. Si la necesidad de !privacidad llega hasta puntos de que el #OMEMO, por poner un ejemplo, no te es suficiente, no usemos teléfono ni nada conectado a Internet. !xmpp
rozzin: I am... so not understanding #OMEMO. Why do people actually like this?
rozzin's status on Friday, 24-Aug-2018 16:05:02 EDT
I am... so not understanding #OMEMO. Why do people actually like this?
lnxw48a1: @cobra2 I only know of one #iOS !XMPP client: Monal. I can't say whether it supports #OTR and #OMEMO.
lnxw48a1's status on Thursday, 23-Aug-2018 18:57:07 EDT
@cobra2 I only know of one #iOS !XMPP client: Monal. I can't say whether it supports #OTR and #OMEMO.
kawaiipunk: @resist_berlin asked me why I stopped using #xmpp.I wanted to make my point publicly that we should focus on net-gen #privacy tools rather than old protocols that have already been lapped in terms of #usability.I have 248 contacts who have #WhatsApp but only a handful with xmpp.Yes #omemo and #conversations are a step in the right direction but I would like to see the community focus on applications like #Briar which has features that WhatsApp simple can't compete with.
kawaiipunk's status on Sunday, 12-Aug-2018 16:37:04 EDT
@resist_berlin asked me why I stopped using #xmpp. I wanted to make my point publicly that we should focus on net-gen #privacy tools rather than old protocols that have already been lapped in terms of #usability. I have 248 contacts who have #WhatsApp but only a handful with xmpp. Yes #omemo and #conversations are a step in the right direction but I would like to see the community focus on applications like #Briar which has features that WhatsApp simple can't compete with.
lnxw48a1: Even better: !XMPP (with #OMEMO or #OTR) or #Wire.
lnxw48a1's status on Tuesday, 07-Aug-2018 00:33:07 EDT
Even better: !XMPP (with #OMEMO or #OTR) or #Wire.
silkevicious: So is this #OMEMO better than #OTR or not?
silkevicious's status on Friday, 18-May-2018 07:36:58 EDT
So is this #OMEMO better than #OTR or not?
kzimmermann2: I set up #OMEMO accross all my close family yesterday using the #Conversations app and #Gajim on the desktop. Bottom line, not too bad. They were impressed by how easy and similar to mainstream messengers like WhatsApp it is, but I think they missed (and still miss) the main point: FREEDOM for communications through decentralization and cryptography. !privacy
kzimmermann2's status on Monday, 14-May-2018 13:43:07 EDT
I set up #OMEMO accross all my close family yesterday using the #Conversations app and #Gajim on the desktop. Bottom line, not too bad. They were impressed by how easy and similar to mainstream messengers like WhatsApp it is, but I think they missed (and still miss) the main point: FREEDOM for communications through decentralization and cryptography. !privacy
Klaus Jónsson Zimmermann (alternative acc)
kzimmermann2: #Gajim 1.0.1 released on Ubuntu 18.04 looks great and feels great. End-to-end #encryption is slick with #OMEMO plugin built right into a native package, and the interoperability with phone-based #Conversations is smooth. I think that now I have my answer as to what I'll propose to my family as an alternative to #WhatsApp from now on.
kzimmermann2's status on Thursday, 10-May-2018 15:32:28 EDT
#Gajim 1.0.1 released on Ubuntu 18.04 looks great and feels great. End-to-end #encryption is slick with #OMEMO plugin built right into a native package, and the interoperability with phone-based #Conversations is smooth. I think that now I have my answer as to what I'll propose to my family as an alternative to #WhatsApp from now on.
make: ChatSecure for iOS starting to support #omemo in group chats. #xmpp https://pleroma.raitisoja.com/media/c01ad0f2-4b4a-4503-b445-3b9693867d48/file.jpeg
make's status on Wednesday, 11-Apr-2018 00:47:23 EDT
ChatSecure for iOS starting to support #omemo in group chats. #xmpp https://pleroma.raitisoja.com/media/c01ad0f2-4b4a-4503-b445-3b9693867d48/file.jpeg
colegota: @tsr107 y aprovecho para responder a @revu que me preguntaba ayer... Cuando vino la actualización no la hice por el aviso de que perdías #OTR (Revu, uno de los tres modos de cifrado en XMPP junto con #OMEMO y #PGP) y me da mal rollo que se abandonen proyectos. Pero por otro lado entiendo que las personas que tratan de mejorar las cosas con desarrollos nuevos se vuelquen en su propio trabajo y no en mantener el de otras. Aparte, el autor, que es también una de las personas gracias a las que !xmpp es lo que es ahora, está explicando todos estos cambios en su blog [1][2]. Creo que tenemos que avanzar en #OMEMO ya que permite el cifrado multidispositivo y en salas de una forma fácil que pueda usar cualquiera. Pero claro, es solo mi opinión. :) [1] https://gultsch.de/omemo_by_default.html [2] https://gultsch.de/conversations_2_design.html @izaro @ppsoesdictadura
colegota's status on Friday, 06-Apr-2018 07:20:25 EDT
@tsr107 y aprovecho para responder a @revu que me preguntaba ayer... Cuando vino la actualización no la hice por el aviso de que perdías #OTR (Revu, uno de los tres modos de cifrado en XMPP junto con #OMEMO y #PGP) y me da mal rollo que se abandonen proyectos. Pero por otro lado entiendo que las personas que tratan de mejorar las cosas con desarrollos nuevos se vuelquen en su propio trabajo y no en mantener el de otras. Aparte, el autor, que es también una de las personas gracias a las que !xmpp es lo que es ahora, está explicando todos estos cambios en su blog [1][2]. Creo que tenemos que avanzar en #OMEMO ya que permite el cifrado multidispositivo y en salas de una forma fácil que pueda usar cualquiera. Pero claro, es solo mi opinión. :) [1] https://gultsch.de/omemo_by_default.html [2] https://gultsch.de/conversations_2_design.html @izaro @ppsoesdictadura
tomatuordenador: Dino. Communicating happiness. Dino is a modern open-source chat client for the desktop. It focuses on providing a clean and reliable Jabber/XMPP experience while having your privacy in mind. https://dino.im/#download !xmpp #OMEMO
tomatuordenador's status on Thursday, 05-Apr-2018 02:39:31 EDT
Dino. Communicating happiness. Dino is a modern open-source chat client for the desktop. It focuses on providing a clean and reliable Jabber/XMPP experience while having your privacy in mind. https://dino.im/#download !xmpp #OMEMO
tomatuordenador: 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
tomatuordenador's status on Thursday, 05-Apr-2018 02:34:47 EDT
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
rbonifaz: 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
rbonifaz's status on Sunday, 01-Apr-2018 17:29:04 EDT
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
masoud: 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
masoud's status on Wednesday, 14-Mar-2018 17:55:55 EDT
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
kzimmermann: Dis my next project: http://qttr.at/22fq !privacy #OMEMO #XMPP
kzimmermann's status on Wednesday, 28-Feb-2018 02:05:49 EST
Dis my next project: http://qttr.at/22fq !privacy #OMEMO #XMPP
postblue: @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.
postblue's status on Tuesday, 20-Feb-2018 19:42:47 EST
@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.
kzimmermann: Oh snap, !TIL that #Pidgin now also supports #OMEMO https://developer.pidgin.im/ticket/16801 Great that more messengers are adopting it!
kzimmermann's status on Monday, 12-Feb-2018 20:42:48 EST
Oh snap, !TIL that #Pidgin now also supports #OMEMO https://developer.pidgin.im/ticket/16801 Great that more messengers are adopting it!
gcupc: 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.)
gcupc's status on Tuesday, 16-Jan-2018 09:14:02 EST
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.)
muto: Finally, with the release of #Conversations 2.0 #OTR will be removed on March 24th, 2018https://twitter.com/iNPUTmice/status/939171488942436352 #XMPP #OMEMO
muto's status on Saturday, 09-Dec-2017 06:19:23 EST
Finally, with the release of #Conversations 2.0 #OTR will be removed on March 24th, 2018 https://twitter.com/iNPUTmice/status/939171488942436352 #XMPP #OMEMO
muto: #ChatSecure v4.2.0 released improved group chat, performance and reliability https://chatsecure.org/blog/chatsecure-v42-group-chat/ #xmpp #omemo
muto's status on Thursday, 26-Oct-2017 02:02:45 EDT
#ChatSecure v4.2.0 released improved group chat, performance and reliability https://chatsecure.org/blog/chatsecure-v42-group-chat/ #xmpp #omemo
bobjonkman: 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.
bobjonkman's status on Sunday, 15-Oct-2017 04:49:37 EDT
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.
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
rugk's status on Sunday, 08-Oct-2017 05:11:28 EDT
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
rugk -> ⚠️ Follow me at https://social.wiuwiu.de/@rugk
tdemin: @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.
tdemin's status on Wednesday, 04-Oct-2017 11:17:18 EDT
@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.
How Legacy Compatibility Kills User Experience in Decentralized Environments
clacke: 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
clacke's status on Sunday, 24-Sep-2017 04:21:00 EDT
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
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.
maiki's status on Monday, 18-Sep-2017 18:43:49 EDT
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.
kontalk: @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
kontalk's status on Sunday, 03-Sep-2017 16:52:11 EDT
@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
Looking back to 2016. Leaping forward into 2017
ziggys: 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
ziggys's status on Saturday, 26-Aug-2017 18:37:50 EDT
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
kzimmermann: !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
kzimmermann's status on Sunday, 16-Jul-2017 02:29:42 EDT
!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