@Aklapper : Yes, this was completed and the results can be seen at this link - Mexico survey results

All Wikipedia Zero partners have been shut down - no banners are currently being served.

@ovasileva - Opera has responded, and their engineers are working on a fix. Not sure about an ETA.

@ovasileva - I've informed Opera of the issue and I'll update on this when I hear back from them.

Thanks everyone, great to see this working again!

@BBlack - not sure why OperaMini proxy IPs are no longer being exported. Can this information be re-established?

Nothing is left on this. Please close out any remaining tasks.

Please keep access for me as I use this for reviewing Zero traffic along with other country-level research for Global Reach / New Readers

Sorry about the delay - this problem has been resolved. Thanks!

I agree, and mentioned this as one of the options we would explore on my initial post to the commons village pump. We're initially focusing on a couple of the other suggestions made there right now, but this is the next to investigate.

My only reference was the conversion of all the zero partners (around 75) from URL-based whitelisting to IP whitelisting when we adopted HTTPS-only, and that took about 5-6 months. Probably the biggest challenge was getting ahold of some partners where the PoC had moved on, or much or all of the current team didn't know about the project.

Any updates on the new IP ranges we will have?

I checked and there is a problem with the testing timer. I'm attaching a screenshot. If you need credentials to access, please contact me outside of Phabricator.

Sounds good

Go ahead and try it - let me know when it's live so I can do another test

Yes, if these file types are possible.

@BBlack Is there an update for ETA for updating the zero whitelisting IPs? I will need several months of lead time before this goes live to get ~50 partners worldwide to update their systems to match.

It can be closed.

Thanks - it has improved.

@Nuria No problem, those are the best qualifiers for who should be able to see this.

For future reference, this page contains all active zero partners.

I've conducted all steps above with no issue. I've also logged out of my zero wiki account and signed back in, and was able to access and edit config pages.

I agree this needs to be done. I will discuss with the team and get confirmatinon/dates.

Can we identify which partner (X-CS) is responsible for the increase at that time? I can look into more details once I have that information.

I would like the feature-WP0 to be autotagged for Zero. Thanks!

@Jdlrobson @jhobs One piece of information here that affects the testing -I had to turn off Zero service to Djezzy on Aug 23rd. I'm not certain of the exact timing this error was observed, so it might have been active at that time.

In T131934#2221686, @jayvdb wrote:

In part, I question this assertion. There is a large cohort of people in developing countries who can only afford to have one provider. If they are using a carrier that registers their activity as a zero rated IP when they request OAuth on Commons, and are prevented on that basis, most of them are unable to participate in the abusive uploading process. This wont affect abusive uploads who can afford to have multiple active SIMs, often with multiple smartphones, but that cohort also has less direct benefit from participating in the abusive uploading.

I can provide data for the general case if requested, but it is only general data, not Wikimedia specific, and not specific to this problem. If WMF has data that shows many of the abusive uploaders are switching carriers, then your assertion is spot on.

Fair question about carrier switching. In my experience traveling to less developed countries in Asia and Africa, the least well off are more likely to use multiple carriers than people who are better off. That's because the mobile operators there are primarily based on a pay-as-you-go model, with no monthly bills, contracts, etc. The people who are watching their money the closest switch sim cards practically per task, since one carrier may offer lower cost for calling out vs sending SMS messages, and other promotional pricing. The users are amazingly adept at the process of switching sim cards around, and some phone models offer a multi-sim capacity so you can switch between carriers without opening the case. So to the point of the discussion, there is a very low barrier for most people to quickly switch between networks.

At this point, we have established that we have the technical capability to identify Zero traffic on tool labs tools / video2commons. However, we’ve also learned that this access is not zero-rated, even on Zero partner networks. In addition, this tool does not use client bandwidth for the video transfer, making even paid mobile access cost effective for the abuse we’re experiencing. Because of this, I believe that identifying Zero network users is not going to help us much here (if at all).

@BBlack @jayvdb My expectation (and current understanding) is that the IP ranges we provide to for zero whitelisting are only for the production servers, and not for any sort of labs or beta system. This was initially decided to avoid the possibility of someone setting up a proxy that would allow users to go through the mobile operators whitelisting and then have the zero-rated traffic redirected outside WMF via that proxy.

There is a data gap, but I have the most recent data now. Thanks!

Good to hear. When should the change be visible? Currently the portal does not show data beyond January.

Also, this is a first step to address the problem. If this first step turns out to be insufficient, future improvement requests would likely include reducing the partners flagged from all to a smaller set, and/or flagging zero rated traffic from the FB/Freebasics proxy. This is just FYI in case these plans can assist with the coding approach for this task.

@jhobs @Jdlrobson @dr0ptp4kt
I've tested and confirmed the fix. Thanks everyone for the quick response!

@Mholloway, this page may also help:

@kevinator - we are unsure this is working properly - can you verify that we have correct countries identified when coming through a proxy?

Thanks Yuri, Jeff!

I did some live testing last night, and the exit interstitial placement and missing banner bugs are resolved. @jhobs will add an interstitial header text override ability but it doesn't seem to fall in the scope of this Phabricator task.

Thanks for your help, Rob!

Hi Sheree, we need to repeat the approval process for the analytics
access. Can you review and respond to Rob's request below?

@RobH - my manager is not on Phabricator. I had my manager (Sheree Chang) send approval via email to coren earlier this week, but I will copy it below. Let me or Sheree know if you need further verification than this.

Steps to reproduce banner issue on ios9 (chrome and safari). May exist on Android - untested.

@coren : My public key is at https://office.wikimedia.org/wiki/User:Dfoy . I've signed the 'L3' document, and the DFoy wikitech user is mine.

Some text/formatting cleanup:

1. Change "Use of correct logo" to "Don't change the logo"
2. Change "Use of recommended measures" to "Use of minimum measures"
3. Change "Use of recommended background" to "Use of recommended spacing"
4. Change "Don't abbreviate Wikipedia" to "Wikipedia wordmark"
5. Change "View Full Brand Guide" to "View Full Visual Identity guidelines"
6. Make #5 larger font size, should be larger than the following "Tips for creating a campaign". You can slightly reduce the "Tips for creating a campaign" if that helps.
7. Add additional "View Full Visual Identity guidelines" after the tips section. This should be visible even if the tips are collapsed.

Ok, I will try it at home this evening. Thanks for checking it.

Hi - we are fully migrated to Phabricator, no need for any Trello migration.