[05:59:22] <wikibugs_>	 10Traffic, 10DNS, 06Operations, 10Parsoid, 13Patch-For-Review: Separate subdomain for parsoid visual diff test service on ruthenium - https://phabricator.wikimedia.org/T159995#3109059 (10Dzahn) this should be done now and work:) right, @ssastry ?  copied over from gerrit:343099:   ``` from tin:  [tin:~]...
[06:04:58] <wikibugs_>	 10Traffic, 10DNS, 06Operations, 10Parsoid, 13Patch-For-Review: Separate subdomain for parsoid visual diff test service on ruthenium - https://phabricator.wikimedia.org/T159995#3109061 (10Dzahn) 05Open>03Resolved
[06:05:50] <wikibugs_>	 10Traffic, 10DNS, 06Operations, 10Parsoid: Separate subdomain for parsoid visual diff test service on ruthenium - https://phabricator.wikimedia.org/T159995#3085873 (10Dzahn) a:05ssastry>03Dzahn
[06:06:00] <wikibugs_>	 10Traffic, 10DNS, 06Operations, 10Parsoid: Separate subdomain for parsoid visual diff test service on ruthenium - https://phabricator.wikimedia.org/T159995#3085873 (10Dzahn) please reopen if anything is missing
[10:48:00] <wikibugs_>	 10Traffic, 10Fundraising-Backlog, 10MediaWiki-extensions-CentralNotice, 06Operations, and 2 others: Purge Varnish cache when a banner is saved - https://phabricator.wikimedia.org/T154954#3109339 (10ema) >>! In T154954#3108634, @Ejegg wrote: > Wouldn't Vary: Cookie explode caching all over the place due to...
[14:32:47] <wikibugs_>	 10Traffic, 10DNS, 06Operations, 10Parsoid: Separate subdomain for parsoid visual diff test service on ruthenium - https://phabricator.wikimedia.org/T159995#3109810 (10ssastry) Thanks. Yes, it works now.
[16:08:44] <wikibugs_>	 10Traffic, 06Operations: Select or Acquire Address Space for Asia Cache DC - https://phabricator.wikimedia.org/T156256#2968867 (10faidon) After passing through Finance and Legal approval via Cobblestone, I submitted the APNIC form today. This is now being tracked by APNIC as #3102214 and in progress.
[16:08:48] <wikibugs_>	 10Traffic, 06Operations: Select or Acquire Address Space for Asia Cache DC - https://phabricator.wikimedia.org/T156256#3110087 (10faidon) a:03faidon
[16:10:03] <paravoid>	 bblack: ^^^ fyi
[16:31:14] <bblack>	 \o/
[16:31:28] <bblack>	 now to find out what kind of requirements they'll impose in practice! :)
[16:36:25] <wikibugs_>	 10Traffic, 06Operations: Select or Acquire Address Space for Asia Cache DC - https://phabricator.wikimedia.org/T156256#3110176 (10BBlack)
[16:39:40] <wikibugs_>	 10Traffic, 06Operations: Select or Acquire Address Space for Asia Cache DC - https://phabricator.wikimedia.org/T156256#3110186 (10BBlack)
[17:04:56] <wikibugs_>	 10Domains, 10Traffic, 06Operations, 13Patch-For-Review: Using wikimedia.ee mail address as Google account - https://phabricator.wikimedia.org/T158638#3110288 (10Dzahn) @Kaarel_Vaidla @Beetlebeard  I can make the change but i wanted to check with you one last time that it is ok instead of just changing it a...
[17:08:20] <mutante>	 paravoid: ^ no reason not to let wikimedia.ee use Google as MX if they request it, right   https://gerrit.wikimedia.org/r/#/c/341359/6/templates/wikimedia.ee
[17:08:58] <paravoid>	 I personally disagree at being a DNS hoster for chapters
[17:09:20] <paravoid>	 and believe that we should either own a domain and its web and email endpoints or not own it at all
[17:09:33] <paravoid>	 but I realize that's a bit of a hard stance
[17:09:51] <paravoid>	 I would check this specific case with legal though
[17:10:43] <mutante>	 paravoid: ok, gotcha, yea. will check with legal
[17:19:18] <bblack>	 that seems like a reasonable stance to me
[17:20:13] <bblack>	 *if* anyone were wondering about the legitimacy/security of some random wiki-sounding domainname, that whois and root servers point at us legitimizes it, at which point it should be something we're in control of.
[17:20:45] <bblack>	 (but of course, in practice 99.999% of all traffic is coming from people that don't even know what a domainname is, much less whois or DNS, so it's kinda moot for most!)
[17:21:57] <bblack>	 but still, there's some follow-on effects I'm sure, e.g. google might check whois/DNS in deciding who's responsible for the site when it comes up as an unsafe/malware site they want to blacklist or not (or it may even influence related decisions for them)
[17:22:21] <bblack>	 ditto spam-related things
[17:25:46] <bblack>	 paravoid: out of curiosity, what was the address space we asked for? /24 + /48 or something like that?
[17:26:55] <bblack>	 (I think their min cost went as big as something like /34, but that seems excessive)
[17:42:59] <paravoid>	 yes, /24 + /48
[17:43:20] <wikibugs_>	 10Domains, 10Traffic, 06Operations, 06WMF-Legal, 13Patch-For-Review: Using wikimedia.ee mail address as Google account - https://phabricator.wikimedia.org/T158638#3110446 (10Dzahn)
[17:49:23] <mutante>	 about the MX change. yes, all that makes sense to me too. just to add: the "before" status is also that there is an external MX in our records. they "just" want to change from "other 3rd party" to Google
[20:21:57] <wikibugs_>	 10Traffic, 10Analytics, 06Operations: A/B Testing solid framework - https://phabricator.wikimedia.org/T135762#3110845 (10Nuria) Design document available in meta:  https://meta.wikimedia.org/wiki/Research:PrivacyConsciousABTestingAtWikimediaFoundation
[20:22:39] <wikibugs_>	 10Traffic, 06Analytics-Kanban, 06Operations, 06Performance-Team, 06Reading-Admin: Preliminary Design document for A/B testing - https://phabricator.wikimedia.org/T143694#3110846 (10Nuria) Design document available in beta: https://meta.wikimedia.org/wiki/Research:PrivacyConsciousABTestingAtWikimediaFound...