<freemangordon>
however, this does not help me answer my question - how to properly stop xorg on shutdown
<freemangordon>
uvos: ^^^ any idea?
ceene has joined #maemo-leste
slep has joined #maemo-leste
uvos has joined #maemo-leste
fab__ has joined #maemo-leste
pere has quit [Ping timeout: 264 seconds]
noidea_ has quit [Ping timeout: 252 seconds]
noidea_ has joined #maemo-leste
akossh has joined #maemo-leste
pere has joined #maemo-leste
<Wizzup>
freemangordon: can't you just send it a signal?
<Wizzup>
freemangordon: regarding the user_dir in tp, if we have jabber with omemo keys, that need manual trust marking, or MAM management in xmpp, where do you suggest we store this?
<Wizzup>
I can change the tdlib database dir for now to something else in the code, so it won't end up in purple, but this will be a problem for other protocols too
<freemangordon>
Wizzup: TP supports AccountStorage or something like that
<freemangordon>
also, I am sure libpurple supports something like that
<freemangordon>
or it could be just accoutn parameter
<freemangordon>
plugin implementing its own storage does not seem proper to me
<Wizzup>
Credentials_Stored (1) The associated account has its authentication credentials (password) stored in the connection manager
<Wizzup>
so if that flag is not set, then the cn can't manage the auth
<freemangordon>
Wizzup: also, I still don;t understand what exactly this plugin keeps out of the account
<freemangordon>
oauth toke *is* kind of password
<Wizzup>
freemangordon: telegram is implemented using a foss library called tdlib, and it has its own database storage, keeps track of what message was last seen by the client/device, and it keeps encryption/auth keys
<Wizzup>
there is no password at all, and these things MUST persist
<freemangordon>
but that'
<freemangordon>
s not TP/pidgin's fault, no?
<Wizzup>
or you have to scan a qr code every time you lose interface, or get a code on sms and enter it
<Wizzup>
pidgin has no problems with this since it doesn't wipe it's own config
<Wizzup>
only tp-haze does this
<freemangordon>
sure, but that's implementation detail
<Wizzup>
ok, what about everything else that needs to be stored/saved?
<freemangordon>
it can be saved as account proprty
<Wizzup>
device-specific keys (given how signal, whatsapp, telegram, xmpp omemo too) works
<Wizzup>
as a property, all these keys, potential binary data, etc?
<freemangordon>
yes
<Wizzup>
in the .cfg file of connection manager? :D
<freemangordon>
TP has no issue whatsoever with custom properties
<freemangordon>
yes
<Wizzup>
I think maybe you want to rethink this
<freemangordon>
what's the problem?
<freemangordon>
I don;t get it
<Wizzup>
params are set by the user, not by the program
<Wizzup>
they are input, not storage
<Wizzup>
freemangordon: you want 500x 4096 bit rsa kes base64 encoded in accounts.cfg?
<freemangordon>
no, I want them in the keystore
<freemangordon>
because they belong there
<Wizzup>
what keystore?
<freemangordon>
user's
<Wizzup>
let me see what fremantle's skype plugin does
<freemangordon>
no
<freemangordon>
wait
<Wizzup>
I bet that it has it's own .config or .local/share or so
<freemangordon>
that's where empathy stores passwords/keys/etc
<freemangordon>
accounts-ui is old-fashioned and we shall fix that someday
<Wizzup>
the tdlib that everyone uses for telegram needs a directory to function
<freemangordon>
as in - we keep passwords in the .cfg
<Wizzup>
where it stores data
<Wizzup>
there's no way around that
<Wizzup>
unless we just don't support it, or fork it
<freemangordon>
well, then it should have a way to set that dir
<Wizzup>
it does, and we set it to the purple runtime dir + tdlib
<Wizzup>
well, the current plugin does
<Wizzup>
and haze makes a new runtime dir and nukes it
<Wizzup>
so I can change it to say ~/.local/share/tdlib or so
<freemangordon>
ok
<Wizzup>
and then pidgin and telepathy-haze will share the directory
<Wizzup>
sorry if that wasn't clear
<Wizzup>
I do agree that if we go for gabble, we might want to see if we can store certain things in the keyring/keystore
<freemangordon>
no, we must do it
<freemangordon>
not only for gabble
<freemangordon>
now we store passworkds in clear form
<freemangordon>
that's bad :)
<Wizzup>
yes, that's a different story/problem I think
<freemangordon>
well, to me it is more or less the same, when it comes to RSA keys etc
<freemangordon>
the same goes for oauth
<freemangordon>
Wizzup: also, you should not change haze work dir to workaround tdlib issues
<freemangordon>
if tdlib has a way to set its work dir - that's another story
<Wizzup>
freemangordon: yes, that is what I said
<freemangordon>
ok
<Wizzup>
freemangordon: well for many of these you're storing public keys of contacts
<Wizzup>
I don't know if those go into your own keystore
<Wizzup>
or like I said before, downloading messages per contact since the last message you saw, that also needs storage
<Wizzup>
and the tp plugins will need this data somehow
<Wizzup>
but non-haze plugins don't have this problem, they can just write whereever
<freemangordon>
that's not TP job (storing messages logs)
<Wizzup>
this is not a message log
<freemangordon>
"downloading messages per contact since the last message you saw, that also needs storage"
<freemangordon>
what is this?
<Wizzup>
this is the state of your account/device that needs to be kept in sync with the server
<freemangordon>
and how is that different from "message log"?
<freemangordon>
besides the wording that is
<Wizzup>
because what you need to sync with the server isn't just the last few messages, but probably specific ids and other stuff, and you need to *provide* that to the server I imagine
<Wizzup>
when you connect
<Wizzup>
so you tell me how the tp plugins get access to that data
<Wizzup>
in any case, we'll run into this I think when we actually implement MAM and such
<Wizzup>
and trust me, this was maybe designed with some of xmpp in mind, but definitely not with all the new hipster/fancy centralised protocols that people use :)
<Wizzup>
in the case of telegram I think we're 'lucky' because tdlib handles all of this transparently
<freemangordon>
I understand that
<Wizzup>
so you just get the new messages since you last signed in
<freemangordon>
but I am almost sure TP already supports that somehow
<freemangordon>
we just have to find how
<Wizzup>
ok, I am not so sure, since how can telepathy-gabble tell the server which message it has last seen when it has no storage?
<freemangordon>
trying to find
<freemangordon>
to me it should be some channel interface