Page MenuHomePhabricator

Missing button to suppress Flow contents on zhwiki
Closed, InvalidPublicSecurity

Description

A recent finding: OSer is now not capable to suppress any contents on FLOW on zhwiki.
There was a button for OSer to suppress a FLOW thread.
May I ask for your investigation on why the button is vanished?
On the other side, remember that the development of FLOW was stopped.
Is this related to the issue? Thank you.

Details

Risk Rating
Low
Author Affiliation
Wikimedia Communities

Event Timeline

Aklapper renamed this task from Unable to suppress (OS) contents of FLOW on zhwiki to Missing button to suppress Flow contents on zhwiki.Oct 10 2021, 12:16 PM

Is this at all related to T163061 or T175554? Or is this a content suppression feature which did exist at some point and now appears not to?

One more clue: Jimmy, another OSer at zhwiki, who is capable to suppress a FLOW topic. i.e. having such a button on his screen.

photo_2021-10-10_21-54-58.jpg (1×1 px, 31 KB)

This is my screen ↓

image.png (258×1 px, 15 KB)

sbassett changed Author Affiliation from N/A to Wikimedia Communities.Oct 18 2021, 3:48 PM
sbassett changed Risk Rating from N/A to Medium.
sbassett edited projects, added SecTeam-Processed; removed Security-Team.

Can you provide the URL for that screenshot?

I'm able to see suppress button at https://zh.wikipedia.org/wiki/Topic:Wip4w0q8yyhrftwq under my staff account. since you also say another oversighter sees the button, I'd say this is a broken gadget/user script issue.

Could the OSer try to load the page in the safemode? They can do that by appending ?safemode=1 (or, if there's already ? in the URL, &safemode=1). For instance, for the URL I posted above, safemode version would be https://zh.wikipedia.org/wiki/Topic:Wip4w0q8yyhrftwq?safemode=1.

If it works in safemode, they'd need to disable (one by one) their gadgets and userscripts to see which one is broken. Once the problematic gadget/script is identified, the maintainers of that script should be alerted.

Hope this makes sense.

Closing as invalid as this seems to be browser/gadget specific. Please reopen (and provide more details) if you think that is not the case.

@sbassett @Reedy Hello, can you please advise if it's a good idea to publish this ticket now? AFAICS, it affects (affected?) a single user due to a broken gadget/user script rather than any issue in MW.

@sbassett @Reedy Hello, can you please advise if it's a good idea to publish this ticket now? AFAICS, it affects (affected?) a single user due to a broken gadget/user script rather than any issue in MW.

It's fine to make this public now.

sbassett triaged this task as Lowest priority.Nov 8 2021, 9:26 PM
sbassett changed the visibility from "Custom Policy" to "Public (No Login Required)".
sbassett changed the edit policy from "Custom Policy" to "All Users".
sbassett changed Risk Rating from Medium to Low.