- User Since
- Oct 16 2014, 4:00 PM (86 w, 1 d)
- Status
- Available
- LDAP User
- Unknown
- MediaWiki User
- Scott
Recent Activity
Thu, May 26
Copied comment from over there: adding as a blocked task because if the magic linking code is going to be addressed it should be done properly, rather than a hacky workaround in the notifications code.
Adding that as a blocking task because if the magic linking code is going to be addressed it should be done properly, rather than a hacky workaround in the notifications code.
@Quiddity - sincere apologies. I was reading on my phone and completely misinterpreted the diff. All good.
I agree that pages in the draft namespace shouldn't get a "publish" button. If anything, an action somewhere in the UI labelled "publish" that is actually "move this draft to mainspace" would be a useful feature. That's obviously outside the scope of this task.
Wed, May 18
@Quiddity, I object strongly to the change to the task description that you've made. You replaced a decade-old high-level request with a specific, and Byzantine, feature implementation proposal.
May 11 2016
See also T49402 (Better diff for revision deletions: Show indicator of what visibility restrictions were set or unset).
Mar 4 2016
Sorry for late entry of an external commenter into this discussion.
Mar 3 2016
Is this still valid now that we have global accounts?
Someone's fixed it.
Note: SUL finalization has removed the "local users" referred to in the original bug report from 2006. However as far as I'm aware the import tool is still setting rev_user = 0 (T111605). Once that's been dealt with, the possibility is there for a cleanup script to be developed to fix attribution on all imported edits.
Account unification happened (hooray!) so this is no longer necessary.
That's not a requirement for filing enhancement tasks. Disregarding for now the unreasonable nature of a request to find people talking about an idea that I just had, doing so wasn't a requirement in any of the previous tasks I filed, either. Rather than being met with a demand to justify their existence, those tasks have either been implemented, started being implemented, merged, or, for the most part, left to accumulate comments over years, as normal.
Is the patch attached to this still valid?
The answer to all your questions is "it's a user preference, so let it happen if they want it".
Feb 9 2016
Jan 27 2016
Jan 13 2016
The link to the sample conversion in the description of this task is broken.
Jan 12 2016
Jan 7 2016
Jan 6 2016
Jan 3 2016
jake wrote in the description of this bug:
Right now when an unprivileged user tries to view a deleted diff they are told that the revision has been hidden, but no why or who by.
Dec 12 2015
@lfaraone, what's the story with this?
Dec 3 2015
Nov 30 2015
Nov 19 2015
Better solution would be tagging as @Bawolff suggests.
This should probably be closed - preferences for these tools are likely to be set on the tools themselves instead, which is better. See T33881.
Nov 14 2015
Every way to examine changes made to the database (edits, deletions, etc.) should be filterable by namespace. Being able to filter Special:Log/delete by namespace is particularly useful for improving the accountability of administrators.
Nov 12 2015
Nov 10 2015
Oct 28 2015
Oct 24 2015
Oct 19 2015
Oct 18 2015
Oh, of course, these days it would also involve renaming the other account. Well, I'll ask there. Thanks Steinsplitter.
Oct 6 2015
If any work is being done on this fairly complex development, could serious thought please be given to implementing multiple watchlists (T3492) either as part of it, or first, which have been requested as a core feature since at least 2005.
I've merged this task from 2007 into a task from 2005 that addresses the core topic of multiple watchlists in a general fashion.
Sep 28 2015
Sep 27 2015
Sep 23 2015
Okay, thanks for letting me know.
Sep 22 2015
Sep 19 2015
Sep 18 2015
Sep 16 2015
Please see commentary on parent task, this doesn't need to be done.
Sorry Keegan, you've misunderstood. These edits belong to Mirwin. That IP-style user name is an artifact of the Stage II import process and doesn't represent a user that needs a global account. As I mentioned above, read T5631 for an explanation of its significance.
Sep 12 2015
Reopening as I've found some more - https://en.wikipedia.org/wiki/Special:Contributions/12.45.50.xxx (including the creation of some major articles!). See T5631 for the background on the user name.