[13:44:00] <mdholloway>	 hi Ramolaweb, if you'd like to contribute to the Wikipedia Android app, please have a look at https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/App_hacking to get set up
[13:46:33] <mdholloway>	 Ramolaweb: a good way to find suitable tasks to pick up is to search Phabricator for tasks tagged with "Wikipedia-App-Android-Backlog" and "Easy": https://phabricator.wikimedia.org/maniphest/query/vFZJrhzhzKSh/#R
[16:23:39] <coreyfloyd>	 nataliaharateh: will be a few late to retro, in another meeting
[17:33:35] <dbrant>	 mdholloway: niedzielski: hockeyapp for beta looks ok. any objections to production?
[17:34:04] <niedzielski>	 dbrant mdholloway: just double checking...
[17:35:41] <niedzielski>	 dbrant mdholloway: looks good to me. for some reason, i'm not seeing any wikipedia prod alpha usage though.
[17:36:04] <niedzielski>	 dbrant mdholloway: er, nevermind. i think it's just mislabled: https://rink.hockeyapp.net/manage/apps/226649/app_versions/92/crash_reasons
[17:40:00] <mdholloway>	 dbrant: no objections from me
[19:28:31] <niedzielski>	 mdholloway dbrant: I'm working on the ol' chore wheel. What's the deal with this OTRS Android queue document? Are you guys logging all responses made in this? Or what's the intent of recording responses here and in OTRS? (I don't mean to criticize but I do want to avoid unnecessary work.)
[19:29:50] <mdholloway>	 niedzielski: i did when i took my turn last week.  i don't know that that necessarily needs to be our practice forever.  it might be handy as a reference.  that said, probably not necessary to log gibberish or IP block complaints
[19:30:07] <mdholloway>	 i was just mimicing rita basically
[19:34:10] <mdholloway>	 next time i'll probably streamline things here and there
[19:35:20] <niedzielski>	 mdholloway: hm, it seems to me that we should strive for everything to live either in phabricator (bug / feature) or otrs (support). maybe the point of this doc is for things that aren't ready for a ticket like confusion around a feature
[19:40:13] <mdholloway>	 niedzielski: that seems reasonable.  i can't really say what purpose rita had in mind originally
[19:41:05] <niedzielski>	 mdholloway: so for example, a user found dark mode hard to find so i'm crossreferencing the ticket in phabricator: https://phabricator.wikimedia.org/T160411
[19:41:43] <mdholloway>	 right, i see what you're saying.
[19:43:46] <mdholloway>	 niedzielski: i wouldn't fault you for doing things however you see fit.  reserving the spreadsheet for unresolved items makes sense
[21:38:46] <lbertolotti>	 https://phabricator.wikimedia.org/T153980
[21:41:02] <niedzielski>	 mdholloway: did you timebox your ticket dive or try to clear the queue? (i'm seeing some older tickets so i assume timebox but wanted to confirm :] )
[21:42:20] <mdholloway>	 niedzielski: yeah, there were some from before that i didn't touch
[21:43:12] <niedzielski>	 mdholloway: cool. thanks!
[22:27:51] <coreyfloyd>	 jdlrobson:  hey when you show “notifications” or the “hello” message for the current user on the mobile page. Where are you getting those? How is that cached?
[23:08:39] <jdlrobson>	 coreyfloyd: huh?
[23:09:00] <jdlrobson>	 can you explain a little more what you mean?
[23:09:10] <coreyfloyd>	 In the mobile web, when I log in and log at the main page it says. “Hello fjalapeño"
[23:09:16] <coreyfloyd>	 My name
[23:09:32] <coreyfloyd>	 But thats a user level customization
[23:09:47] <coreyfloyd>	 So is everything just uncached at that point?
[23:10:08] <coreyfloyd>	 Same thing with the indictor for echo that shows how many notifications I have.
[23:10:12] <coreyfloyd>	 jdlrobson: ^
[23:10:33] <jdlrobson>	 our infrastructure doesnt cache for logged in users
[23:10:38] <jdlrobson>	 it's a big flaw
[23:10:47] <jdlrobson>	 that said..
[23:10:51] <jdlrobson>	 talking about html here
[23:10:55] <jdlrobson>	 the parser output is cached
[23:11:09] <jdlrobson>	 but every page view the HTML has to be constructed by the server
[23:11:50] <coreyfloyd>	 jdlrobson: ok - so some of the page is cached then?
[23:12:14] <coreyfloyd>	 jdlrobson: for context: wondering if we should try to address this with the new APIs and such
[23:12:15] <jdlrobson>	 yes there's just no top level HTML cache
[23:12:34] <coreyfloyd>	 Got it… does it still get cached in varnish at all for a short time?
[23:12:55] <coreyfloyd>	 Or is that completely circumvented?
[23:57:30] <jdlrobson>	 nope
[23:57:37] <jdlrobson>	 varnish is what does HTML caching