This is veryyyy annoying

😢

The Cloud-Services project tag is not intended to have any tasks. Please check the list on https://phabricator.wikimedia.org/project/profile/832/ and replace it with a more specific project tag to this task. Thanks!

Any update on this?

idk why bug bot didn't link this but this exists: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/952276

Some other thoughts:

When an article is being edited by 2+ editors. I think the latter is already a feature.

This is somewhat related as autogeneration could also help human editors... but

Here are some demo queries and responses testing this with English Wikipedia revisions:

Was interested in how many hours this could save per year and queried for a rough answer: https://quarry.wmcloud.org/query/76523

All I can find is: https://github.com/viagrunts/viagrunts

@Krinkle I was originally planning to use LinkRenderer for Echo, but then that would make notifications have 2 links (clicking on them and a link inside them). Additionally, links inside of notifications were a thing in the past, but removed for UI reasons. We could use LinkRenderer and hack our way around it by stripping everything but the page title, but that doesn't seem like a clean solution.

Here is a past change someone made to mediawiki install files to allow this behavior: https://www.mediawiki.org/wiki/Topic:Vn3phnl79hyleo6s

Looks to be working now

504 Gateway Time-out is now the error.

Sure

I do too.

Spent about 6 hours trying to solve this and was unable to.

@Michael yes! The hook for that purpose is what I'm requesting here: T334803: Create PageTitle hook

Yep. This is so annoying.

This is literally not stalled for the above reason.

I think I screwed up my ownership of some directories which caused this. I solved by reinstalling OS.

I screwed up my ubuntu installation somehow and I reinstalled to OS and now it works.

Prob bad UX. They had page names originally and were changed for a reason. Having the notification be linked and the page names linked is bad.

Fair points, especially about the standardization.

What does that comment even mean?

I mean it's totally possible. You just set up a tracking database to determine which requests are sent to each server. Isn't this up to WMDE to decline?

Reopening for the above reason. Revising the task description to better-convey what this is requesting.

See also Wikidata Telegram discussion about feedback on the new mute button.

Agreed.

It's already possible to add examples to every parameter. Does this help?

No, I don't. This mute notifications option is particularly useful for Wikibase users who may want to easily unsubscribe from receiving notifications from entities that are often linked to an entity that they created. I don't know if it would be annoying for normal wiki users or not though.

I think this is increasingly becoming a common design pattern found on many major websites (see task description)

I also don't think GitHub or Reddit are going to be removing their "Copy link" buttons anytime soon.

more likely to used by senior contributors.

So senior contributors are more-likely to be able to decipher unintuitive designs than newbies? I don't think so. People are going to continue to ask "how do I get the link to a comment" at some point if there is not a button no matter how much experience they have. Nobody wants to keep answering that question.

Esanders is a god

I created a userscript that allows you to filter label, alias, and description changes by language: https://www.wikidata.org/wiki/User:Lectrician1/filter-watchlist-languages.js

How is this even hard @Arian_Bozorg? You just borrow an example from "Wikidata property example" that matches the format constraint and display it in the constraint message.

Yeah @Aklapper this task is requesting for the ability for users to cancel a query on the query server, not starting another query when another one is running. This task should be open.

Reopening because it was declined for a reason unrelated to the original request. Users want to be able to cancel queries so that they can create new ones easily and not have to wait - not because this will increase performance (and what ideas do you have?).

Idk this looks like it would require an intermediate database to keep track of which query ids are being sent to which servers.

Seriously? Could this like be updated in documentation?

@Bleakprestiger it's in https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/Flow/+/refs/heads/master

when I run git clone it asks me for my paraphrase before cloning over ssh but get-code does not.

git clone https failed:

Here is the diff file extracted from the Google Code Archive source Peter originally stored his work in if anyone would ever want to work on integrating it:

idk I think my OS is screwed up. mwcli doesn't have permissions to write to anything.

Well now it doesn't work again!

idk I was unable to until I chowned it

Ohhhhhh. Whatever it works now. I think it was my stupid WiFi network which sometimes doesn't let me download certain stuff.