| dsc_ | alright | 00:16 |
|---|---|---|
| dsc_ | thanks for confirming | 00:16 |
| freemangordon | hmm... | 01:12 |
| freemangordon | actually there is no bug | 01:12 |
| freemangordon | this *is* master contact, but temporary | 01:12 |
| freemangordon | dsc_: https://pastebin.com/wYyBdKvG | 01:24 |
| pere | Anyone had time to look at <URL: https://github.com/maemo-leste-extras/dorian/issues/18 > yet? | 12:47 |
| sicelo | i saw it when i made my recent MR to dorian, but did not have time to attempt a fix. i will only start to have time at the beginning of December (I hope) ... but my TODO list is already packed. | 12:52 |
| sicelo | i'm clueless with C++, but I could add this task on my todo as well if it'll still be useful | 12:54 |
| pere | I guess everyones TODO is packed. four years later, my <URL: https://github.com/maemo-leste-extras/dorian/pull/17 > is still pending. | 12:59 |
| freemangordon | pere: I understand your frustration, but yes, we are basically 3-4 (at most) devs working in our spare time on the project and yes, things like working audio, conversations, contacts, phone calls, phone settings, etc are considered with higher prio than book reader. Believe me, it is not that we don;t want patches, but day is only 24 hours. | 13:15 |
| pere | sure. | 13:16 |
| freemangordon | maybe you can become maintainer of the said book reader | 13:16 |
| freemangordon | dunno, now I see Wizzup being maintainer, but I guess that's because he imported it in the repos | 13:17 |
| freemangordon | Wizzup: ^^^ what do you think | 13:17 |
| pere | at the moment maemo do not have any relevant usecases for me, have been considering using it as a ebook reader, but it is not working well, so my motivation for maintaining any of the packages is low. | 13:19 |
| pere | did also consider it as a address book, but lacked the time to figure out how to get my old dongle connected to my ical server. | 13:20 |
| freemangordon | I understand, however, could you elaborate on what is missing (besides the book reader that fits your needs, obviously :) ) | 13:20 |
| freemangordon | hmm, I think we have instructions on wiki in regards to ical | 13:21 |
| pere | It has been a while since I looked at it, but I have vague memories of having no way to keep the ical connect password only in memory, only found a way to store it on disk, and I do not want that. | 13:22 |
| sicelo | pere: you use Leste on N900? or different device? | 13:35 |
| sicelo | ah, my other message was lost ... | 13:36 |
| pere | I got a old N900 which I might use as a simple PDA, not as a phone. | 13:36 |
| n900 | i'm biased, but its also great for running weechat and lurking in this channel... | 13:37 |
| * n900 goes back to lurking | 13:37 | |
| sicelo | so I was saying I can look at the open dorian issues and fix whatever I can. perhaps mid Dec, since early Dec I really need to focus on the L5 port | 13:37 |
| freemangordon | sicelo: want a short lesson on pointers etc? mow I have 10 minutes free | 13:39 |
| freemangordon | *now | 13:39 |
| sicelo | yes, let's do it :-) | 13:41 |
| freemangordon | ok, so... | 13:41 |
| freemangordon | imagine, for simplicity, a 16bit processor that supports only real addresses (no virtual addressing) | 13:42 |
| freemangordon | and lets assume it has 64KB of memory attached to its address bus | 13:43 |
| freemangordon | that's the maximum amount of memory this CPU can address without hacks (like shadow mem , virtual addresses, etc) | 13:43 |
| sicelo | yes, following | 13:44 |
| freemangordon | also, assume linear addressing (no paging) | 13:44 |
| freemangordon | so, each byte of that memory will have address from 0000 to FFFF | 13:44 |
| freemangordon | ok? | 13:45 |
| sicelo | yes, am with you | 13:45 |
| freemangordon | so, consider this C code: | 13:45 |
| freemangordon | void main() { | 13:46 |
| freemangordon | int a = 2; | 13:46 |
| freemangordon | int *pa = &2; | 13:46 |
| freemangordon | *pa = 3; | 13:46 |
| freemangordon | } | 13:46 |
| freemangordon | what we do here is: | 13:46 |
| freemangordon | we declare a var and assign 2 to it | 13:46 |
| sicelo | yes. understandable | 13:47 |
| freemangordon | it the 'real life', i.e. the memory of the CPU, this will mean that on some address (in the stack, as this is local variable) we will have value of 0x0002 stored | 13:47 |
| freemangordon | for simplicity, lets assume that int is 16 bits on that platform | 13:48 |
| freemangordon | oops, I made a typo | 13:48 |
| freemangordon | int *pa = &2; should be int *pa = &a; | 13:48 |
| freemangordon | this line gets the *address* of the memory where the value of a is stored | 13:49 |
| sicelo | stack and heap I'm also not too clear about, but I guess that's not too relevant for this | 13:49 |
| freemangordon | it is not | 13:49 |
| freemangordon | those are just different parts of memory | 13:49 |
| freemangordon | so, do you get the idea of "gets the *address* of...' statement? | 13:50 |
| sicelo | &a is the address. yes I get that | 13:50 |
| sicelo | so *pa is what stores that address | 13:50 |
| freemangordon | so, if the value of a (0x0002) is stored at address 0xBEEF, then pa will have a value of 0xBEEF | 13:50 |
| freemangordon | exactly | 13:51 |
| freemangordon | so, '&' means 'take the address of' | 13:51 |
| freemangordon | is it clear so far? | 13:51 |
| sicelo | yes, | 13:51 |
| freemangordon | BTW, the *value* of pa is also stored in the memory, lets assume on address 0xDEAD | 13:52 |
| sicelo | right, yes make sense | 13:52 |
| freemangordon | another thing - pa is *pointer to int* | 13:52 |
| freemangordon | which means 'this variable is of such a type, that it holds and address of a memory block that contains int value' | 13:53 |
| freemangordon | s/and/an | 13:53 |
| freemangordon | we can take the address of pa as well, with int **ppa = &pa; | 13:54 |
| freemangordon | mind those '**' | 13:54 |
| freemangordon | this is pointer-to-poiner-to-int | 13:54 |
| sicelo | right, yes | 13:55 |
| freemangordon | and we can do that as many times as we want, but in practice it stops at '***' | 13:55 |
| freemangordon | any questions so far? | 13:55 |
| sicelo | i completely understand | 13:56 |
| freemangordon | great | 13:56 |
| freemangordon | no, what we can do if we want to assign 3 to a | 13:56 |
| freemangordon | we can simply do a=3; | 13:56 |
| sicelo | a = 3 :-) | 13:56 |
| freemangordon | right | 13:56 |
| freemangordon | but we can cheat, and do '*pa = 3' instead ;) | 13:57 |
| freemangordon | that's called de-referencing | 13:57 |
| freemangordon | pa 'references' a as it hold a address | 13:57 |
| sicelo | store 3 in the location specified by pa? | 13:57 |
| freemangordon | exactly | 13:58 |
| freemangordon | '*' operator when used with pointer means: | 13:58 |
| freemangordon | do the next operation ( = in our case) with the *memory* that is pointed by the pointer | 13:58 |
| freemangordon | we can do pa = (int *)3 as well | 13:59 |
| freemangordon | operation in the brackets is called 'casting' | 13:59 |
| freemangordon | otherwise compiler will spit on us | 13:59 |
| sicelo | yes, i know casting | 13:59 |
| freemangordon | so pa = (int *)3 will put 3 at memory address 0xDEAD instead of 0xBEEF | 14:00 |
| freemangordon | clear? | 14:00 |
| freemangordon | read the backscroll for which var is stored where in the memory | 14:01 |
| sicelo | this one's a bit confusing because it sounds like put the address of 3 in pa? | 14:03 |
| freemangordon | look at it like pa = 3 | 14:05 |
| freemangordon | (int *) is to make compiler happy | 14:06 |
| freemangordon | if we want to 'take the address of 3' (which is not allowed), we shall do &3 | 14:07 |
| sicelo | ah right | 14:07 |
| freemangordon | one may ask why we need pointers at all? | 14:07 |
| sicelo | that i understand ... | 14:08 |
| freemangordon | ok | 14:08 |
| sicelo | so we can, for example, modify variables in place, e.g. strings | 14:08 |
| freemangordon | 2 of the main reasons are - dynamic memory allocation and parameters passing | 14:08 |
| freemangordon | one note: C have no idea what 'string' is ;) | 14:09 |
| sicelo | yes, i recall :-) | 14:10 |
| freemangordon | cool | 14:10 |
| freemangordon | ok, so far anything unclear? | 14:10 |
| sicelo | it's clear. | 14:11 |
| freemangordon | cool | 14:11 |
| freemangordon | now, about . and -> | 14:11 |
| freemangordon | those are used with structs | 14:11 |
| sicelo | of course the `pa = (int *)3` example i'll need to revisit :-) | 14:11 |
| freemangordon | lemme elaborate on it | 14:12 |
| freemangordon | it will assign 3 to pa, and if you try to dereference pa by doing *pa = 5, most - probably you'll get segfault, as it will try to store 0x0005 at memory address 0x0003 | 14:13 |
| sicelo | i see | 14:14 |
| freemangordon | usually addresses at the beginning of the address space are reserved for the OS, or interrupt vectors, etc. but that's irrelevant here - what is relevant is that you access address that does not belong to your program, simply to speak | 14:14 |
| sicelo | ignoring the (int *) part, so it's pa = 3 ... i.e. make pa hold 3, so the pointer points at 0x0003? | 14:15 |
| freemangordon | exactly | 14:15 |
| sicelo | ok. i was hung up on the (int *) | 14:15 |
| freemangordon | that's just for the compiler | 14:15 |
| sicelo | i think i get it properly now | 14:15 |
| freemangordon | now, you cans see things like char *s = NULL; all over the place | 14:16 |
| freemangordon | usually pointers are initialized with 0 (NULL is defined as (void *)0 most of the times) | 14:17 |
| freemangordon | this is done so if we use that pointer to hold address of a dynamically allocated memory, we can later on check if we need to free it or not | 14:17 |
| freemangordon | if (s != NULL) | 14:18 |
| freemangordon | free(s); | 14:18 |
| freemangordon | no, . and -> | 14:18 |
| freemangordon | those are used to access structure members | 14:18 |
| freemangordon | -> is used when you have a *pointer* to structure | 14:19 |
| sicelo | we need to free it if it's non-NULL? | 14:19 |
| freemangordon | well, usually is it more complicated: | 14:19 |
| freemangordon | char *s = NULL; | 14:20 |
| freemangordon | if (some_condition()) | 14:20 |
| freemangordon | s = malloc(128); | 14:20 |
| freemangordon | if (s) | 14:20 |
| freemangordon | free(s); | 14:20 |
| moparisthebest | "assume linear addressing" reminded me of this old gem: https://www.moparisthebest.com/images/how-memory-works.png | 14:20 |
| freemangordon | yeah, that's why I made that note at the very beginning ;) | 14:21 |
| freemangordon | sicelo: so, any specific questions you want to ask? | 14:23 |
| sicelo | sorry, got disconnected for a moment | 14:23 |
| sicelo | let me re read | 14:23 |
| sicelo | I think I still understand so far, | 14:24 |
| sicelo | when is -> used | 14:26 |
| sicelo | sorry, I mean . | 14:27 |
| freemangordon | so, it is not clear to you when '.' and when '->' are used? | 14:27 |
| freemangordon | see this: | 14:28 |
| freemangordon | struct struct1 {int a;}; | 14:29 |
| freemangordon | struct struct1 s1; | 14:29 |
| freemangordon | struct struct1 *ps1; | 14:29 |
| freemangordon | s1.a = 5; | 14:29 |
| freemangordon | ps1->a = 8; | 14:29 |
| freemangordon | (*ps1).a = 9; | 14:29 |
| freemangordon | so, when you have a struct variable, you use '.' to access its members | 14:30 |
| freemangordon | when you have a *pointer* to struct variable you use -> to access it members | 14:31 |
| sicelo | makes perfect sense | 14:31 |
| freemangordon | or, you can *de-reference* that pointer and use '.' to access its members | 14:31 |
| freemangordon | the last 3 lines ^^^ all do the same - assign a value (5,8,9) to 'a' member of 's1' variable, which is of type 'struct struct1' | 14:32 |
| freemangordon | sicelo: do you see anything wrong with my code ^^^ | 14:34 |
| sicelo | nowhere do you set ps1 to the address of s1, I think | 14:35 |
| * freemangordon :claps: | 14:35 | |
| freemangordon | how would you write that? | 14:35 |
| sicelo | struct struct1 *ps1 = &s1; | 14:36 |
| freemangordon | great | 14:36 |
| freemangordon | 2 more things and I think we are ready: | 14:37 |
| freemangordon | in the ^^^ example ps1 was 'uninitialized pointer', pointing to some random address of the memory, so noone knows what happens when you de-reference it | 14:38 |
| freemangordon | the same case at with pa = (int *)3 | 14:38 |
| freemangordon | uninitialized pointers are very bad, so you should be extremely careful, they are one of the reasons why people don;t like C | 14:39 |
| freemangordon | but, what is even worse, are the so-called 'dangling pointers' | 14:39 |
| freemangordon | see: | 14:40 |
| freemangordon | char *s = malloc(128); | 14:40 |
| freemangordon | s[10] = 'a'; | 14:40 |
| freemangordon | free(s); | 14:41 |
| freemangordon | s[12] = 'b'; | 14:41 |
| freemangordon | after 'free(s);' line, s becomes 'dangling', and de-referencing it again leads to memory access of a memory that does not belong to us, but, the ugly thing is that memory *might* still contain valid data | 14:43 |
| freemangordon | 'dangling pointer' bugs are usually very hard to catch | 14:43 |
| sicelo | must first set it to NULL? | 14:44 |
| freemangordon | will not help | 14:44 |
| sicelo | just manually keep track of what you're doing? | 14:45 |
| freemangordon | basicly :) | 14:45 |
| freemangordon | my point was - one should be very careful when using pointers | 14:46 |
| sicelo | i need to play with this some more | 14:46 |
| freemangordon | sure | 14:46 |
| freemangordon | let it settle, please ask if anything is still unclear | 14:46 |
| sicelo | what was the second thing? <<< freemangordon> 2 more things and I think we are ready:>> ... or it's uninitialized pointers, and dangling pointers? | 14:48 |
| freemangordon | yes | 14:48 |
| freemangordon | those 2 types for 'bad' pointers | 14:48 |
| Wizzup | yes please take over maintainership | 15:13 |
| Wizzup | @ dorian | 15:13 |
| Wizzup | (if you want) | 15:13 |
| sicelo | i can take it ... i think pere said he can't | 15:16 |
| sicelo | anyway i guess who maintainer is doesn't matter too much ... MRs will be merged as and when they become available | 15:17 |
| dsc_ | C is good if you have unlimited time for a project | 15:18 |
| dsc_ | but in the real world... :D | 15:18 |
| sicelo | isn't it on par with C++ though? | 15:22 |
| sicelo | or what would make C++ dev faster? | 15:22 |
| pere | heh. C got a lot of rope to hang oneself in, and C++ got all of that in addition a lot of guns to shoot yourself in the foot with. :) | 15:25 |
| dsc_ | sicelo: I would say the same about c++ tbh ^^ | 15:49 |
| dsc_ | the reason everyone uses Electron is time-to-market | 15:52 |
| pere | note, I like both C and C++, and regularly program in both. :) | 16:16 |
| dsc_ | my point was that both C and C++ take more effort, which is a useless statement to make because everyone knows already :D | 16:18 |
| freemangordon | dsc_: well, if TTM is the only thing one cares about, then in wrong hands c/++ might take more time | 16:32 |
| freemangordon | but, if you want to make your customer happy with what you do, then there are other things to consider | 16:33 |
| freemangordon | also, c/++ is programming language, and what really matters are libraries | 16:34 |
| freemangordon | so, I don;t think TTM for a Qt project is much (if at all) longer than any other language | 16:35 |
| freemangordon | dsc_: on a abook side: did you see what I pasted ^^^ | 16:36 |
| freemangordon | *an | 16:36 |
| dsc_ | yes thank you :) | 16:37 |
| freemangordon | does it work? | 16:37 |
| dsc_ | did not try | 16:37 |
| freemangordon | ok | 16:37 |
| dsc_ | about TTM, i am passionate about making GUI development more accessible/faster for programmers, I do think Qt is quite slow overall in terms of productivity compared to e.g web technology | 16:46 |
| dsc_ | so I integrated Qt into a game engine and provide some high level API | 16:48 |
| dsc_ | https://godotwebview.com/ | 16:50 |
| freemangordon | OTOH, what I do for living is mostly backend development, and there are things we developed 20 years ago that are still in production, running 24/7 | 16:54 |
| freemangordon | so it really depends on what relations with the customer you have | 16:54 |
| freemangordon | if it is about 'grab the money and run', then yeah, TTM is the most important | 16:55 |
| freemangordon | if you want to establish long-term relations, not so | 16:55 |
| freemangordon | not to say that it still matters if you require 16 CPUS/64GB RAM vs 2 CPUS/4 GB RAM, with the qt implementation running 10 times faster than the same thing running tomcat/java etc | 16:57 |
| dsc_ | hmm yeah so generally speaking I disagree with you, but the context also matters. For Maemo it is good to make use of robust software, or however you want to classify it | 16:58 |
| dsc_ | but for a commercial company, its best to focus on productivity, TTM, that kind of thing | 16:59 |
| dsc_ | else you just get ran over by a competitor | 17:00 |
| dsc_ | who uses Electron :D | 17:00 |
| freemangordon | no, it is not that simple | 17:00 |
| freemangordon | trust me, we basically run out of competitors here for the last 20 years, while using c/++ as main language | 17:01 |
| dsc_ | hehe | 17:01 |
| freemangordon | no, really | 17:01 |
| freemangordon | programming language is just a techology | 17:02 |
| freemangordon | usually, for big commercial project, 1 or 2 moths mean nothing | 17:02 |
| freemangordon | *months | 17:02 |
| dsc_ | but again, the context matters. Your sector absolutely requires robust/stable software. Not software made by college students on adderall, which is what sillicon valley runs on. | 17:02 |
| freemangordon | sure | 17:02 |
| freemangordon | and I agree that there is no "one size to fit them all" | 17:03 |
| dsc_ | freemangordon: hmm | 18:43 |
| dsc_ | ==== haze/jabber/stevejobs_40xmpp_2ewajer_2eorg0-dsc@xmpp.is published: 1 | 18:43 |
| dsc_ | 1 = OSSO_ABOOK_PRESENCE_STATE_NO | 18:43 |
| dsc_ | https://plak.infrapuin.nl/selif/65yv1a3g.txt | 18:43 |
| dsc_ | https://plak.infrapuin.nl/selif/j6znzuqo.png <== added as friend | 18:45 |
| dsc_ | let me check subscribed.. | 18:45 |
| dsc_ | ah ok, nvm it works | 18:46 |
| dsc_ | published: 1 | 18:47 |
| dsc_ | subscribed: 0 | 18:47 |
| dsc_ | so I am subscribed but not published, even though the remote party can see my status | 18:47 |
| freemangordon | could you show me the vcard? | 18:47 |
| freemangordon | roster one | 18:47 |
| dsc_ | i noticed it does not print the vcard, but ill try again | 18:47 |
| freemangordon | it does here | 18:47 |
| freemangordon | G_MESSAGES_DEBUG=all OSSO_ABOOK_DEBUG=all | 18:48 |
| freemangordon | hmm, wait | 18:49 |
| dsc_ | this is maybe my fault, I might be in a weird XMPP state | 18:50 |
| freemangordon | dsc_: define OSSO_ABOOK_DEBUG | 18:50 |
| dsc_ | qputenv("G_MESSAGES_DEBUG", "all"); | 18:50 |
| dsc_ | qputenv("OSSO_ABOOK_DEBUG", "all"); | 18:50 |
| dsc_ | this used to work | 18:50 |
| dsc_ | ill try via commandline | 18:50 |
| freemangordon | you have to #define OSSO_ABOOK_DEBUG | 18:50 |
| dsc_ | oh define | 18:50 |
| freemangordon | mhm | 18:50 |
| freemangordon | https://github.com/maemo-leste/osso-abook/blob/master/lib/osso-abook-debug.h#L81 | 18:51 |
| dsc_ | cool | 18:52 |
| dsc_ | yes that works | 18:52 |
| dsc_ | lets see | 18:52 |
| dsc_ | https://plak.infrapuin.nl/selif/pobma4ec.txt | 18:53 |
| freemangordon | X-TELEPATHY-PUBLISHED:no | 18:53 |
| dsc_ | X-TELEPATHY-SUBSCRIBED:yes\r\nX-TELEPATHY-PUBLISHED:no | 18:53 |
| dsc_ | yeah | 18:53 |
| dsc_ | PEKBAC | 18:53 |
| freemangordon | heh | 18:53 |
| freemangordon | wrong message? | 18:53 |
| dsc_ | its weird though | 18:53 |
| dsc_ | published = no = remote cannot see my status | 18:54 |
| dsc_ | but I can see it | 18:54 |
| freemangordon | so, what is the PEBCAK? | 18:54 |
| freemangordon | I see nothing wrong | 18:54 |
| freemangordon | ah, right | 18:55 |
| freemangordon | 1 is NO, 0 is YES | 18:55 |
| dsc_ | status publish is no, so remote should not see my status (online/offline, etc) | 18:55 |
| dsc_ | I think? not sure | 18:55 |
| freemangordon | me neither, lets read the docs | 18:56 |
| dsc_ | with PEKBAC I meant that maybe I am not accepting the friend requests the right way | 18:59 |
| freemangordon | I see | 18:59 |
| freemangordon | lemme see what eds plugin does | 18:59 |
| dsc_ | I do `contact->authorizePresencePublication()` for accepting | 19:00 |
| dsc_ | and then I check the subscription state, if its 'no' I send a `contact->requestPresenceSubscription()` | 19:00 |
| dsc_ | so that publicity for both directions is the same | 19:01 |
| dsc_ | but ehh | 19:01 |
| dsc_ | ill read some tp-qt code | 19:01 |
| freemangordon | I see some local/remote states | 19:02 |
| dsc_ | freemangordon: I think you should not look into this, its for me to figure out | 19:07 |
| dsc_ | thanks | 19:08 |
| dsc_ | (since this is probably my fault) | 19:08 |
| freemangordon | still, I want to understand how is it supposed to work | 19:08 |
| freemangordon | I agree there is no obvious problem in tp/abook | 19:09 |
| freemangordon | the fuck? freedesktop.org went down :( | 19:10 |
| dsc_ | https://plak.infrapuin.nl/selif/iu7je1to.png | 19:16 |
| dsc_ | this is from pidgin | 19:16 |
| dsc_ | it shows 2 statusses | 19:16 |
| dsc_ | not sure if relevant | 19:16 |
| dsc_ | nvm, its pidgin + maemo | 19:17 |
| dsc_ | hmm ok it works now. I blame some weird state I got myself in earlier. | 19:23 |
| dsc_ | (I blame Wizzup's server :P) | 19:23 |
| freemangordon | seems pidgin has issues, at least here | 19:23 |
| freemangordon | yeah, maybe the server is to blame | 19:24 |
| freemangordon | going offline for a bit, to restart pidgin | 19:24 |
| freemangordon | didn't help | 19:26 |
| freemangordon | X-TELEPATHY-PUBLISHED:local-pending | 19:28 |
| freemangordon | whatever is that supposed to mean | 19:28 |
| dsc_ | http://maemo.org/api_refs/5.0/beta/libosso-abook/libosso-abook-osso-abook-presence.html#OssoABookPresenceState | 19:28 |
| freemangordon | yes, but what is that supposed to mean in TP terms | 19:29 |
| dsc_ | :) | 19:29 |
| freemangordon | I see 'not authorized' in pidgin | 19:29 |
| freemangordon | and in the same time I can chat | 19:29 |
| dsc_ | you can always chat | 19:30 |
| freemangordon | so, that relates to presence only? | 19:30 |
| freemangordon | what if it is blocked? | 19:30 |
| dsc_ | yes | 19:30 |
| dsc_ | ehhhhhhh | 19:30 |
| freemangordon | no messages from contact | 19:31 |
| dsc_ | X-TELEPATHY-PUBLISHED:local-pending <== I *think* this means you have to publish YOUR status (from maemo) | 19:31 |
| dsc_ | to pidgin | 19:31 |
| freemangordon | no, that's the status of remote contact (the one in pidgin) | 19:32 |
| dsc_ | i dont think so, but maybe you are right | 19:33 |
| dsc_ | the connection manager adds these attributes | 19:34 |
| dsc_ | from the perspective of CM | 19:34 |
| dsc_ | so local = local | 19:34 |
| dsc_ | maybe... | 19:34 |
| freemangordon | yeah, could be, but FDO is down and I can;t look into docs | 19:35 |
| jrayhawk | freemangordon: oh, that's not good. I'll look into it. | 19:35 |
| freemangordon | jrayhawk: hmm, sorry, lost the context | 19:35 |
| freemangordon | ah, FDO | 19:35 |
| jrayhawk | okay, i fixed it for now. not sure why that happened. | 19:36 |
| freemangordon | seems back up | 19:36 |
| freemangordon | jrayhawk: thanks! | 19:37 |
| freemangordon | dsc_: https://telepathy.freedesktop.org/spec//Channel_Interface_Group.html#Property:LocalPendingMembers | 19:37 |
| dsc_ | no, not group I think | 19:38 |
| dsc_ | this is roster stuff | 19:38 |
| freemangordon | this is the dbus interface that's used | 19:38 |
| dsc_ | ok | 19:38 |
| freemangordon | but the point is that you are right | 19:38 |
| freemangordon | I send "auth request" from pidgin | 19:38 |
| freemangordon | *sent | 19:39 |
| freemangordon | but, no way to accept it from contacts | 19:39 |
| dsc_ | right | 19:39 |
| freemangordon | I wonder if it is possible to to reset that state somehow | 19:39 |
| freemangordon | as it seems that's kept on the server | 19:40 |
| dsc_ | yes | 19:40 |
| dsc_ | in tp-qt this is `removePresenceSubscription` and `removePresencePublication` | 19:40 |
| freemangordon | remove?!? | 19:41 |
| dsc_ | with state you mean subscribption/presence state? | 19:42 |
| dsc_ | PendingOperation *requestPresenceSubscription(const QString &message = QString()); | 19:42 |
| dsc_ | PendingOperation *removePresenceSubscription(const QString &message = QString()); | 19:42 |
| dsc_ | PendingOperation *authorizePresencePublication(const QString &message = QString()); | 19:42 |
| dsc_ | PendingOperation *removePresencePublication(const QString &message = QString()); | 19:42 |
| freemangordon | https://telepathy.freedesktop.org/spec//Connection_Interface_Contact_List.html | 19:42 |
| freemangordon | I think this is the correct doc | 19:42 |
| dsc_ | it is, yes | 19:43 |
| dsc_ | for removePresenceSubscription, tp-qt eventually calls https://telepathy.freedesktop.org/spec//Connection_Interface_Contact_List.html#Method:Unsubscribe | 19:43 |
| freemangordon | phew: https://telepathy.freedesktop.org/spec//Connection_Interface_Contact_List.html#Contact-Attribute:subscribe | 19:43 |
| freemangordon | finally | 19:43 |
| freemangordon | yeah, we must read that couple of times :) | 19:44 |
| dsc_ | xD | 19:45 |
| dsc_ | this removal is another thing I wanted to bring up, because I dont think I get signals when the remote does that | 19:47 |
| dsc_ | but not now | 19:47 |
| freemangordon | I think you shall get some 'remote-rejected' state | 19:48 |
| freemangordon | ok, there is something wrong with the sever, I was seeing presence before requesting authorization | 19:52 |
| freemangordon | *server | 19:52 |
| dsc_ | I delete stevejobs (maemo) from my friendlist and the only thing that seems to change is online->offline, it will still say X-TELEPATHY-SUBSCRIBED:yes\r\nX-TELEPATHY-PUBLISHED:yes | 19:52 |
| dsc_ | well ok, this is from perspective of local | 19:53 |
| dsc_ | but still, I expect a signal | 19:53 |
| freemangordon | you have contact-changed signal, no? | 19:53 |
| freemangordon | or rather - contacts-changed | 19:53 |
| dsc_ | yes, this fires because status change (online->offline) | 19:54 |
| dsc_ | but still X-TELEPATHY-SUBSCRIBED:yes\r\nX-TELEPATHY-PUBLISHED:yes | 19:54 |
| freemangordon | yes, that's the local state, no? | 19:54 |
| dsc_ | yes | 19:54 |
| freemangordon | so I see no issue | 19:54 |
| dsc_ | true | 19:54 |
| freemangordon | on a side note - I am really glad abook/eds plugin handle all this properly | 19:55 |
| freemangordon | this code was never tested outside fremantle | 19:56 |
| dsc_ | yes :) it works well | 19:56 |
| freemangordon | mhm | 19:56 |
| Wizzup | sicelo: icon for OTP? :D | 21:02 |
| sicelo | still on the way 🤠| 21:08 |
| Wizzup | :D | 21:23 |
| sicelo | Wizzup: maybe give me access to dorian repo already | 21:35 |
| Wizzup | sure | 21:40 |
| Wizzup | btw guys, work really caught up with me, which I haven't been too active | 21:40 |
| Wizzup | I'm getting back into the all of this soon | 21:40 |
| dsc_ | Wizzup: website :) | 21:41 |
| Wizzup | sicelo: you should have access now | 21:41 |
| Wizzup | dsc_: ok, after this mtg I will do it :) | 21:41 |
| sicelo | thanks! | 22:26 |
| dsc_ | im finished but needs some testing | 23:12 |
| dsc_ | will continue tomorrow | 23:12 |
| Wizzup | dsc_: on the website or something else? | 23:15 |
| dsc_ | on Tp stuff | 23:19 |
| dsc_ | website is OK | 23:19 |
| sicelo | Wizzup: btw addition in github repo also automatically grants on Jenkins side? | 23:19 |
| sicelo | seems not. Please also add me Jenkins side when you find a chance. | 23:27 |
| arno11 | is it a new repo or ? | 23:28 |
| pere | sicelo: look like I will have to dig out my n900 tomorrow to test the new dorian. :) | 23:28 |
| sicelo | pere: https://github.com/maemo-leste-extras/dorian/issues/18 is fixed now, at least the URL. the error checking will have to wait for another day. should hit the repos as soon as build has happened | 23:29 |
| sicelo | yeah, please do ;-) | 23:29 |
| sicelo | however, https://github.com/maemo-leste-extras/dorian/issues/12 becomes more visible. unfortunately that's something that, at least from my end, has to wait | 23:30 |
| pere | sicelo: do you use dorian yourself to read books? | 23:31 |
| sicelo | i used to read them a lot on fremantle. nowadays no, not really. and the search function i had never used even under Fremantle | 23:32 |
| sicelo | i still have dorian installed on leste for whenever i get an epub to read, hence i fixed the volume key based page navigation about a week ago since i was so used to that from fremantle days | 23:33 |
| sicelo | arno11: no, old repo, and i've just taken up maintainership. | 23:38 |
| sicelo | dorian e-book reader, in case you do use it :-) | 23:38 |
| arno11 | ah ok | 23:45 |
| arno11 | i never tried it btw | 23:45 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
