[11:24:28] [telegram] Hi everyone, Can anyone please help me with this: [11:24:28] [telegram] 1. How to resize OO.ui.PopupButtonWidget? [11:24:29] [telegram] 2. How to import google fonts in userscripts ooui? [11:24:31] [telegram] Or can guide me to the right place? [11:25:58] [telegram] I can only help with 1: Give it a class, set the size via CSS on that class. (re @Ankit18gupta: Hi everyone, Can anyone please help me with this: [11:25:59] [telegram] 1. How to resize OO.ui.PopupButtonWidget? [11:26:01] [telegram] 2. How to import google fonts i...) [11:26:30] [telegram] or `myPopup.$element.css( "css", "here" );` if you want to do inline CSS [12:35:37] [telegram] Doesn't help. It just shifts the popup but does not resize it. (re @jhsoby: or myPopup.$element.css( "css", "here" ); if you want to do inline CSS) [12:41:31] [telegram] what css are you applying to it? (re @Ankit18gupta: Doesn't help. It just shifts the popup but does not resize it.) [12:47:47] [telegram] width and height with margin: auto (re @jhsoby: what css are you applying to it?) [12:50:36] [telegram] then try adding `display: block;` to the mix (re @Ankit18gupta: width and height with margin: auto) [12:51:43] [telegram] Still the same result (re @jhsoby: then try adding display: block; to the mix) [13:49:06] [telegram] mc【午夜成人直播】火爆在线直播APPni👞来看正妹脱光光，午夜色播👢fv👀91视频麻豆传媒 SWAG 指定合作伙伴免VIP观看入口🕶️zt🧦成人色播国产韩国网红主播大秀全网最火色播APP💍zx👜外围主播可约可降。全网最火叫鸡APP🎓fc💍正在免费直播极品粉嫩鲍鱼🦻hy💍APP观看地址： yaobo.mewt🥼直播点击地址： [19:10:09] [telegram] does anyone know if the https://w.wiki/4wJS’s advice to “Send `the header Accept-Encoding: g`zip,deflate”, for better caching, still applies? [19:10:50] [telegram] I’m making some test requests from axios (node.js), and as far as I can tell, I’m not sending Accept-Encoding, the response doesn’t have a Content-Encoding, and I stil`l get x-cache-status: hit`-front [19:11:23] [telegram] so I suspect this is as outdated as the term “squid caches” implies ;) but if anyone knows better, I’m curious :) [19:12:55] [telegram] ew, looks like bridgebot messed up my message on the IRC side :/ https://wm-bot.wmcloud.org/browser/index.php?start=03%2F10%2F2022&end=03%2F10%2F2022&display=%23wikimedia-hackathon [19:13:27] [telegram] maybe better to avoid rich text for the bridge? or maybe it does something smart with the link? or not... (re @lucaswerkmeister: does anyone know if the robot policy’s advice to “Send the header Accept-Encoding: gzip,deflate”, for better caching, still appl...) [19:14:11] [telegram] I thought it turned links into something like link text (but that’s why I used w.wiki to make the URL shorter) [19:14:53] [telegram] yes but it was broken by the 's after link [19:15:23] [telegram] by why not just write text yourself [19:16:10] [telegram] for the record the link is https://w.wiki/4wJS [19:16:59] [telegram] let’s put that discussion aside, I’m more interested in actual answers to my question :) (re @jeremy_b: by why not just write text yourself) [19:17:19] [telegram] also IRC side seems to lose the link text too "robot policy" [19:19:33] [telegram] 12.5 years since there was a change to content of that page [20:49:34] [telegram] I’ve updated the Accept-Encoding part and otherwise marked the page as outdated [20:57:11] @lucaswerkmeister are you sure that axios doesn't automatically add an Accept-Encoding header and deal with decompressing transparently? I would honestly be pretty surprised if it didn't. [20:59:41] [telegram] fairly sure, I console.logged the response and saw what looked a lot like the on-the-wire headers [20:59:46] https://github.com/axios/axios/commit/42eb9dfabc85ed029462da1c503f8b414b08ffd0 [21:00:05] [telegram] though axios *can* automatically decompress (yup, exactly that ^^) and I am adding a corresponding commit now [21:00:23] [telegram] and with that added, I can see the difference in the logged headers too [21:03:23] [telegram] bd808: https://github.com/lucaswerkmeister/m3api/commit/d210e481ef90b28284f88db6eea5f60048eadaa8 [21:04:52] +1. The fine folks in the #wikimedia-traffic IRC channel would probably be the place to start looking for someone who feels confident in updating https://wikitech.wikimedia.org/wiki/Robot_policy [21:05:27] [telegram] /me wonders if the python mwapi includes compression [21:05:39] That page does look to be mostly very old advice from Tim [21:06:10] [telegram] with userpage by hashar :) (re @wmtelegram_bot: [irc] That page does look to be mostly very old advice from Tim) [21:07:19] I have a hunch it was a duplicate account from some content import too. Tim's "real" account is https://wikitech.wikimedia.org/wiki/User:Tim_Starling [21:09:53] [telegram] looks like Python’`s reques`ts automatically include`s Accept-Encoding: gzip, defla`te, yay (re @lucaswerkmeister: /me wonders if the python mwapi includes compression) [23:07:56] [telegram] Forwarded from unknown: I never expected this, All thanks to this platform for turning my $300 to $4000. Initially I thought it was fake but now I know you are real and legit. I recommend everyone to invest with him through the link [23:07:57] [telegram] ✍️ ✍️ @James_fx_helen [23:07:58] [telegram] https://t.me/joinchat/Qs452CESlBA5ZTY0 [23:34:29] I kind of love that every time I notice spam here on the irc channel I find that someone already cleaned it up on the Telegram side. Thank you co-moderators! :)