[12:36:39] <ebernhardson>	 \o
[13:19:23] <inflatador>	 <o/
[15:05:54] <ebernhardson>	 i'm going to guess, no retro today due to ascension day
[15:27:34] <Trey314159>	 I'm not feeling great, so I'm taking the day off.
[15:27:44] <ebernhardson>	 take care, hope tomorrow is better
[16:53:54] <ebernhardson>	 not finding great reasons for the mismatch buckets :S Like i can see a session that reported T407432_dym_g_ld:control for many searches, but then the second-to-last request got T407432_dym_g_ld:d1v.  So somehow they were provided a different bucket...but no clue why
[17:02:03] <ebernhardson>	 best random guess is x-forwarded-for or ip address changed. Maybe mobile switching, but that doesn't add up to 40% :(
[17:02:13] <ebernhardson>	 or if it does, i would be surprised at least
[17:08:36] <ebernhardson>	 maybe privacy tech just doesn't allow this system to work anymore, but seems like a big jump to make without stronger proof
[18:35:27] * ebernhardson wonders why we log some http headers, but not the x-forwarded-for we need here...at least can fix that