#tde-devs < 2025/08/24 > |
| [02:32] | kasesag has quit (Server closed connection) |
| [02:32] | kasesag has joined |
| [02:59] | micheleC has joined |
| [02:59] | micheleC: @Fat-Zer: bear with me for asking a few questions, since I didn't go through the tsak or tdmtsak code in details. |
| [03:00] | micheleC: what are the differences/relation between tsak and tdmtsak? I was unanware of tsak in full, while I always thought tdmtsak was responsible for the SAK logic at login/lock screen |
| [03:01] | micheleC: can you share more info if you konw more? that would space some code analysis :-) |
| [03:01] | micheleC: *would spare |
| [07:39] | Fat-Zer has quit (Ping timeout: 258 seconds) |
| [07:52] | Fat-Zer has joined |
| [12:26] | micheleC has left (Kopete 0.12.7 : http://trinitydesktop.org) |
| [13:00] | Fat-Zer: sorry, have missed the questions... IRC clients usually don't recognize mentions of a nick with @... |
| [13:02] | Fat-Zer: to be fair I don't know much about it either... tsak is at least used to check if sak functionality is available. It seems to have some other stuff going on, but I'm not sure whether it is actually used. |
| [18:30] | Fat-Zer: actually tsak seem to do all heavy lifting... tdmtsak just checks if it is running |
| [19:52] | Fat-Zer: *and communicates with it |
| [20:31] | kasesag has quit (Ping timeout: 258 seconds) |
| [20:33] | kasesag has joined |
#tde-devs < 2025/08/24 > |
© 2010-2026 Trinity Desktop Project