La da di di da!

Global preferences ready for testing edit


I am contacting you because of your support for Global settings in the 2016 Community Tech Wishlist. Global preferences are now available for beta testing, and need your help before being released to the wikis.

  1. Read over the help page, it is brief and has screenshots
  2. Login or register an account on Beta English Wikipedia
  3. Visit Global Preferences and try enabling and disabling some settings
  4. Visit some other language and project test wikis such as English Wikivoyage, German Wiktionary, the Spanish Wikipedia, the Hebrew Wikipedia and test the settings
  5. Report your findings, experience, bugs, and other observations

Once the team has feedback on design issues, bugs, and other things that might need worked out, the problems will be addressed and global preferences will be sent to the wikis.

Please let me know if you have any questions. Thanks! Keegan (WMF) (talk) 19:37, 26 February 2018 (UTC)Reply

The Community Wishlist Survey edit


You get this message because you’ve previously participated in the Community Wishlist Survey. I just wanted to let you know that this year’s survey is now open for proposals. You can suggest technical changes until 11 November: Community Wishlist Survey 2019.

You can vote from November 16 to November 30. To keep the number of messages at a reasonable level, I won’t send out a separate reminder to you about that. /Johan (WMF) 11:23, 30 October 2018 (UTC)Reply

Thank you for your help with the Wishlist Survey edit

Hey Izno! Thanks for all your helpful comments on the wishlist proposals. Way too many for me to thank individually so I'll just thank you here. I appreciate your involvement! :) -- NKohli (WMF) (talk) 23:18, 6 November 2018 (UTC)Reply

@NKohli (WMF): Knowing that I have missed any opportunity to see my inbox light up further because of my contributions to the CommTech survey saddens me greatly. Curses! --Izno (talk) 23:27, 6 November 2018 (UTC)Reply
I came here to say the same thing. Metawiki unfortunately doesn't seem to have barnstars...? You deserve one :) MusikAnimal (WMF) (talk) 17:12, 9 November 2018 (UTC)Reply

Community Wishlist edit

Hello, you expressed an endorsement on this wish: Community Wishlist Survey 2019/Editing/Autocomplete summaries in VisualEditor. Do you want to give a support vote too? --Dvorapa (talk) 18:51, 18 November 2018 (UTC)Reply

Watchlist Expiry project page edit


During the Community Whishlist survey 2019, you have voted for the Watchlist item Expiration wish.

Community Tech has created the Watchlist Expiry project page to work on this feature, and is looking for your feedback about the open questions they have.

Regards, IFried_(WMF), 15:51, 25 September 2019 (UTC)Reply

Community Wishlist Survey 2019 - Section Name in Diff edit


The Community Tech team (WMF) has officially started the project for Section Name in Diff, the #9 wish from the 2019 Community Wishlist Survey!

You previously voted for this wish, so we are now contacting you. We invite you to visit the project page, where you can read a project analysis and share your feedback.

We hope to see you on the project talk page, and thank you in advance!

-- IFried (WMF), 14:14, 9 March 2020 (UTC)Reply

SGrabarczuk (WMF)

18:25, 20 November 2020 (UTC)

SGrabarczuk (WMF)

16:08, 11 December 2020 (UTC)

It takes arbitrary images edit


Per our discord conversation Wugapodes (talk) 01:16, 18 August 2021 (UTC)Reply

A barnstar for you! edit

  The Community Wishlist Survey Barnstar
For your awesome assistance in technical reviews of the Wishlist proposals NRodriguez (WMF) (talk) 19:31, 15 February 2022 (UTC)Reply

IP Range block edit

Hi there! Recently I noticed you blocked the range I kept a tab up showing their contributions. It revealed the range was used by MegaMack02, who is also subsequently a hacker. Looking at said user’s SPI archived cases they somehow hacked their way into an unrelated IP From a CU I also consulted, said sockmaster also hacked into an unrelated IP that began with 107 to create the ThomasDuhTankEngine2843 account (now global locked as LTA), and it was an IP accused for vandalizing various pages, including one on a TV series “Chowder” in the past, before the sockmaster’s coming. And here are some tidbits of info the sockmaster said:

MegaMack uses IPs operated by the American VPN provider Norton ([1]). All IPs are currently blocked for 6 months, and previously for 3 months and 1 week (for, but I would like to request a permanent block since the listed IPs are not only Open Proxies/VPNs, but there have been multiple hackings into these IPs by this particular sockmaster. Sockmaster has also said that they will repeat their hacking/sockpuppeting on a monthly basis. Thanks. VandalMan247 (talk, contribs) 02:04, 19 January 2023 (UTC)Reply

List of Wikipedias/it edit

Hello, it's not about my preferences; the visualization of the tables was very wrong, and everything was very wide, exceeding the width of the page. Anyway it seems that the problem was somewhere else and "imported" in the page with your edit, and now it seems to be fixed, so I will restore your edit and check if it's all right. Phyrexian ɸ 07:29, 8 March 2023 (UTC)Reply

Style sheets for system messages edit

Dear Izno,

Do you know whether there is a way to import a sanitized-css page into a a system message? Actually, templateStyles do work, but they are limited to .mw-parser-output scope.

I did not find such a feature request at Phabricator, do you know whether it has already been requested or discussed? Do you think it would be an interesting feature?

My goal is removing rule sets from Common.css which are specific to some system message which are not globally loaded.

-- Pols12 (talk) 19:13, 7 April 2024 (UTC)Reply

@Pols12, what specific rules and where are they being applied? IznoPublic (talk) 19:41, 7 April 2024 (UTC)Reply
That was a generic question; but for example, at at frwiki (line 1846), we target MediaWiki:Wikimedia-copyrightwarning which only displays while editing a page. -- Pols12 (talk) 19:57, 7 April 2024 (UTC)Reply
@Pols12, yeah, I understand it being a generic question, but there are multiple different answers depending on the situation. In some cases, you can add <div class="mw-parser-output">content</div> (e.g.). In others, you can do nothing because of the particular selectors being used, because they target elements that can't be targeted with TemplateStyles. In a few others you could potentially do something but TemplateStyles does not yet support the relevant CSS (... or has a bug).
The specific rule you've pointed to here is of the third kind I think today (particularly, container queries), otherwise the second kind (because of .ve-ui-mwSaveDialog .oo-ui-window-frame). We have something like it in our CSS at MediaWiki:Common.css#L-211 that I think would go away if we could target mw-parser-output as a container, since at least two of those selectors + the associated rules pertain to the size of the popup box.
You can target <body> and <html> in TemplateStyles, but neither of those help in this case. Izno (talk) 20:16, 7 April 2024 (UTC)Reply
Thank you for this detailed answer! 🙂 I did not think about simply adding a .mw-parser-output wrapper div, that may indeed solve some cases. -- Pols12 (talk) 22:43, 7 April 2024 (UTC)Reply