Wikimedia Meta-Wiki

Community Wishlist Survey 2021/Notifications

< Community Wishlist Survey 2021
Community Wishlist Survey 2021
Notifications
7 proposals, 163 contributors, 211 support votes
The survey has closed. Thanks for your participation :)



Alert after adding or removal a CSD tag

  • Problem: On smaller wikis, pages that are marked with CSD tags can survive for a long period, even if there are active administrators.
  • Who would benefit: Users who choose to activate this feature from Special:Preferences#mw-prefsection-echo.
  • Proposed solution: Adding an option (that per default, it should be disabled) at Special:Preferences#mw-prefsection-echo. If you choose to activate that feature: if a CSD tag is added/removed in/from a page, you will receive an alert about that. In order to work, all CSD tags should contain "<includeonly>__ECHOCSD__</includeonly>" (the adding/removal of this magic world should trigger the alert). If there are added more than one CSD tags in page, you should receive only one alert, to prevent spamming. Also if there are added further additional CSD tags or if there are removed some CSD tags, but not the last (you should be announced only if the last CSD tag is removed from a page). To prevent the adding of __ECHOCSD__ magic word without a CSD tag, it should be created an abuse filter which stop other users to add this magic word in a page, but allows them to place it if they place a CSD tag.
  • More comments: Something similar it could be created for unblock requests.
  • Phabricator tickets:
  • Proposer: --NGC 54 (talk / contribs) 12:59, 18 November 2020 (UTC)[reply]

Discussion

Voting

Automatically Notify a User when ANY of their subpages are edited

Discussion

I agree notifications are crucial for keeping the community interactive. I also lack notifications for inline comments in all Talk pages (in case no explicit ping is made). Cheater no1 (talk) 10:45, 19 November 2020 (UTC)[reply]

Seems reasonable. Dreamy Jazz talk to me | enwiki 00:08, 20 November 2020 (UTC)[reply]

  • I think this proposal is more specific than it should be. Really, there should be a way to watch for changes to subpages of any given page (or pages in any category, for that matter), and for any set of watched pages to generate notification. It might be worthwhile to have one's own page "watched" in that manner by default (in a way that can be disabled), but there should be more fine control over monitoring for changes in general. --Yair rand (talk) 07:13, 17 December 2020 (UTC)[reply]

Voting

Categorize notifications

  • Problem: Every notification is just listed with barely few to no categories, especially those who contribute to one project (or just a few)
  • Who would benefit: Editors
  • Proposed solution: Categorize notifications into: Talk page message / Security / User mentions / You've got email / Others, etc.
  • More comments: This will mean revamp of the notifications system, and would hope to make some other suggestions (e.g. notification on page being edited) being viable and not overwhelm the whole system
  • Phabricator tickets:
  • Proposer: 1233 （T / C） 13:42, 22 November 2020 (UTC)[reply]

Discussion

  • Add one point: It is dumb to select what category to be notified but, when there are notifications, every category just sits there and mix. Categorizing the type before the message received timestamp can smoothen this issue and enable more notification types to be added while not affecting the ease of use of the notification system.--1233 （T / C） 14:13, 22 November 2020 (UTC)[reply]
  • @1233: I'm not sure I follow. What do you mean by "categories"? As in, the icon you see that indicates what type of notification it is? Or do you feel there should be more notification flyouts (right now there is a button for "alerts" and a button for "notices")? Thanks, MusikAnimal (WMF) (talk) 22:29, 2 December 2020 (UTC)[reply]
Sort the notifications by category before by time, at here. e.g. when you click the notification button, it can categorize. e.g. Sort thank yous before mentions before left a message before failed attempts, etc.--1233 （T / C） 06:15, 3 December 2020 (UTC)[reply]

Voting

Real-Time notification

  • Problem: Notifications are not Real-Time if encase of surprise block after users save the edit, however this need to be refresh the page to seen notification.
  • Who would benefit: Contributors
  • Proposed solution: while Contributors are editing may receive an notification without refreshing an page, this helpful for slow internet connection and while reading.
  • More comments:
  • Phabricator tickets:
  • Proposer: Farpen (talk) 03:55, 26 November 2020 (UTC)[reply]

