| Xaosflux | |
| Nov 13 2023, 2:46 PM |
| F100208731: image.png | |
| Aug 26 2026, 11:43 AM |
Just what it says on the tin
in Special:Preferences#mw-prefsection-echo add a checkbox option to mute all non-standard users, T207659 would allow this with a "0.0.0.0/0, ::0/0" entry, but that is a technical format and would not match upcoming temporary user accounts.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Feature | None | T207659 Allow 'Muted users' notification preference to support IP ranges | ||
| Open | Feature | None | T351091 Allow muting all non-permanent users (mute Temporary Accounts) |
The last incident was a few days ago on the English Wikipedia when an IP (presumably an LTA) would repeatedly ping a bunch of admins including myself and then delete their own message.
There's been another incident of a person pinging the same editor from many pages, and many Temporary Accounts.
Most editors don't have (or want) access to the IP addresses for TAs, so T207659: Allow 'Muted users' notification preference to support IP ranges won't work for them.
A tickbox in Special:Preferences#mw-prefsection-echo-blocknotificationslist that turns off all pings or other notifications from TAs (perhaps resetting after 90 days?) would probably work.
perhaps resetting after 90 days?
A dropdown similar to the one for the watchlist would be nice (mute permanently, for 1 week, 1 month, ...):
I like the idea of being able to pick a variable amount of time. I would not recommend having "Permanent" be the default, because most harassers give up (or get range-blocked) after a while, and it has the effect of blocking legitimate contact from innocent people.
I agree with @WhatamIdoing: Permanent muting should be possible, but we should not encourage this by making it the default option.
Maybe we are talking different cases. If muting a particular temporary account, we probably agree. But there should be a general switch to turn off temporary accounts altogether. This does not hinder them from taking part in discussions, but it would cut my echo notifications by half on some days.
Aschmidt, I don't think we're communicating clearly. Given a proposal that looks something like this:
my proposal is that the default setting in the dropdown menu be something in the middle of the list (e.g., 90 days) – and then you can change it yourself to a shorter or longer time period, depending on your own preferences.
You seem to be insisting here that the dropdown menu must start with the longest possible option in place. Is it really important to you that everyone else start with the longest possible default? Or is it good enough that you be able to switch it to a permanent/lifetime/heat death of the universe setting for yourself?
That's a good question. I thought about it for a while. And I think if the longest possible period is the default in other such dropdown menus, it is a matter of usability and consistency of the user interface to keep it like this in all other places because most users would be puzzled it it was otherwise. This is why I would advise you accordingly.
Most important, of course, would be that such a switch is implemented at all.
BTW, I like the term 'heat death of the universe setting'. :)