Hi! @KinneretG's manager here – looks like she was blocked from Superset over the weekend for some reason. Could you please reinstate her permissions? Thanks!

@kzimmerman Yep, Isaac has kept us in the loop – happy to reach out to Yandex if/when we decide that more upstream technical changes aren't feasible.

@Reedy Sorry for the delay – I don't check Phab as much as I used to ;) Not sure when the integrations went down because no one on our end has been monitoring them very closely (but Jon Robson's guess is that, per Legoktm, Let's Encrypt is the issue). And I asked the IFTTT team to move our applets page (https://ifttt.com/wikipedia) into hidden mode while we're figuring out what to do here, so new users wouldn't stumble on it and try to use the broken integrations.

Thank you, @nshahquinn-wmf! We're going to set up a meeting with TT to talk more and get a bit more clarity on their CTR estimates. Will keep you posted if/when we learn more!

@nshahquinn-wmf Any updates on this task? We got some initial impressions data but are waiting more more recent impressions/CTR data from TikTok and are planning to present on this product at the monthly staff meeting this Thursday, so anything you can share on impact to site visits would be really helpful!

Apple testers are reporting that it's not just logged out users who are impacted – it appears logged in users on Relay may not be able to edit, either. Is there a way for us to reproduce this?

A few other pieces of data that would be helpful:

@Aklapper Just making sure you didn't miss this request :) Let us know if we need to provide any additional info to complete this – thanks!

Just commenting to confirm this request for Kinneret to be added to the contractors' access group for Superset/Turnilo! LMK if you need anything else – thanks!

Oops – thanks, @Urbanecm! Logged in through Maryana and it worked. In other news, I have way too many WMF accounts ;)

I'm getting this error message when I try to log in to superset.wikimedia.org – is this expected?

Meeting w/a Senior Account Manager of Digital Publishing this week.

Update as of 5/11/2020: our cold call was passed onto marketing – meeting still to be scheduled.

Stub here for discussion at the next design review: https://trello.com/c/X2elvfFw/257-beta-alpha-designation

I just wanted to flag this as the last decision to change search in the above way was completely data driven and yielded great results and we should be careful in making these changes that we are just as careful.

@Jdlrobson Let's uphold our end of the bargain on good communication on Phab & please not title bugs with "X is terrible".

I think this would make a good alpha experiment :)

This is by design to avoid cluttering the reader experience and loading more elements on the page than absolutely necessary (have to think about lower-end device users and slow connections). I should also note that our data on reader patterns indicates that over half of users never scroll past the lead section of articles on the mobile site anyway, so I think for now the top-level issues flag is sufficient.

Please engage constructively on Phabricator or don't engage at all. Asking for an opt out for a feature = constructive. Calling that feature "ugly as fuck" = not constructive.

It's not, AFAIK.

Just checked on beta labs and the stars are now misaligned in a different way :) The non-watched and watched ones line up now, which is good, but they're all floating too close to the top border of the search results box and not in the center, which is not so good.

Not seeing this in alpha anymore. Can you confirm, @bmansurov?

I think all that's needed for this is for the same clear button that we use for normal search to be added to search-within-pages search.

Additional use-case to consider: sometimes the lead image is really not appropriate as a banner image (think scary medical conditions you don't want to see close up). It would be great if this service could support having new images pushed to it, so users could select a better lead image from all the ones in the article or on Commons without having to edit the page :)

This particular use-case is: a pair of testers manually creating accounts on a handful of different mobile devices all using the same IP. They're not in our office, so whitelisting the office IP wouldn't help. Apparently, they hit the limit after they created 6 accounts. From their email reporting the issue:

I hit this over the weekend but am not able to replicate it anymore, so *hopefully* it was just a glitch in the matrix.

In T85151#961235, @RobLa-WMF wrote:

I think we need to have a large group alignment conversation about our engineering strategy around mobile, and what the organization as a whole should be doing. I repeatedly hear skepticism about the fall of desktop and rise of mobile as a reason to drop what we're doing and have everything be about mobile. It's not so much skepticism about the fact that it's happening (though there is a little misplaced skepticism there), but cynicism about what that fact is being used to justify.

The temptation on this session would be to "go with what we know", which is lots of presentations and demos. These will be utterly unconvincing and unengaging to mobile strategy skeptics. I think it likely needs to be a conversation rather than a presentation in order to win over skeptics, but exactly what this looks like is a bit unclear to me.

Oh, I didn't realize that patch was just in beta -- why hasn't it gone up to stable? It's a big improvement to browsing UX! Let's graduate it.

@Deskana – do you happen to remember which device you were able to replicate this on? I know it was one of the ones in the office... A community member also reported seeing it on a Samsung Intercept with Android 2.2.2 and the standard web browser.

All browsers tested on by The Specialist Guild (stock Android browser & Chrome on Android 4 devices, and Safari on iOS 6, 7, & 8 iPhones). They didn't see anything wrong with site search.

In T667#16960, @Tnegrin wrote:

My comments on the goals themselves:

1. I don't like stretch goals. Let's keep them short and attainable and under-commit per Lila.