@Soda that seemed to fix the issue, but it would be good if the documentation was updated to include that.

My browser info

I found something that can help with having dark mode on Vector/Monobook/Timeless/Minerva: https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme

@Aklapper

I used Windows Steps recorder to try show you the issue in more detail.

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

In T219697#5072182, @Nirmos wrote:

How can "edits" ever be stored as a "cookie"?

They can't. A cookie can only hold around 4–10 kB or so.

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.

@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.

This does not seem fixed, as this problem appears on Edge as well, and still does on the Wikipedia article ammonia.

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

closing, it may have been a problem with my computer :)

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.

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)?

Great job getting started on fixing this!!!

How about NoCAPTCHA?

I notice that the problem is with some sites (like Wikipedia) but not others.

or not

Closing, this issues appears to be fixed.

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

Sorry

Actually closing, they show up at Special:BlockList

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.

Closing this task, please put such requests on Meta, not here.

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.

Check on en.wikipedia.org. I have done it there, and I do not want to send mentions to the users here either.

Okay

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.

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?

I still think the close my account extension is the solution

@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.

The extension should be deployed, only that the username is changed to deletedaccount-[x] where x is the number for the deleted account.

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.

In T166858#3310169, @Aklapper wrote:

Whatever "Fandom" is (probably some hosting service?),

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?

Yes

(Removing MediaWiki-User-management tag as this does not seem to be a request to write code in MediaWiki core.)

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.

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.

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:

1. The user cannot use the same username.
2. All of their pages will be tagged for speedy deletion.
3. The above cannot take effect for 30 days.

This will prevent errors and also ensure that users do not circumvent their blocks.