Aug 31 2019
The main problem is that going through recent changes on large projects like Wikipedia is a nightmare. Because Wikipedia gets thousands of edits every hour, it becomes extremely difficult to patrol recent changes for vandalism, etc.
@Aklapper wikiHow just upgraded to MediaWiki 1.33: https://forums.wikihow.com/discussion/28385/mediawiki-upgrade-coming-today-thu-aug-1-new-code-now-out
Mar 31 2019
So they can be stored in the database but they are deleted after 24 hours and invisible to all users. That could work but can still create issues with copyrighted content.
Mar 30 2019
Mar 5 2019
Oct 3 2018
Aug 24 2018
@Aklapper: this is on meta.wikimedia.org. And actually, I just realize that it is a side effect of another of the scripts I wrote, so closing this task as invalid.
Aug 23 2018
Aug 8 2018
This does not seem fixed, as this problem appears on Edge as well, and still does on the Wikipedia article ammonia.
Aug 7 2018
Jun 4 2018
Jun 3 2018
I am unsure about the source code just for RC patrol, but I do know the source code that wikiHow runs off of is located at src.wikihow.com
May 30 2018
Apr 21 2018
Feb 20 2018
closing, it may have been a problem with my computer :)
Feb 12 2018
Timeless is a skin that I believe is designed for Desktop. I think it is supposed to make Wikipedia look like other wiki sites (such as wikiHow or Wikia). I could be wrong, so please make any corrections.
Nov 16 2017
And the idea with url shortening is that the article name will be the thing after the url so that it is easy to enter in.
And w.wiki url shortening is disabled. Bummer.
I like domain hacks, and they make lives a lot easier. (Goo.gl/e) or (google.com)? (Group.me) or (GroupMe.com)?
Oct 18 2017
Great job getting started on fixing this!!!
Oct 6 2017
How about NoCAPTCHA?
Sep 30 2017
I notice that the problem is with some sites (like Wikipedia) but not others.
Closing, this issues appears to be fixed.
Sep 29 2017
Sep 28 2017
Sep 17 2017
Also... add ?action=viewsource so that editors can view the source code, whether or not if they have permission to edit. When the user clicks "edit", instead of saying "View source for "$1"" it should say Permission error: You have been blocked from editing or whatever MediaWiki:BlockedText says
Sep 11 2017
Actually closing, they show up at Special:BlockList
Sep 10 2017
blocked users see "edit" instead of "view source". And title blacklisted titles also see an "edit" tab instead of "view source". The tabs should say "view source" for the previous two.
Sep 9 2017
Closing this task, please put such requests on Meta, not here.
Sep 7 2017
My contribs (included my deleted ones). What I did was transcluded my user talk page into my user page, where mention notifs were sent. Then I transcluded my user page into a user subpage, where they were sent again. I left an apology on my talk page, but that was disruptive enough to get me blocked indefinitely from editing. I only have access to this diff (https://en.wikipedia.org/w/index.php?title=User:UpsandDowns1234/main.css&oldid=794971340). I transcluded the css file a while ago before doing this to my chat.
Sep 6 2017
Check on en.wikipedia.org. I have done it there, and I do not want to send mentions to the users here either.
Sep 5 2017
Also, see [//en.wikipedia.org/wiki/User_talk:Iridescent]
I transcluded a userpage with a bunch of links to other's userpages into another userpage. Do this on Test Wikipedia, it got me blocked indefinitely on en.wikipedia
In other words, modify the extension before deploying.
I actually realize that this should do the same thing as global locking except that they are given a link to unlock their account that expires in thirty days. Of course, if they contact a steward, then the account can be reactivated, but this will likely be declined unless if their account was compromised.
Sep 2 2017
Sep 1 2017
Aug 31 2017
Regarding the Community-consensus-needed tag, I would bring this up to the Village pump on Wikipedia, but am currently indefblocked. Where else can I mention this?
Aug 26 2017
I still think the close my account extension is the solution
Jul 22 2017
Jul 13 2017
@MarcoAurelio there is a 30-day grace period. Adding email reminders at T-30 days, T-15 days, T-5 days, and T-1 day can ensure that the editor is aware that their account is closed.
Jun 8 2017
The extension should be deployed, only that the username is changed to deletedaccount-[x] where x is the number for the deleted account.
Jun 4 2017
Closure is different from deletion - Deletion removes all existence that the account existed, closure prevents the user from logging in by scrambling the password and changing the username.
Jun 3 2017
Yes, Fandom is the global community for all wikis on Wikia.
there is the ability to close one's own account.
Why would you like to "close" an account, compared to not using an account anymore? Which problems does that solve?
Closing accounts prevents unused accounts from being compromised or becoming sockpuppets.
This task currently proposes a solution to an unknown problem.
The problem is similar to why Google and Microsoft offer account closure. It removes most of the evidence that the user never existed: it removes the user's credentials, removes the settings, and scrambles the password, but does not remove the user's contributions.
Can you add that functionality to Wikimedia?
Is this a request to review and deploy the "CloseMyAccount" extension on Wikimedia servers?
(Removing MediaWiki-User-management tag as this does not seem to be a request to write code in MediaWiki core.)
Jun 2 2017
It would supplement the right to vanish. What close my account does is scramble the password, remove the email address, and change the real name to Deleted Account.
May 21 2017
Which is also used to prevent vandalism.
The cascade protection is to ensure that if administrators forget to protect any files transcluded in the MediaWiki namespace, the files are automatically protected.
May 20 2017
Apr 25 2017
This can be fixed by denying all transclusions
Apr 16 2017
It would be best if this function was created, however, with the blocked users and the banned users deleting accounts to circumvent their blocks, they should be locked into their account so they cannot sign out or delete. Also, to prevent errors, all contributions must be assigned to an identifier. The following can occur:
- The user cannot use the same username.
- All of their pages will be tagged for speedy deletion.
- The above cannot take effect for 30 days.
This will prevent errors and also ensure that users do not circumvent their blocks.