User talk:TBolliger (WMF)

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Extending global blocks to named accounts[edit]

I noticed that you didn't list the wish list survey suggestion I created for extending global blocks to named accounts instead of globally locking users, does this have a particular reason? This concerns your request for comment. --Donald Trung (Talk 🤳🏻) (My global lock 🔒) (My global unlock 🔓) 14:16, 9 December 2017 (UTC)

We're watching a lot of the Wishlist proposals that are related to Anti-Harassment work, but those three I specifically linked were closest to the top 10. — Trevor Bolliger, WMF Product Manager 🗨 17:57, 11 December 2017 (UTC)

Blocks based on hardware[edit]

As you may know, Nipponese dog calvero is a very long term vandal. Is it possible perhaps for a wmf hardware block on his devices? I mean, block any edits based on his personal computer and phone? --Artix Kreiger (Message Wall) 00:28, 17 January 2018 (UTC)

For any requests about cross-wiki vandalism, please contact Stewards. (For the record, hardware blocking is not possible with current MediaWiki software.) — Trevor Bolliger, WMF Product Manager 🗨 00:40, 17 January 2018 (UTC)


Hello! May I leave some feedback on flow? --Artix Kreiger (Message Wall) 18:19, 3 March 2018 (UTC)

@Artix Kreiger: I'm not involved with the Flow project, I would recommend you discuss on Talk:Flow. — Trevor Bolliger, WMF Product Manager 🗨 19:53, 5 March 2018 (UTC)

What happens after lock of page expires?[edit]

Hi TBolliger!

Disclaimer: Yes, I know there is probably better place to write about this, but in last 10 years I saw a lot of mediawiki tinkering which surely spent a lot of man-hours, really man-years and not so much of improvement to end users, meaning Wikipedia volunteers. This is, the first really good idea I saw in years, and now I think I have idea for another one good improvement. :)

  • Description of problem/current mediawiki behavior: after lock of page expires, page is unlocked, meaning - no protection at all.
  • Description of wanted mediawiki behavior: after lock of page to sysop level expires, page should either go to previous level of protection, if such exists, or it should be possible to set state of page lock after sysop lock when actually locking to set period of time.
    • Comments: this could be circumvented with bot and tasklist page.
    • Answer to above comment: that is not good software design. It should be set better, smarter, in the first place. (Yeah, right. :)

Maybe this idea already is written somewhere, maybe not. I have no clue. But it's written here and now. I kind of thought to write above on page: Grants:IdeaLab/Inspire, but before doing that, it would be wise (or ideal) that I find time to read, or at least skim other ideas. But there are a lot of ideas... Smiley.svg Regards! SpeedyGonsales (talk) 10:25, 7 August 2018 (UTC)

@SpeedyGonsales: Yes, we've received this request before too, but we cannot find ways to connect it to Anti-Harassment work, and it would take a few months for us to work on, so my team (the Anti-Harassment Tools team) will focus on other project when we're done with Partial Blocks. The phabricator task is phab:T41038 for future reference. — Trevor Bolliger, WMF Product Manager 🗨 21:04, 7 August 2018 (UTC)

New message re WCNA 2018[edit]

Hi Trevor! Left you a message on the WCNA wiki. Thanks, ~SuperHamster Talk Contribs 18:03, 10 September 2018 (UTC)

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:24, 30 October 2018 (UTC)