[17:29:16] bearND: hey [17:29:59] matanya: o/ [17:30:26] bearND: wanted to brainstorm a sec about a feature request, please [17:30:42] k [17:33:47] can you please reload the page from the server after every save of an edit and not use the stored version? [17:34:08] it is a bit confusing when the edit is not shown unless hard refreshing the page [17:34:46] also, bearND i wanted to thank you very much for making the app mulit-ligngual, i love this feature [17:36:27] matanya: Are you talking about the Android app? Those thanks should go to cgauthier, cooltey, sharvani_ and (dbrant if was here). I'm not working on the Android app anymore. [17:36:55] bearND: fair, thanks for thanking the right people :) [17:37:14] bearND: what is your current thing then? [17:39:26] matanya: the reload of the page is a bit tricky, first it takes a while until the page gets updated after an edit in RESTBase (both the Parsoid HTML and the MCS mobile-sections output). Secondly the Android app uses a caching layer. I think I remember seeing a task about this, though. Will look for it in a bit. [17:39:48] thanks [17:40:16] matanya: I'm working on the Mobile - and Page Content Services (MCS + PCS). [17:40:35] ah, the lower levels [17:46:20] matanya: https://phabricator.wikimedia.org/T173098 is probably what you are describing. It has links to other similar tasks in the comments as well. IIRC the app waits a few seconds before loading the page again after an edit. [17:46:52] thanks much bearND [20:58:47] bearND|afk: anything stopping me at hackathon from working on reading lists on mobile? [20:58:49] (and desktop) [22:48:36] jdlrobson: nothing at all. I think this would be great since the whole RI team will be there if you have backend questions. FYI, mdholloway is working on a very simple browser extension to add the current page to the default reading list (see https://github.com/wikimedia/webextension-readinglists + https://github.com/wikimedia/readinglists-extension-safari). [22:49:40] There's nothing for displaying reading lists for the web yet since it'll probably need some design, too. Once you have something officially for the web then we probably deprecate the browser extensions. [22:50:35] actually, the hackathon might be a good opportunity to split out the api interaction code into a library that the browser extensions and the mobile web could share [22:51:04] (and anyone else of course)