<Wizzup>
to be honest I'm quite happy with how this is working out wrt tp
<Wizzup>
I think if we can implement some history fetching for some of the more important protocols, we're quite far then
cockroach has quit [Quit: leaving]
mdz has quit [Ping timeout: 245 seconds]
mrkrisprolls has quit [Ping timeout: 245 seconds]
mrkrisprolls has joined #maemo-leste
mrkrisprolls has quit [Ping timeout: 260 seconds]
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
mrkrisprolls has joined #maemo-leste
<freemangordon>
Wizzup: yes, your messages from web client (or another leste device) are reported as scrollback messages to tp
<freemangordon>
what is the issue with password field?
<freemangordon>
if it is either password or api token, just enter it there
mrkrisprolls has quit [Ping timeout: 260 seconds]
uvos has joined #maemo-leste
mrkrisprolls has joined #maemo-leste
mrkrisprolls has quit [Ping timeout: 268 seconds]
<freemangordon>
arno11: did you manage to fix you fb plugin issues?
<freemangordon>
Wizzup: hmm, sometimes sent messages got lost
<freemangordon>
like, I type something on the kbd, press send and nothing happens, besides that message field is cleared
<freemangordon>
if I kill conversations, it starts to work
mrkrisprolls has joined #maemo-leste
nela has quit [Ping timeout: 264 seconds]
mdz has joined #maemo-leste
arno11 has joined #maemo-leste
<Wizzup>
freemangordon: it's not either api_token or password, they are seperate things for the plugin
<Wizzup>
freemangordon: I have never gotten a message that I have sent myself delivered, not as scrollback or otherwise, but I don't do fb
<arno11>
freemangordon: no, i still have issues with FB plugin: purple-FB is perfectly working through pidgin but not through tp-haze/conversations (from a fresh install, i tried twice, with devel upgrade and FB plugin from extras testing)
<arno11>
maybe that's something due to my account, i don't know, otherwise everything is fine (even with overclock :P, btw my n900 is stable @1GHz with Fremantle and works @1.1GHz)
<Wizzup>
does it not log into the account, or do messages not get reported?
<arno11>
it refuses to log in fact
<arno11>
and when i start presence-ui from command line it show 'network error')
<arno11>
what i don't understand is why it works in pidgin with exactly the same settings and same network
<freemangordon>
arno11: hmm, weird
<freemangordon>
will ping you later on to check what haze is doing
<arno11>
ok
arno11 has left #maemo-leste [#maemo-leste]
rafael2k has joined #maemo-leste
mdz has quit [Ping timeout: 260 seconds]
ceene has joined #maemo-leste
<freemangordon>
Wizzup: maybe I didn't explain it properly - it is not about messages from other channels, but IM message (person-to-person)
<Wizzup>
I understand
<Wizzup>
so on xmpp with gabble you won't get these currently
<Wizzup>
we'd need the xep 0313 MAM support for this I believe
<freemangordon>
again, it is not about any history
<freemangordon>
I just type a message, press 'Send" and nothinbg :)
<Wizzup>
what if you're offline on the phone at that moment?
<freemangordon>
I am not
<Wizzup>
so there are two things
<Wizzup>
if a protocol supports real time sending your sent messages, handle them well
<freemangordon>
but even if I am, I should be given at least error message or something
<Wizzup>
and then there is the more general case
<Wizzup>
yeah, we don't handle the offline / not in a room case yet
<Wizzup>
we will
<Wizzup>
but the more general case is that various protocols can send you message history from channels, like slack, xmpp, etc
<freemangordon>
ok, I think I am just hitting some bug
<freemangordon>
right
<Wizzup>
so that your phone can have the 'full/correct' log
<freemangordon>
right
<freemangordon>
got it
<freemangordon>
but all this has nothing to do with what I reported ^^^ :)
<Wizzup>
if tp-haze reports your message sent from another device and conversations doesn't log it, that's a bug
<Wizzup>
conversations currently ignores messages marked as delivery reports
<Wizzup>
but it doesn't look at the scrollback status
<freemangordon>
I know
<freemangordon>
it is not about scrollback or delivery report
<freemangordon>
again:
mn3monic0 has joined #maemo-leste
<freemangordon>
I press on a IM action in addressbook, conversations open IM channel, I type something, press send, message field gets cleared and that's all
<Wizzup>
I see, and if you re-open the window in conversations, is the message there?
<freemangordon>
the message is neither received on the other side, nor does it appear in the history
<freemangordon>
no, it is not
mn3monic0 is now known as mn3monic
mn3monic has quit [Ping timeout: 256 seconds]
<Wizzup>
ok, so the sending just goes awry
<freemangordon>
yes
<freemangordon>
that's what I am trying to say all the time :)
<freemangordon>
unfortunately no idea how to repro
<freemangordon>
maybe if account re-connects ?
<Wizzup>
I think the first thing to do is the handle the status of a sent message
<Wizzup>
we don't track that currently
<Wizzup>
we just fire and forget
<freemangordon>
ok, but when do you add it to history and to scrollback?
<Wizzup>
when it is sent successfully
<freemangordon>
how do you know that?
<Wizzup>
tp lets us know though the channel onMessageSent signal
<freemangordon>
ok
<Wizzup>
but if we want to get specific errors for a msg, we will need to follow it
<freemangordon>
BTW, I suspect once you open a channel and account re-connects, the handle is no longer valid
<Wizzup>
and then we would log messages to the db, set flags that they aren't sent yet, and then update those flags instead of logging a new message in onmessagesent
<Wizzup>
that is correct, at least for rooms
<Wizzup>
I am not sure if this is the same for direct 1:1 messages too
<freemangordon>
it should be the same for IM channels as well
<Wizzup>
oh, wait, I see, yes.
<freemangordon>
;)
<Wizzup>
yes, this is probably it
<Wizzup>
we'll have to handle the channel invalidation then
<freemangordon>
so you should handle acount status
<Wizzup>
because we have a channel 'cache', so we don't make double channels
<freemangordon>
yes
<freemangordon>
I don;t think that's needed
<Wizzup>
I think we just handle channel invalidation, not check onOnline or something
<freemangordon>
at least haze does that for you
<Wizzup>
no, this can definitely happen
<freemangordon>
for group chats that is
<Wizzup>
even if it is the same channel, we would connect() the qt signal twice
<Wizzup>
resulting in double messages :)
<freemangordon>
ah
<freemangordon>
anyway, have to run, ttyl
mn3monic8 has joined #maemo-leste
mdz has joined #maemo-leste
<Wizzup>
ttyl
mn3monic8 is now known as mn3monic
vahag has joined #maemo-leste
mdz has quit [Quit: mdz]
mdz1 has joined #maemo-leste
mdz1 is now known as mdz
ceene has quit [Remote host closed the connection]
<rafael2k>
Happy 2024 everybody!
<rafael2k>
The maemo is running on the PPP here for 2 week without reboot. At least the kernel from Mobian is very stable.
<Wizzup>
right, but the display/hildon-desktop still needs to be figured out, right?
<Wizzup>
also, happy new year
<rafael2k>
yeap
<Wizzup>
we're making lots of progress I think :)
<rafael2k>
anyone with time, lemme know, I too a look in the code, but I feel I'll spend much more time than any of you
<Wizzup>
I think fmg is the best candidate to take a look
<Wizzup>
I don't know too much about h-d
<rafael2k>
I have a feeling there could be some issue at panfrost too. I hope not
<Wizzup>
could be, but let's exclude that for now
<Wizzup>
rotation is likely not 3d related
<rafael2k>
right
<rafael2k>
and the lock screen is perfectly working, no lags, correct aspect and so on
<freemangordon>
rafael2k: how can I copnnect?
<freemangordon>
*connect
arno11 has joined #maemo-leste
<arno11>
freemangordon: i got logs fron tp-haze and issue seems related to recent changes with my ISP !
<freemangordon>
ugh
<freemangordon>
but why it affects haze only?
<arno11>
because it seems to be related to tricky stuff with ipv6
<freemangordon>
so, can we do anything to fix that?
<arno11>
and pidgin seems to have patch for that issue
<freemangordon>
ahaaa
<arno11>
not at the moment
<arno11>
and this issue seems to affect FB and google mainly
<arno11>
so anyway
<freemangordon>
wtym 'pidgin has a patch", isn't it the same plugin?
<arno11>
same plugin yes, but i mean pidgin itself
<freemangordon>
ok, but pidgin is just an UI, it is the plugin that does all the job
<arno11>
apparently not all the job iiuc
<freemangordon>
ah, maybe the fix is in libpurple
<arno11>
ah yes probably
<freemangordon>
but... they use the same libpurple
<arno11>
i'll have a 'deeper' look and let you know
<freemangordon>
ok, LMK if you find some details
<freemangordon>
ok
<freemangordon>
I wonder shall we do PR for our changes to upstream
xmn has quit [Quit: ZZZzzz…]
xmn has joined #maemo-leste
arno11 has quit [Quit: Lost terminal]
nela has joined #maemo-leste
mdz has quit [Ping timeout: 252 seconds]
<rafael2k>
hey
<rafael2k>
I'll write to you in pvt
asriel has quit [Quit: Don't drink the water. They put something in it to make you forget.]