@Aklapper We already have some cookies for anonymous users, I just checked in the F12 developer console. Some sort of tracking is needed anyway for stuff like Visual Editor to remember preferences for logged out users (which appears to be done) and to make sure the 'Start editing' dialogue does not appear more than once.

Thinking about it, I think this can just be a toggle on special pages in user preferences. There could be a "Load More" button which just scrolls more, but the toggle would just make the load more button click automatically after scrolling to the bottom.

I intended to add screenshots but apparently I forgot. Anyway here is a couple:

The thing is, though, there is a bottom to these special pages. Well, not the log page, but other special pages have a bottom. Also what loads is predictable almost every time. We are not a social network - we are a wiki, and improving workflow is going to be helpful to readers and editors alike. Nowhere does this infinite scrolling have to be automatic -- a simple button called "load more" could be at the bottom of a special page that loads the next X items and puts it underneath.

I am talking about https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/mw.Api. I have tried the solutions listed on https://www.mediawiki.org/wiki/API:Client_code#JavaScript but they seem largely unintuitive. On the other hand, the library I linked here is a bit more intuitive because it is well documented and allows for code reuse between the browser JS and Node JS.

@Volker_E good start. Can you add @media (prefers-color-scheme: dark) to the gadget-specific portions?

Yep, that disappeared as well for me.

https://en.wikipedia.org/wiki/Special:Preferences

Maybe someone could work on this as a possible future MediaWiki extension, but it does not get rolled out to Wikimedia wikis right away... hmm....

@Aklapper I disagree with this closure. Sure it is technically possible with the abuse filter, but it is impractical to configure 400 or so pages where slow mode is enabled. On smaller wikis, yes, we can use the abuse filter. But on large wikis like Wikipedia, there are dozens of pages that could benefit from slow mode, like articles sanctioned by ArbCom. There is no way to get all those pages into one abuse filter neatly.

Hah, maybe just add this as a feature to confirmedit.

Fine, then maybe just upgrade to slidercaptcha and do nothing else. The text CAPTCHAs are very broken anyway.

Unfortunately, that is a downside. We will still need an audio option. But this may be one step in the right direction, as it is pretty obvious that you need to fill the puzzle piece, which is a lot more accessible than the blurry mess you get from our current CAPTCHAs.

I do not know how I ended up creating two tasks from one click, but that appears to be an error. Can this task be deleted @Aklapper?

Here is a CAPTCHA idea that we could maybe implement on Wikimedia (for visual Captcha).

I am a few months late to this discussion, haha.

Okay... I focused on one specific task at hand right now. Someone probably already asked this before but the task is located at T269210.

@Aklapper thank you for the feedback. :)

@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