12.03.2018, 15:18, "Volker Krause" :
> On Monday, 12 March 2018 13:00:31 CET Aleksey Kontsevich wrote:
>> 12.03.2018, 11:25, "Volker Krause" :
>> > I'm fine with changing things, I'm just still trying to understand the
>> > requirement
12.03.2018, 15:18, "Volker Krause" :
> On Monday, 12 March 2018 11:06:59 CET Aleksey Kontsevich wrote:
>You could still do that as part of the custom data source, the request does
> after all only have to happen once, rather than on every submission.
I agree - only once
12.03.2018, 11:25, "Volker Krause" :
> I'm fine with changing things, I'm just still trying to understand the
> requirements correctly :)
Main idea and requirements: we need more generic and extendable approach, in
particular:
- network communication
- local statistics log
- settings
- UI: audit
12.03.2018, 11:25, "Volker Krause" :
> On Sunday, 11 March 2018 16:23:33 CET Aleksey Kontsevich wrote:
>> Thanks, Volker, for the answer. Will think more and try it in action
>> provider<->server<->analytic app to see how it works to better understand.
>&
Thanks, Volker, for the answer. Will think more and try it in action provider<->server<->analytic app to see how it works to better understand. However still have some concerns: if I want to get such id from the server I need to write separate logic, API, etc. I see that we can create, subclass, ex
Hi Volker,
Have some questions. I've read Telemetry discussion in kde-community mailing
list, however some KUserFeedback logic is not quite clear:
https://www.mail-archive.com/kde-community@kde.org/msg03898.html
You said data is submitted once per week to a server. How the user is
identified
