Thats a pity, because it is not possible to order the case together with the phone.
However I'm going to order the pinephone.
I am using a nexus 5 too.
At 17.21 I send a message to a friend of mine with converse.js. She uses conversations.
I see two messages in converse.js: the message I wrote and a OMEMO warning, both at the same time.
While this is something I don't understand, I could read her answer which is shown only once with no warning.
But it is usable so far, in fact it is the only usable xmpp client on ubports. So thank you very much for your work.
I have reinstalled converse.js and deleted all app data. Then logged in and wrote a message to my wife.
I could read this message on both converse.js and conversations.
Then my wife wrote an answer. I could read it on converse.js, but not on conversations.
I wrote a message again (readable on both) and then I could read the answer on both clients.
Now I add gajim. I had to trust the other device. After that most of the messages arrived and could be read on all devices.
Seemed to work now.
Well, I have no idea what I did wrong the weeks before.
@PhoenixLandPirat Kaidan is not really usable:
The textfield is hidden when writting a message. Sometimes a message gets lost. Files cannot be send. The communication is not synchronize with other clients, ...
@advocatux I wrote a message to the loqui developer. They told me, that it seems to be a ubports problem, loquiim itself works fine.
I did not try Movim yet.
some further investigations about the double messages:
(1) If I send multiple messages to one person quit fast after each other, the I get only one omemo warning.
(2) Although warning and message have the same time, they do not arrive at the same time.
When I send the message the warning is displayed later although the same time as for the message is shown.
Could it be that the warning is caused by a read confirmation or something similar ?
Strange. It happens in direct chats. And of course trashserver supports http-upload.
Trashserver itsself works fine. These problems only happen with the converse.js client. With conversations and gajim everything works well.
May it be a problem caused by the bosh / wss configuration?
I added both to the server configuration. In that case which connection is used?
I reinstalled converse.js again, deleted cache ... via ut tweak, .... and autologin works now.
But still I those omemo warnings.
Do you need a screenshot? If yes: how do I do a screenshot?
May I can ask one further question? I saw at the screenshots in openstore that it should be possible to send a file or picture. Do I have to activate this feature somehow? Because at the moment I see no paperclip while typing a message.