These are chat archives for whereat/contrib

24th
Apr 2016
Meitar M.
@meitar
Apr 24 2016 07:52
Is anyone here familiar with OwnTracks? http://blog.owntracks.org/post/81979947611/where-is-everybody-owntracks-at-the-office Looked relevant at first blush but haven't dug deep. Just curious.
aguestuser
@aguestuser
Apr 24 2016 20:47
@jamesattard -- hi! sorry for slow response! the call to startLocationPolling() you referenced in your email invokes a native module we wrote to wrap Mapzen's LOST Location Provider.
we published the wrapper on npm, so you can include it in your project with npm install --save react-native-lostlocationprovider
then (optionally) wrap calls to start the location provider and register callbacks to execute when a new location is produced in a service wrapper like we did here
aguestuser
@aguestuser
Apr 24 2016 20:53
since the actual LocationProvider is running on the native Android layer, it can handle background tasks. new locations are emitted as events to the JS layer. we've tested that it works, although haven't done any tests to see if it continues to work when app doesn't have focus, phone is in users' pocket, etc... as we have confirmed is the case with a normal native app.
for more on native modules, this section in the docs is okay, but feels a bit hastily composed. i'm trying to work on a blog post about how to properly implement and test them.
hopefully that helps?
@meitar -- saw that a couple weeks ago with GREAT curiosity! started digging through the docs but have been distracted since.
at first glance looks pretty good!
they have a nice booklet for their docs
aguestuser
@aguestuser
Apr 24 2016 20:58
paid particular note to the security section
"we can't protect you from the NSA" (and so apparently aren't going to try?) caught my eye
as did the reliance on user accounts -- which is totally fine, but outside the desig we'd been thinking -- also seems to indicate they're not attempting to solve the problem of anonymity, which for the use case of a big march seems sort of indispensible
takeaway was to look into an MQTT broker for some of the stuff we might be trying to do? (Kafka, to my understanding is just another form of message broker. made me want to look at how they were facilitating direct communication between the mobile clients and the message broker, and if we might not want to do that with where@ as well
Meitar M.
@meitar
Apr 24 2016 21:01
I noticed the Booklet but didn't read it (yet). I've been burning the midnight oil on other stuff and even had to drop the React Native primer because I got so overwhelmed preparing for this Tuesday event deadline I have. But when that crossed my feed I immediately thought of you. Glad you picked up on it, too!
aguestuser
@aguestuser
Apr 24 2016 21:01
other notable takeaway from persuing their security section: no attempt at HPKP/certificate pinning nor concern that TLS traffic is subject to fairly trivial to mount a MITM attack
@meitar hope the event(s) have been are going well! let's catch up soon!!!
Meitar M.
@meitar
Apr 24 2016 21:02
Yeah, I skimmed their blog and was left with the impression of talented developers who don't have the kind of political approach or motivations in mind that we do. This isn't bad, per se, but it obviously influences what they're prioritizing and how they're working on stuff….
Thanks! The gist (because I don't wanna spam the room with my own stuff) is that I feel like I'm doing a lot of work on making the project approachable for the right people that I really hope will pay off but I'm trying not to get my hopes too high. ;)