--- Log opened Tue Apr 10 00:00:23 2018
00:28 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 256 seconds]
00:28 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n
00:28 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed
00:28 #navit: < Navit> See compile results history at http://legacy.navit-project.org/logs/navit/stats.html
00:33 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
00:35 -!- aerostitch [~aerostitc@VEVO-LLC.bar2.SanFrancisco1.Level3.net] has quit [Ping timeout: 264 seconds]
00:58 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 260 seconds]
01:09 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
02:09 -!- aerostitch [~aerostitc@c-67-164-55-119.hsd1.ca.comcast.net] has joined #navit
03:58 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
04:07 -!- noradtux [~noradtux@port-20277.pppoe.wtnet.de] has quit [Ping timeout: 265 seconds]
04:07 -!- noradtux [~noradtux@2a04:4540:8c04:aa01::1] has joined #navit
04:45 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 260 seconds]
04:48 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
04:52 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
04:52 -!- mode/#navit [+v xenos1984] by ChanServ
05:32 -!- aerostitch [~aerostitc@c-67-164-55-119.hsd1.ca.comcast.net] has quit [Remote host closed the connection]
09:55 -!- ColdFyre_ [~lenny@24-113-172-199.wavecable.com] has joined #navit
09:56 -!- ColdFyre [~lenny@24-113-172-199.wavecable.com] has quit [Ping timeout: 264 seconds]
14:23 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
14:54 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
14:54 -!- mode/#navit [+v xenos1984] by ChanServ
15:20 -!- aerostitch [~aerostitc@VEVO-LLC.bar2.SanFrancisco1.Level3.net] has joined #navit
16:07 #navit: <@KaZeR> howdy
16:07 #navit: <+jkoan> hi KaZeR
16:07 #navit: <+jkoan> 'sup?
16:11 #navit: <@KaZeR> damn you guys are all stealing my catchphrase!
16:13 #navit: <+jkoan> yes, this was intended 
16:16 #navit: <@KaZeR> nicely done
16:17 #navit: <@KaZeR> do you think that you could help on the play store compliance thing? the clock is ticking
16:17 #navit: <+jkoan> did you read the new mail from google play?
16:17 #navit: <+jkoan> i dont really know whats the problem with our app
16:17 #navit: <@KaZeR> i did, but i'm not sure that it applies to us, does it?
16:18 #navit: <+jkoan> not really sure, dident found anything that directly match to us
16:18 #navit: <@KaZeR> the problem with our app is probably for this new gdpr compliance law - we just need to state that we don't collect data i believe
16:18 #navit: <@KaZeR> yeah same here. i think that we can ignore the latest email
16:20 #navit: <+jkoan> so in the worth case just remove acra? or only add a message which said that we dont collect data
16:20 #navit: <+jkoan> ?
16:24 #navit: <@KaZeR> yeah the easiest way out for now might be to remove ACRA
16:25 #navit: <@KaZeR> You must be transparent in how you handle user data (e.g. information provided by a user, collected about a user, and collected about a user’s use of the app or device), including by disclosing the collection, use, and sharing of the data, and you must limit use of the data to the description in the disclosure.If your app collects and transmits personal or sensitive user data unrelated to functionality
16:25 #navit: <@KaZeR> described prominently in the app’s listing on Google Play or in the app interface, then prior to the collection and transmission, it must prominently highlight how the user data will be used and have the user provide affirmative consent for such use.
16:25 #navit: <@KaZeR> the thing is that i don't see where we are supposed to discoles the collection and use of the data
16:26 #navit: <@KaZeR> *disclose
16:26 #navit: <@KaZeR> "You may want to consider adding a dialog notifying users of user data collection during crash reporting to ask their consent before the collection occurs."
16:26 #navit: <+jkoan> so if we would have the setup like we designed on draw.io and would add a message it would be enought?
16:28 #navit: <@KaZeR> i think so yes. The question is how can we make sure to display that before collecting crash data.. because it's a process external to navit
16:32 #navit: <@KaZeR> https://github.com/ACRA/acra/wiki/Interactions
16:32 #navit: <+jkoan> i would like the notification thing
16:33 #navit: <@KaZeR> the Dialog one might fit our need maybe. The user has to accept, and we can add a small blurb about the data collection
16:33 #navit: <@KaZeR> yeah notification might work too
16:33 #navit: <+jkoan> i like "small blurb" the phrase :D
16:34 #navit: <@KaZeR> if we can add a link in the notification or dialog, we could link to a more detailed page on the wiki or even better a privacy statement on our website
16:34 #navit: <@KaZeR> :)
16:34 #navit: <+jkoan> sounds nice
16:35 #navit: <+jkoan> the notification thing can also have customized text, but no link :/ 
16:39 #navit: <+jkoan> do you know where the annotation should be?
16:39 #navit: <@KaZeR> the annotation?
16:40 #navit: <+jkoan> the @AcraNotification(resText = R.string.notification_text, resTitle = R.string.notification_title,         resChannelName = R.string.notification_channel) line
16:40 #navit: <+jkoan> this is a annotation, its a java thing :D
16:46 #navit: <@KaZeR> i think it probably has to be somewhere here : https://github.com/navit-gps/navit/blob/94a3c994a7a5970be3b3bb9d290f9e1d8d437034/navit/android/src/org/navitproject/navit/NavitAppConfig.java but that's all i know
16:46 #navit: <+jkoan> would also be my idea
16:57 #navit: <+jkoan> i cant promise when i have time to look into it, but i try to implement it :) 
17:16 #navit: <@KaZeR> thanks! I'll try to reach out to jandegr too, he might know better
19:12 -!- jandegr [d5d38fe3@gateway/web/freenode/ip.213.211.143.227] has joined #navit
19:15 #navit: < jandegr> hi kazer
19:19 -!- jandegr [d5d38fe3@gateway/web/freenode/ip.213.211.143.227] has quit [Quit: Page closed]
19:21 #navit: <@KaZeR> damn that was quick
21:03 -!- ilovekiruna [~ilovekiru@ip1f129b37.dynamic.kabel-deutschland.de] has joined #navit
21:03 -!- mode/#navit [+v ilovekiruna] by ChanServ
21:20 #navit: <+ilovekiruna> hi all
21:32 -!- aerostitch [~aerostitc@VEVO-LLC.bar2.SanFrancisco1.Level3.net] has quit [Remote host closed the connection]
21:53 #navit: <@KaZeR> hi ilovekiruna 
22:09 #navit: <+ilovekiruna> hi KaZeR
22:09 #navit: <+ilovekiruna> I have a brief programming question for you again
22:09 #navit: <+ilovekiruna> are you also familiar with C++11?
22:10 #navit: <@KaZeR> i'm more familiar with C than C++
22:14 #navit: <+ilovekiruna> hmm, ok
22:14 #navit: <+ilovekiruna> but would still like to challenge you
22:15 #navit: <+ilovekiruna> C++11 considers a new keyword, nullptr, how can one do sth like this in C or C++ in older versions
22:22 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
22:25 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 256 seconds]
22:33 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
22:50 #navit: <@KaZeR> so you want to backport the nullptr keyword?
22:55 -!- Horwitz [~mich1@p200300800E021400022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
23:07 -!- Horwitz [~mich1@p200300800E7F3900022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:07 -!- mode/#navit [+o Horwitz] by ChanServ
23:53 -!- Horwitz [~mich1@p200300800E7F3900022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
--- Log closed Wed Apr 11 00:00:24 2018