User Details
- User Since
- Nov 27 2014, 3:32 AM (489 w, 6 d)
- Availability
- Busy Busy until Apr 30.
- IRC Nick
- Niharika
- LDAP User
- Niharika29
- MediaWiki User
- NKohli (WMF) [ Global Accounts ]
Thu, Apr 4
I think this task can be brought in to the sprint now.
Tue, Apr 2
Fri, Mar 29
Thu, Mar 28
We haven't heard any complaints from our previous deploys. This should be good to go now.
Mon, Mar 25
Dec 22 2023
@PBradley-WMF I have included a mock for what this look like in a comment above. Can you please confirm if it looks OK?
And for the link to the policy - the link you provided originally was for the Minimum requirements section. Is that intentional?
The current patch links to the entire page. That can be changed if you feel the section is more appropriate.
Current design:
Dec 19 2023
We have decided to go with serial instead of scramble.
Dec 16 2023
This feature is being scheduled for a complete rollout over the next couple of months. The plan for complete rollout is outlined in T280531: Enable partial action blocks on all Wikimedia production wikis and in MediaWiki by default.
After Chinese Wikipedia's deployment, we will not accept any more pilot wikis. Instead, we plan to deploy to all wikis. The plan for complete rollout is outlined in T280531: Enable partial action blocks on all Wikimedia production wikis and in MediaWiki by default.
Dec 15 2023
Dec 14 2023
@taavi It's good to go.
Dec 8 2023
Dec 6 2023
Thanks for waiting on me. I think we can go ahead on this. Sorry for my late reply!
Dec 2 2023
I can confirm that revealing a user's own IP address to themselves should be OK.
Nov 29 2023
@KSiebert I believe these extensions are also owned by CommTech:
- PageAssessments
- WikimediaOCR
- RealtimePreview
Nov 27 2023
I expect querying older IPs that no longer exist in Spur database would be a valid use case. I don't have a good sense of how important is it for end users (do they run into these IPs once a month? do they run into these IPs a few times a day?). I suggest we wait on user feedback before prioritizing this feature enhancement. We can make this an explicit focus when we gather user feedback after Spur is integrated into IP Info.
Nov 23 2023
Nov 21 2023
@stjn If there is any feedback from the community about this feature (positive or negative) I would love to hear it. Thank you for managing this.
Nov 20 2023
Nov 17 2023
@dom_walden can you confirm if this bug still persists?
Nov 7 2023
Nov 6 2023
Oct 31 2023
+1 to what @Tchanders said. @Samwalton9-WMF we should talk about this.
Let's go ahead with bullet list of the various blocks. Consistent with what we did on T344463.
Oct 30 2023
Oct 26 2023
Oct 25 2023
Oct 24 2023
Based on the feedback, I think we should do the following:
- Adding a line break in $2 of blockedtext-composite breaks the list created by the initial colon, so the real reason appears in its own paragraph with no indent. With a template generating a block-level element, the period after the </em> also ends up on its own line.
- Remove the blockedtext-composite-reason "There are multiple blocks against your account and/or IP address" because that doesn't make sense.
- Loop over all original blocks and show the blockedtext message for each one.
Oct 17 2023
Oct 13 2023
Thanks for the comment @L235. @Xaosflux @AntiCompositeNumber @Izno @taavi as a quick solution for this problem, is the currently implemented solution acceptable?
... show one local block message, but not necessarily the preferred one if there are multiple local blocks
Oct 12 2023
Oct 10 2023
Thanks!
Sep 26 2023
Sep 22 2023
Sep 19 2023
Would it be preferable to build this special page into its own extension or tap into an existing extension like CentralAuth?