Revision history [back]

There is thread on feature request which is just fighting about OTR vs OMEMO and they request that new thread would be opened.

I said at Diaspora:

And #OTR shows it’s badness when you have #BitlBee, #Pidgin and #Conversations open. I have no idea which client received the messages. It could be worse if #SailfishOS Messaging also supported OTR.

#OMEMO again is unsupported by Pidgin and BitlBee and SailfishOS Messaging and the only client which somewhat supports it on desktop is #Gajim, but I seem to have problems with it freezing.

and I doubt I am the only one having this issue or that many people only use Sailfish OS for their messaging needs.

Links:

• Simple explanation on what is OMEMO
• Specifications:
  • XEP-xxxx: OMEMO Encryption
  • XEP-xxxx: OMEMO Encrypted Jingle File Transfer
• TJC: The feature request on OTR which is just fighting to my point of view.

There is thread on feature request which is just fighting about OTR vs OMEMO and they request that new thread would be opened.

I said typed at Diaspora:Diaspora:

And #OTR shows it’s badness when you have #BitlBee, #Pidgin and #Conversations open. I have no idea which client received the messages. It could be worse if #SailfishOS Messaging also supported OTR.

#OMEMO again is unsupported by Pidgin and BitlBee and SailfishOS Messaging and the only client which somewhat supports it on desktop is #Gajim, but I seem to have problems with it freezing.

and I doubt I am the only one having this issue or that many people only use Sailfish OS for their messaging needs.

Links:

• Simple explanation on what is OMEMO
• Specifications:
  • XEP-xxxx: OMEMO Encryption
  • XEP-xxxx: OMEMO Encrypted Jingle File Transfer
• TJC: The feature request on OTR which is just fighting to my point of view.

There is thread on feature request which is just fighting about OTR vs OMEMO and they request that new thread would be opened.

I typed at Diaspora:

And #OTR shows it’s badness when you have #BitlBee, #Pidgin and #Conversations open. I have no idea which client received the messages. It could be worse if #SailfishOS Messaging also supported OTR.

#OMEMO again is unsupported by Pidgin and BitlBee and SailfishOS Messaging and the only client which somewhat supports it on desktop is #Gajim, but I seem to have problems with it freezing.

and I doubt I am the only one having this issue or that many people only use Sailfish OS for their messaging needs.

Links:

• Simple explanation on what is OMEMO
• Specifications:
  • XEP-xxxx: OMEMO Encryption
  • XEP-xxxx: OMEMO Encrypted Jingle File Transfer
• TJC: The feature request on OTR which is just fighting to my point of view.
• Upstream(?) (Telepathy) bug report
  • Maybe someone should poke them as they talk about moving that bug to XMPP component which never happened?

There is thread on feature request which is just fighting about OTR vs OMEMO and they request that new thread would be opened.

I typed at Diaspora:

And #OTR shows it’s badness when you have #BitlBee, #Pidgin and #Conversations open. I have no idea which client received the messages. It could be worse if #SailfishOS Messaging also supported OTR.

#OMEMO again is unsupported by Pidgin and BitlBee and SailfishOS Messaging and the only client which somewhat supports it on desktop is #Gajim, but I seem to have problems with it freezing.

and I doubt I am the only one having this issue or that many people only use Sailfish OS for their messaging needs.

Links:

• Simple explanation on what is OMEMO
• Specifications:
  • XEP-xxxx: OMEMO Encryption
  • XEP-xxxx: OMEMO Encrypted Jingle File Transfer
• TJC: The feature request on OTR which is just fighting to my point of view.
• Upstream(?) (Telepathy) bug report
  • Maybe someone should poke them as they talk

  Status of OMEMO in Telepathy:

  2016-04-23 14:55:22+0300 < Mikaela> Hi, what is the status with https://bugs.freedesktop.org/show_bug.cgi?id=93090 ? I am asking, because it talks about moving to XMPP component, but the tracker says that bug to it's in gabble component and I believe Sailfish OS Messaging OMEMO support depends on it.
  2016-04-23 14:57:21+0300 < Mikaela> allso possibly a little offftopic according to the /topic, but does Empathy support XMPP component bookmarks or is it even supported in Telepathy? I am currently using Pidgin on desktop which never happened?

There is thread on feature request which is just fighting about OTR vs OMEMO and they request that new thread would be opened.

I typed at Diaspora:

And #OTR shows it’s badness when you have #BitlBee, #Pidgin and #Conversations open. I have no idea which client received the messages. It could be worse if #SailfishOS Messaging also supported OTR.

#OMEMO again is unsupported by Pidgin and BitlBee and SailfishOS Messaging and the only client which somewhat supports it on desktop is #Gajim, but I seem to have problems with it freezing.

and I doubt I am the only one having this issue or that many people only use Sailfish OS for their messaging needs.

Links:

• Simple explanation on what is OMEMO
• Specifications:
  • XEP-xxxx: OMEMO Encryption
  • XEP-xxxx: OMEMO Encrypted Jingle File Transfer
• TJC: The feature request on OTR which is just fighting to my point of view.
• Upstream(?) (Telepathy) bug report

Status of OMEMO in Telepathy:

2016-04-23 14:55:22+0300 < Mikaela> Hi, what is the status with https://bugs.freedesktop.org/show_bug.cgi?id=93090 ? I am asking, because it talks about moving to XMPP component, but the tracker says that it's in gabble component and I believe Sailfish OS Messaging OMEMO support depends on it.
2016-04-23 14:57:21+0300 < Mikaela> allso possibly a little offftopic according to the /topic, but does Empathy support XMPP bookmarks or is it even supported in Telepathy? I am currently using Pidgin on desktop which doesn't support them.
2016-04-23 15:29:39+0300 < 1Filtered_Just_In_Case1> Mikaela: gabble is the telepathy connection manager for XMPP
2016-04-23 15:30:28+0300 < 1Filtered_Just_In_Case1> Mikaela: Nobody has stepped up to implement this, yet
2016-04-23 15:31:07+0300 < 1Filtered_Just_In_Case1> Mikaela: Apart from that, there is no XEP for OMEMO is not
2016-04-23 15:31:56+0300 < 1Filtered_Just_In_Case1> There was some talk on the standards mailing list about that but the problem seems to be that there is no standard for OMEMO either but only the reference implementation
2016-04-23 15:34:49+0300 < Mikaela> thanks :)