2013-01-14

05:18 se7h joined #geoloqi
07:03 [007g3m1n1] joined #geoloqi
07:53 se7h joined #geoloqi
08:44 hsoj joined #geoloqi
08:58 hsoj joined #geoloqi
09:22 [007g3m1n1] joined #geoloqi
09:23 patrickarlt joined #geoloqi
09:25 hsoj joined #geoloqi
09:53 kyledrake joined #geoloqi
10:26 caseorganic joined #geoloqi
10:38 caseorga_ joined #geoloqi
10:50 patricka_ joined #geoloqi
11:06 kyledrake joined #geoloqi
11:22 patrickarlt joined #geoloqi
11:57 kyledrak_ joined #geoloqi
12:03 hs0j joined #geoloqi
12:18 Azra-el joined #geoloqi
12:44 <Loqi> https://twitter.com/singly :: We're partnering with @puppetlabs, @geoloqi and @networkredux for APIs &amp
12:44 <Loqi> IPAs in Portland. Get tix before we run out! http://pdxapipa.eventbrite.com/
12:57 <Azra-el> hey guys... any way to delete all users at once? :)
12:57 <aaronpk> nope, but would be a pretty simple script to write
12:58 <Azra-el> yeah just checking if there is one before actualy writing it
12:58 <Azra-el> also thanks for the email aaron :) create_anon works great on node.js ... and we'll check it soon on titanium
12:59 <aaronpk> great! I sent back an email with a new titanium module
13:00 <Azra-el> one question... it seems that if from mobile ..device_id is needed.. should i forward that from the phone to nodejs and include it in the create_anon or not? and ... just by initializing geoloqi with an existing token? in your gist you run geoloqi.init and only in onsuccess you set the token.. does that by any chance create an extra user ?
13:01 <aaronpk> it doesn't create an extra user because of the extra config setting, `allowAnonymousUsers: 0` which disables the automatic user creattion
13:02 <Azra-el> ok great
13:02 <Azra-el> and that should be all right?
13:02 <aaronpk> I don't think we need the device_id, that really only comes into play when dealing with push notifications, but if you're using Urban Airship for that, it won't be needed
13:03 <Azra-el> ok great. yeah... we're handling our own urban_airship token aquisition somewhere else
13:03 <Azra-el> thanks
13:03 <Azra-el> hope we dont get into any more brick walls
13:04 <aaronpk> great!
13:14 <Azra-el> aaron .. if you're still here.. im curious ... what's your method of testing stuff? assuming i have a build on my phone with the propper initialization... and the user is subscribbed to a know layer.. how can i test hitting certain points?
13:16 <patrickarlt> you go out and run a trail then download the json (via the api) and you can replay the points
13:17 <Azra-el> lol ... that involves running :D
13:18 <Azra-el> location/update has any effect?
13:24 <patrickarlt> it basically fakes out the api on the location of you phone
13:24 <patrickarlt> if you hit any triggers then those triggers will run
13:25 <Azra-el> great.. so i can manually hit that with a good place i know there's a trigger and it will trigger it
13:25 <aaronpk> yes, it's best to first send a location update for a ways away from the trigger, wait a few seconds, then send one inside the trigger
13:27 <Azra-el> ok.. and that works for both dwell type trigger and imediate?
13:27 <Loqi> https://twitter.com/kinlane :: RT @singly: We're partnering with @puppetlabs, @geoloqi and @networkredux for APIs &amp
13:27 <Loqi> IPAs in Portland. Get tix before we run out! ht ...
13:55 patricka_ joined #geoloqi
14:00 se7h1 joined #geoloqi
14:12 kyledrake joined #geoloqi
15:08 aaronpk_ joined #geoloqi
15:08 caseorganic joined #geoloqi
15:09 caseorga_ joined #geoloqi
15:09 kyledrake joined #geoloqi
16:10 kyledrake joined #geoloqi
16:24 kyledrak_ joined #geoloqi
17:21 <Loqi> https://twitter.com/twobillionideas :: Weds, 1/16: Geoloqi/Erai hosts Portland Lunch 2.0 http://calagator.org/events/1250463118
17:41 kyledrake joined #geoloqi
17:53 patrickarlt joined #geoloqi
17:56 patrickarlt joined #geoloqi
18:40 [007g3m1n1] joined #geoloqi
20:37 patrickarlt joined #geoloqi
21:10 se7h joined #geoloqi
21:18 patrickarlt joined #geoloqi
21:38 aaronpk joined #geoloqi
22:40 kyledrake joined #geoloqi
23:07 se7h joined #geoloqi
23:24 [007g3m1n1] joined #geoloqi