maemo.org - Talk
Page 129 of 157 « First 119127128 129 130131139 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   [M5] [Announce] Yappari - New maintainership and new features! (https://talk.maemo.org/showthread.php?t=94465)

handaxe 2016-01-24 21:51
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by Gabriel85 (Post 1496178)
This package could work with Nokia N9? Or you could do an adaptation ....:confused:
Er, ... http://talk.maemo.org/showthread.php?p=1496174

But there are /were issues there too.

Or you know about that app, but it is not working so you wonder about yappari? No it does not work AFAIK.

ricardo86 2016-01-26 16:32
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by Ramonf4 (Post 1492597)
Gracias por tu respuesta ceene.
Alguna forma para que no se cierrre la aplicacion o como puedo solucionar, no puedo usar Yappari.
Saludos.
Hola Ramon, disculpa pudiste solucionar el problema?

enne30 2016-01-26 17:37
Re: [Announce] Yappari - New maintainership and new features!
 
Ceene bad news:

I'm loosing messages in group chats, from specific android clients and it seems they are encrypted in logs :(

Strange thing is that same clients above are able to send me private unencrypted messages :confused:

I'll post some log file later at home..

mcnobody 2016-01-26 20:11
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by enne30 (Post 1496448)
Ceene bad news:

I'm loosing messages in group chats, from specific android clients and it seems they are encrypted in logs :(

Strange thing is that same clients above are able to send me private unencrypted messages :confused:

I'll post some log file later at home..
I have seen same now after upgraded to Yappari 2.0.23.

Code:
INCOMING:
<message>
  from=358xxxxx-143xxxxx@g.us
  id=C069zzzzzzzz127E65
  notify=Firstname Lastname
  participant=358yyyyyyy@s.whatsapp.net
  t=1453731286
  type=text
<enc>
  type=skmsg
  v=2
 ....here encrypted message....

parseMessageInitialTagAlreadyChecked
Encoded message from 358407711636-1439890434@g.us
OUTGOING:
<receipt>
  id=C069zzzzzzzz127E65
  to=358xxxxx-143xxxxx@g.us
  type=error
<error>
  type=plaintext-only
It seems that encryption error message is sent back to group id - not to person sent encrypted message. And nothing after that so the sender does not senf message again without encryption.

s4br0s0 2016-01-26 22:38
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by enne30 (Post 1496448)
Ceene bad news:

I'm loosing messages in group chats, from specific android clients and it seems they are encrypted in logs :(

Strange thing is that same clients above are able to send me private unencrypted messages :confused:

I'll post some log file later at home..
+1.

Same here.

Greetings.

mcnobody 2016-01-27 06:13
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by enne30 (Post 1496448)
Ceene bad news:

I'm loosing messages in group chats, from specific android clients and it seems they are encrypted in logs :(

Strange thing is that same clients above are able to send me private unencrypted messages :confused:

I'll post some log file later at home..
I have seen same.

Code:
INCOMING:
<message>
  from=358xxxxxxxx-14398yyyyy@g.us
  id=C069AAzzzzzzzzz65
  notify=Firstname Lastname
  participant=358zzzzzzzz@s.whatsapp.net
  t=1453731286
  type=text
<enc>
  type=skmsg
  v=2
  ....encrypted message....

parseMessageInitialTagAlreadyChecked
Encoded message from 358xxxxxxxx-14398yyyyy@g.us
OUTGOING:
<receipt>
  id=C069AAzzzzzzzzz65
  to=358xxxxxxxx-14398yyyyy@g.us
  type=error
<error>
  type=plaintext-only
It seems that plaintext-only reply is sent back to group and not to actual sender. Maybe that's the reason for problem now.

This sender has Android phone.

enne30 2016-01-27 07:03
Re: [Announce] Yappari - New maintainership and new features!
 
1 Attachment(s)
Sorry for late..

Attached log file contains the following use case: contacts 39380 and 39348 send me messages in same group (encrypted) and private messages (plain text)..
It seems it happens only in one group atm (not sure anyway..); maybe some group partecipant could force encryption in entire group? (group is plenty of devices: iphones, android, windoze phone :eek: )

EDIT (maybe a work-around): try to ask to all contacts sending encrypted messages in group chats, to send you private messages until you see at least one (first ones may be encrypted and not displayed);
it seems this way server stores information that we cannot receive encrypted messages and you will start to receive plain-text again from those contacts in groups :eek:
I don't know how much time this will last, until clients start again to send encrypted messages... I'll let you know...

PathFinder@9GS 2016-01-27 18:01
Re: [Announce] Yappari - New maintainership and new features!
 
So I was able to boot up my n900 after a few years and with the updated version I am not able to register my new number. It still connects with the old number.
Is there a known problem with that? I'm not getting a new sim detected prompt. Can someone help me if there's a workaround.

Thank you very much

sicelo 2016-01-27 19:44
Re: [Announce] Yappari - New maintainership and new features!
 
Delete /home/user/.config/scorpius/yappari.conf

PathFinder@9GS 2016-01-27 20:43
Re: [Announce] Yappari - New maintainership and new features!
 
Quote:
Originally Posted by sicelo (Post 1496639)
Delete /home/user/.config/scorpius/yappari.conf
That worked perfectly. Thank you very much :)


All times are GMT. The time now is 22:06.
Page 129 of 157 « First 119127128 129 130131139 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8