<freemangordon>
and do 'message window' matching upon scrollback message being received
<freemangordon>
also, I think we have message timestamp
<freemangordon>
hash+ts should be enough to uniwue identify a message
<Wizzup>
ok, I think you may want to reconsider this after some reading
<freemangordon>
mhm
<Wizzup>
if you can for example ask for the latest received message on the client side you can inform the server what to send to you
<Wizzup>
for this some own custom hash won't suffice, you need the protocol specific message id
<Wizzup>
this is the 'right' solution to getting the messages you want, not just the unread ones as facebook does currently for you
<freemangordon>
no, FB can do the full history
<Wizzup>
and this requires storing at least some message ids locally, potentially more, but that is just how this ought to work
<Wizzup>
ok, but I doubt that you want the full history every time, and with message markers as in xmpp I think you have a much cleaner and easier way to get what you need
<Wizzup>
again we don't need this now and gabble can't even do it
<Wizzup>
just things to consider before we start filling db fields :D
<freemangordon>
right
<Wizzup>
(gabble can't even do it -now-)
<freemangordon>
re FB: you request the last N messages
<freemangordon>
or full history
<freemangordon>
not sure how's that supposed to work
<freemangordon>
I guess it is same/similar for xmpp
* freemangordon
reads the specs again
<freemangordon>
oh, it seems I misunderstood it
<freemangordon>
"This is not guaranteed to be unique, even within the scope of a single channel or contact: the only guarantee made is that two messages with different non-empty tokens are different messages."
<freemangordon>
I am not sure I can grok the "...he only guarantee made is that two messages with different non-empty tokens are different messages." part
<Wizzup>
It is probably intentionally vague
pere has joined #maemo-leste
<freemangordon>
hmm, libpurple does not seem to provide message ids :(
<Wizzup>
so there's pidgin fork/changes with message markers for example
<Wizzup>
also omemo plugins, would be interesting if we could just load those somehow
<Wizzup>
this would of course be for tp-haze not gabble (these plugins)
<freemangordon>
ok, what is the status of pidgin3?
<freemangordon>
#pidgin
<freemangordon>
maybe join ^^^
<Wizzup>
k
<Wizzup>
I wouldn't look at that now
<Wizzup>
we have all we need to make this work on pidgin2 I think
<Wizzup>
see my links bove
ac_laptop has joined #maemo-leste
<freemangordon>
they say they use timestamps, which is not exactly message ids
<freemangordon>
buok, lets not focus on that now, we have more issues
Oksana has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11>
weird: on my N900 conversations UI is still very slow to launch from hildon icon (around 10 sec, even after the first time). but if i start it from a fb chat or sms notification, it starts in 2 or 4 sec max.
<arno11>
*2-4 sec max to show UI and chat window
<Wizzup>
this is because the first one launches conversations for conversations to find out it is already running and activating itself
<Wizzup>
the second one I believe just lets conversations know on dbus that it needs to show itself
<Wizzup>
we can probably have the conversations desktop icon also be a similar dbus call
<dsc_>
10sec while its already in the background?
<arno11>
yes
<arno11>
but not from notifications
<dsc_>
right
<dsc_>
its because clicking on a notification will just raise conversations
<dsc_>
while clicking will actually start a 2nd instance, at which point it finds out that its already running, and exit, and raise the original one
<Wizzup>
dsc_: I think we are in agreement ;)
<dsc_>
yes
<Wizzup>
but we can have dbus start conversations potentially, and then make the icon just do a dbus call
<arno11>
lol indeed you are
<arno11>
makes sense imo
<dsc_>
is there something in dbus that can prevent running something 2 times?
<dsc_>
how does it check if it is already running?
pere has quit [Ping timeout: 260 seconds]
<dsc_>
or do we then just launch a bash script that checks a lockfile
uvos has joined #maemo-leste
<uvos>
The problem ist that QApplication::QAppilcation() takes way to long
<uvos>
sphone also has this problem, when run with a qt module starting sphone via the icon takes long and i blocks in this call
<uvos>
if no qt module is used with sphone it starts and informs the other instance very fast
<dsc_>
yes, starting conversations just to check if an instance is already active is wasting resources
<dsc_>
it can be done with something simple
<uvos>
sure, same with sphone, (well sphone is a lot better, since it loads all the modules after checking if it needs to raise the other instance)
<uvos>
but still QApplication::QAppilcation() takes an unresonable amount of time regardless
<Wizzup>
this we could probably really 'fix' with a maemo-launcher qt booster
<Wizzup>
uvos: so sorry to pester you with this, but what can I do on razr with android to see if we can fix the screen issue?
arno11 has left #maemo-leste [#maemo-leste]
pere has joined #maemo-leste
<uvos>
Wizzup: i mean you could look at /diff the DSS registers see page 2192 in the TRM
<uvos>
but its a shot in the fairly dark
<Wizzup>
ok
<Wizzup>
so we think it's likely not a dts issue but rather a driver issue?
<uvos>
could be either really
<Wizzup>
ok
<Wizzup>
and I think for atrix we made some notes on how to make the dts changes, how it was different from the bionic
<Wizzup>
did you host those somewhere?
<Wizzup>
there is the signal map I see
ungeskriptet has quit [Ping timeout: 256 seconds]
kiva has joined #maemo-leste
<kiva>
I was 2 1/2 hour MS Teams meeting with Pinephone Keeyboard thru Firefox 115.1. Mic keeps muted so had to write chat of it, when I wated answer. Mic worked about half yeas ago...I think it was bug in M$-code, it did not understand that mic was allowed by Firefox.
<kiva>
wated=wanted
<kiva>
After that meeting there was stll 39% battery left..thanks for two batteries of PPK.
<kiva>
Anyway it might be also good thing that M$ does not know how to listen mic from Maemo Leste device ;)
<sicelo>
teams meeting via phone (3g/4g)? or how?
<kiva>
4g
<kiva>
connecting with Firefox with 4G internet connection.
kiva has quit [Quit: Client closed]
<sicelo>
oh wow. teams web?
kiva has joined #maemo-leste
<kiva>
yes
ceene has quit [Ping timeout: 252 seconds]
<freemangordon>
kiva: on leste? you are my hero :)
<uvos>
Wizzup: afaik as i know there is no difference between the atrix and the bionic
<uvos>
sensors and modems aside
<uvos>
i think it would just boot a bionic image
<Wizzup>
uvos: right, but we need to make a dts for the diff sensors at least
<Wizzup>
iirc we made some list on irc of what was different
<Wizzup>
I g2g
<kiva>
freemangordon: ofcourse with Leste.
<uvos>
Wizzup: de decoded the dtb and the signal map
<uvos>
both of those are on my server
<uvos>
you can diff them with bionic for differences
<uvos>
but iirc there are none besides the mentioned sensors and different modem
<uvos>
setup
<uvos>
the real issue is that it needs clownboot which is annoying
<uvos>
you could add dmesg for mb865 seams we lack it
nmdv has joined #maemo-leste
kiva has quit [Quit: Client closed]
<Wizzup>
uvos: yeah I checked your server :)
<Wizzup>
I think I already got clownboot sorted?
<Wizzup>
I have a working atris 2 with leste here
<Wizzup>
atrix
<Wizzup>
iirc it was the same
<Wizzup>
(as bionic)
<dsc_>
clownboot? :P
<Wizzup>
double kexec
<uvos>
silly boot method i devised for devices with locked bootloaders that have no known vunerabilities
<uvos>
that involves kexecing twice
narodnik has quit [Quit: WeeChat 4.2.2]
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 272 seconds]
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 264 seconds]
narodnik has joined #maemo-leste
nmdv has quit [Ping timeout: 252 seconds]
akossh has quit [Ping timeout: 260 seconds]
akossh has joined #maemo-leste
noidea_ has quit [Ping timeout: 260 seconds]
noidea_ has joined #maemo-leste
noidea__ has joined #maemo-leste
noidea_ has quit [Ping timeout: 260 seconds]
arno11 has joined #maemo-leste
parazyd has quit [Ping timeout: 252 seconds]
parazyd has joined #maemo-leste
<inky>
kiva: i think with chromium you would not have a mic problem.
<inky>
kiva, also advice from a former corporate employee (and jobless now) - i compiled pidgin's teams plugin and i was able to be always online for them from my droid4 and leste.
<Wizzup>
it would be nice/cool to have that packaged like we packaged the other libraries