Discussion

  • Hi Farpen. I have some questions about your proposal. You mention blocks in your "problem" statement. Is that an example of how you came up with this idea? Would your wish be for "real-time" notifications that don't require a page refresh even if those notifications are not about blocks? What other kinds of notifications would be helpful as "real-time" notifications? --AEzell (WMF) (talk) 23:39, 2 December 2020 (UTC)[reply]
    • If user was blocked from editing, a "you have a new message" will appear without refreshing, but if user tried to save an edit then an blocked text will appear. Other kind of notification like alerts from "your edit was reverted", "your edit has thanked" and "article reviewed". It maybe useful for any kind of notification like "alerts" and "notices". "Real-Time" notification are not required to refresh an page, those user was blocked without warning may not received an notification and may see a block notice. -Farpen (talk) 02:56, 3 December 2020 (UTC)[reply]

Voting

Logout confirmation dialog

(Machine translation from Japanese to English.)

  • Problem : When I click the "Logout" menu displayed at the top right of the Wikipedia page, the logout is executed immediately. I want you to implement a function that displays a dialog asking if you really want to log out in case you click "Logout" due to an operation mistake even though you do not intend to log out. ..
  • Who can help : All users who may click "Logout" due to an operation error
  • Proposed resolution :
  • Other comments :
  • Phabricator Tickets :
  • Proposer: Keruby (talk) 04:04, 18 November 2020 (UTC)[reply]

Discussion

  • I've discussed a 2-step process for logout somewhere on Phabricator. Not sure where off the cuff. And I feel like this may be a previous proposal? --Izno (talk) 05:14, 18 November 2020 (UTC)[reply]
    @Izno I think you mean phab:T217914 —TheDJ (talk • contribs) 13:19, 4 December 2020 (UTC)[reply]
  • Courtesy pinging community participants of en-WP Village pump discussion who haven't voted yet (apologies if I missed/repeated anyone). @Anita5192, Fuzheado, Randy Kryn, Arnabsaha, Forbes72, Johnuniq, Ovinus Real, Enjoyer of World, Herbfur, JGHowes, RoySmith, 2pou, and Aza24: Please feel free to weigh in on this. {{u|Sdkb}} talk 19:46, 11 December 2020 (UTC)[reply]
  • For anything that makes logging out harder, it's worth thinking about the impact on people who intentionally attempt to log out in a rush, and simply click the link and leave without realizing that they will still have to click something else (and consequently not actually being logged out); there were suggestions to make this out-in only, which potentially alleviates this concern. Another thought that comes to mind is having a countdown timer that starts after the clicking "Log out" (e.g. for 30 seconds or a minute) so that if the user doesn't either confirm the intent to log out or cancel the action altogether within that time, the user will still be logged out; that's an idea inspired by what I've seen on some operating systems, and may help if the user actually clicked it then left in a rush as I described earlier. Hazard-SJ (talk) 06:31, 13 December 2020 (UTC)[reply]
    A countdown seems reasonable. Making this opt-in, however, would greatly diminish its reach, as most people who would want it won't enable it. {{u|Sdkb}} talk 08:28, 13 December 2020 (UTC)[reply]
    Expanding on that thought, I'm imagining that clicking on logout would pop up the box with two options, one of which says something like "yes I really mean to log out" and clicking on it log you out immediately. The second says, "no I didn't really need to log out" and clicking on that undoes the logout request. If neither are clicked, the logout proceeds after some period of time even if you closed your browser and turned off the computer. I think 30 seconds is more than long enough but I'll leave that detail to others. It should be the default not an opt in.--Sphilbrick (talk) 14:28, 19 December 2020 (UTC)[reply]
  • Y a t-il des personnes qui peuvent témoigner s'être déjà accidentellement déconnecté ? Il faudrait voir le pourcentage car j'ai l'impression que c'est plus contre-productif qu'autre chose et que ça fera perdre du temps. -- Nemo Discuter 12:11, 25 December 2020 (UTC)[reply]

Voting

Safari Push Notifications

Discussion

Voting

Edit Notifications

  • Problem: There are some pages where it is important knowing when are edited (ex. Requests to administrators), and just adding them to the watchlist can slow down the response times.
  • Who would benefit: Patrollers, admins, other contributors.
  • Proposed solution: Making users able to create a list of pages that will send them a notification when edited.
  • More comments:
  • Phabricator tickets:
  • Proposer: ValeJappo【〒】 07:45, 17 November 2020 (UTC)[reply]

Discussion

It could be arranged in a two-tier system, with normal addition to watchlist working as currently and some specific pages in that list (to be selected by user) also appear as notification.--FAR (talk) 12:12, 28 November 2020 (UTC)[reply]
Refined options/multiple watchlists, quota system, daily summary and other mechanisms may reduce the consumption.--YFdyh000 (talk) 23:10, 8 December 2020 (UTC)[reply]

Voting

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Community_Wishlist_Survey_2021/Notifications&oldid=20877429"