User Details
- User Since
- Jan 4 2015, 2:23 PM (500 w, 2 d)
- Availability
- Available
- LDAP User
- IKhitron
- MediaWiki User
- IKhitron [ Global Accounts ]
Wed, Jul 31
I'm just curious, why wasn't the standart Wikicode editor Search popup extended with the new functionality instead of creating two working at the same time?
Thu, Jul 25
Answering to the wikitech letter. As a heavy user of the extension over the years I can add my five cents.
- I really hope there will be local notifications, so the readers can see their content immediately, without a need to go to Meta.
- The expected Flow shutdown will kill the Newsletter extension, FMHO, if there will not be done adjustments in the extension code.
- The Newsletter extension is a great thing, and it should continue and evolve.
Tue, Jul 23
Yes, good idea. One possible impact is that looks like it kills the Newsletter extension, except there will be found an alternative way to keep it.
Sat, Jul 13
Well, @thiemowmde, it took us always a month, but I've implemented it by your request. So much time because I've made it at least ten times more functional than the bare minimum, and every key was needed to be coded and approved in the metro project. Hope you like it, on both maps. Thanks again for paying my attention to this issue.
Jul 1 2024
Maybe there is a way to add to the algorithm a paragraph "if you show subsubpage in the line X, but its master page exists and wasn't shown above, then show the master page in the line X+1?"
Done.
I think the task should be reopened, there were a couple of cases in the last few days.
Jun 23 2024
Jun 20 2024
Could anyone, please, tell me, for inwiki purposes, when exactly the noresize code was changed in the New Vector, so I could tell the community when the problem started. Thank you in advance.
Thank you all for this. I'm not so sure I'm smart enough to understand all this but I'll try my best at least to evaulate it as described. I'm glad you agree it's not the gadget problem.
I don't think you should check the gadget at all, just the area tags in the safemode. But if you insist, there is a completely separate sandbox with completely separate sandbox javascript code, and you can edit them all, if you wish. The area coordinates are here.
By the way, the gadget has apparently no support for keyboard navigation, one of our most basic Accessibility requirements.
Great idea, thanks, we'll consider it.
The gadget author suggests it could be T265549.
Maybe if I could know, what changed in the New Vector in svg rendering on in area tag, I could understand what to look.
This is possible, of course. But I have no idea how to find what part could volitale, when the gadget do not distinct between skins.
New Vector:
Legacy Vector:
Jun 12 2024
Well, for the last 21 hours no querry could run. So it's pretty bad.
Jun 9 2024
I didn't see any complains this time on hewiki forums.
Jun 5 2024
-1. But I think it's fine to have a non default preference for this. So anyone who does want to get these mails could turn this on.
Jun 4 2024
Jun 3 2024
May 9 2024
I hope it will work soon, because now I can't delete any item, not just some.
Apr 22 2024
Any solution that avoids the situation with script does not run without any explanation is fine.
Yep. Exactly. There are a lot of people that upload files with wrong licenses onto local wikis and Commons. There are special forces which are supposed to stop them, VRT. There will be the same count, or maybe even more, people that will do it inline. Who will recognize and stop them? Or the VRT groups are supposed to do much more work? And to learn how to do this at all?
A silly question. Apologies if it was already mentioned before and I missed it.
Where exactly will be the license? And how exactly it will be checked, and by whom, to avoid copypasting inline some copyrighted svg file, such as a company logo?
Apr 17 2024
Thanks, done.
A pity.
Apr 16 2024
Well, there is a new button "delete" on mediawiki.org. Clicking on it makes the item disappear. Refreshing Special:EditRecovery brings everything back. Houston, we have a problem.
Apr 8 2024
There are much more cases when this needed, see here.
Apr 2 2024
Looks like it indeed.
Mar 15 2024
My attention was drawn to this bug after I saw this, when moving the help icon to its appropriate place:
I made a very stupid fix for now, from
Mar 11 2024
In this case we definitely should consult to community first, because otherwise, from my experience, nobody will pay attention. A week discussion will put it on the radar.
Mar 10 2024
"Opt-in" means that newcomers to enwiki, for example, do not get it by default, @MusikAnimal?
Mar 2 2024
I request to cancel the change for hewiki, please. The community decided to ask this, in Village pump, with more than enough voices, at least 31 supported from 32 that participated. You can find the voting over here. Thank you.
Feb 29 2024
Well, I tried a couple of times to explain you it has nothing to do with all this, with new pages for example, only with any edit in any article. I can see no way to explain more.
This is something else, of cource. For me, if some user can't be trasted to make their one edits in articles, they for sure can't be trusted to have an Interface admin flag, which was created just because the Foundation didn't think the admins (sic!) were trusted enough to have. You definitely can have different ipinion.
Feb 28 2024
Don't know what are the relevant tags.
Seems obvious, but OK.
Feb 24 2024
Feb 20 2024
Really hope this is the case. The current text looks like "write us, we make statistics, and abandon the current task, if there are a lot".
One more question, please. If we "write it as a task on the Phabricator", as mentioned above, what are our chances to leave it on our wiki as is? You said nothing about this.
Feb 19 2024
Hi there. A couple of questions.
If patroller X has a patrolling script that adds tags to some existing edit, will it work?
If AbuseFilter triggered by autoconfirmed adds tags to theirs edit, will it work?
Feb 18 2024
Wow, I created a task, a d didn't even remember the previous one that I created in 2017 wasn't fixed, thought it's a new bug.
Feb 15 2024
Feb 14 2024
Well, I've just tried four most significant scenarios, and it works fine.
Feb 12 2024
I've asked to retrieve my bot flag, which I temporarily gave away a while ago due to lack of time. I know pretty well what is going on now on Watchlist in different modes, because I wrote a huge gadget, Whatchlist Manager, years ago. So, I'm planning to create various use cases to check what is the state after the deployment. Starting from this one:
- Open some watched page at 23:59.
- Close it.
- Go away for an hour.
- During this period, another accounts edit this page: three non-bot edits, a bot edit, three more non bot edits.
- Return to the screen and open the Watchlist in group mode, showing new edits only.
I expect to see a new group with seven edits. As far as I understand from todays Tech News, I will see none. Those before because of the new change, since marking an edit as seen marks automatically all the previous ones. Those after because of the mentioned old bug in the new conditions. The best result will be if I see all the seven.
Jan 29 2024
Very well. Changing to "Avoid the possibility to give the interface-admin rights to users without autopatrolled or autoreviewed rights" will by OK for you? So that user must have at least one of these two.
Because as far as I understand, not being a regular on enwiki, just from reading that page, autoreview and autopatrol are synonims. If they are not, I can always change the task title to be "Avoid the possibility to give the interface-admin rights to users without autopatrolled or autoreviewed rights", to fit both cases.
What do you mean by "autopatrol"? (in enwiki, to be more clear)
You mean, each sysop's edit is patrolled by a human patroller? The page https://en.wikipedia.org/wiki/Special:ListGroupRights claims otherwise, see "Have one's own revisions automatically marked as "accepted"" in sysop chapter.
I'm not talking about autopatrol group, but about autopatrol rights. The user's edits should not be manually patrolled. Sysops have this included for there group too.
I suggest to restrict someone without autopatrol rights to get interface admin, because that means the local community does not trust them. Autoconfirmed is just automatic rights, not related to my suggestion.
I see now. You changed my words too, not just title. Itbrakes also the facts and my thoughts. I don't know why did you do this, but if you think the opposite of my suggestion, you can always create another task. I return my request back.
@JJMC89, I do not understand your edit. It has no sence now.
Jan 9 2024
I would suggest somethink like
Pages that use the JSON contentmodel will now use tabs instead of spaces for autoindentation. This will significantly reduce the page size.
The first sentence because otherwise it will look like "name":"John Doe" -> "name":"John\tDoe" conversion, or even asking the users to insert tabs manually. The second one explains the large impact more straightforward.
Jan 5 2024
Jan 4 2024
Dec 25 2023
Well, enough time later I can say that the problem disappeared a second after the consequent deployment. Unless somebody else continues experiencing it, I would suggest to close the task.
Dec 12 2023
You do remember it's an Android problem?
Dec 11 2023
Dec 9 2023
Even didn't see the misaligned part.