In T10813#218207, @Agent_Isai wrote:In T10813#218202, @Naleksuh wrote:In T10813#218164, @Reception123 wrote:In the past we have seen rash resignation prompted by heated arguments. Please do take time to consider this and whether it's worth resigning over one argument. I for one won't be actioning this request until 24 hours pass.
But isn't the point of this request supposed to be VCP enforcement? "resigning over one argument" seems rather undescriptive to me
VCP enforcement would come from a Steward. If we enforce the VCP with an auto-revoke if one argument occurs then neither you nor I would have any roles.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
May 8 2023
May 8 2023
In T10813#218164, @Reception123 wrote:In the past we have seen rash resignation prompted by heated arguments. Please do take time to consider this and whether it's worth resigning over one argument. I for one won't be actioning this request until 24 hours pass.
OK, well, I have explained it now. Sorry for not catching you before.
@Agent_Isai This form is inapplicable. For example, one of the forms asks about "user data" even though there is no user data anywhere there. It is a static site
Apr 3 2023
Apr 3 2023
Naleksuh moved T9912: Have CreateWiki provide a notice about existing wikis on the same topic from Long Term to Backlog on the MediaWiki (SRE) board.
Mar 20 2023
Mar 20 2023
Yes the log entries do but like I said before the other issue is that anything external would be looking for the old groups, like user scripts, scrapers, or just links.
@Void No, there are more places and even if you changed those you can't change external places where it's used (i.e. scripts that people make). Like I said before this happens once in a blue moon and when it does happen it's usually for a technical reason. A good example of this is https://phabricator.wikimedia.org/T112147 - and even when it is necessary, a huge amount of disruption was caused. That's why it's generally recommended not to do that, especially when the point is just to change the display name, which you can already do via MediaWiki pages
Because it's how the group is referenced by code, this means changing that means changing any scripts looking for it, changing every reference to that group in the database, basically anything that points to it, plus it's not really seen by end-users anyway. It could probably be a numeric identifier, but it's not.
Groups can be renamed by editing the relevant MediaWiki pages. If you mean changing the underlying name, this is not something that you are supposed to do; in the 20 years of MediaWiki history I can count the number of times this has happened on one hand
Mar 7 2023
Mar 7 2023
@Reception123 For the root domain naleksuh.com, yes, no-one but me can upload any files there. Some of the subdomains and other domains I have do contain wikis and such that anyone can write to. But I am only asking for naleksuh.com right now
Feb 11 2023
Feb 11 2023
Naleksuh renamed T10478: Rename raspwiki to rpiwiki from To rename raspwiki to rpi to Rename raspwiki to rpiwiki.
@BrandonWM Only the Vector and Vector-2022 skins work like that. No other skins do. Actions are handled outside of skin-specific stuff but it depends on what people want. I thought people wanted something in the toolbox, as otherwise this would too easily repeat the mistakes of the Report extension
Feb 6 2023
Feb 6 2023
I meant the discussion of how the interface should work, not the discussion of what the rules are.
Feb 4 2023
Feb 4 2023
@Reception123 Which one could work? The first or the second?
I just mean "something like" Twinkle. I sent Agent Isai a copy of a prototype but I don't know if they've tried it out yet. If they don't like that one, I will try something else via the backend
Naleksuh added a comment to T9154: Warn wiki requesters if their request is likely to be declined due to issues.
How would a warning after it's submitted be of any use though? Wouldn't that defeat the whole purpose of the warning?
Could this work something like Twinkle?
Feb 3 2023
Feb 3 2023
Naleksuh added a comment to T9912: Have CreateWiki provide a notice about existing wikis on the same topic.
Is there a demand to add new features to this AI? I was under the impression the community had problems with it and it was being phased out, including NotAracham stating that it was a "failed attempt" to make wiki creations automated. There should be consensus to continue developing this, as it's not like this is supposed to be an ongoing thing--I personally have major objections to this AI existing at all, and I don't think I'm the only one, so there definitely at the very least should be consensus to continue working on it
Naleksuh added a comment to T9154: Warn wiki requesters if their request is likely to be declined due to issues.
Hey I just saw this as part of the SRE recruitment however are people sure this is a good idea? The Reception123 examples sound fine, but if the idea is keywords for bad things, I'm more worried this will just make people lie and say other things instead. The subdomain idea sounds great though, so maybe I will look at that :D
Feb 1 2023
Feb 1 2023
Naleksuh added a comment to T10368: Add preference to use safemode across entire site (like ?safemode=1 but don't need it in the URL).
@Reception123 The use case for this in core is relatively low, because it only affects user farms like Miraheze and Fandom. While I would agree with this if the basis were to only have extensions be unofficial, given that many features are put into extensions and how many extensions Wikimedia runs, I see no reason for this to be in core, and is something more suited for the MirahezeMagic extension
Jan 26 2023
Jan 26 2023
Naleksuh added a comment to T10368: Add preference to use safemode across entire site (like ?safemode=1 but don't need it in the URL).
This is more useful for Miraheze than for Wikimedia. Could this be part of MirahezeMagic extension?
Jan 22 2023
Jan 22 2023
Reopening per Universal_Omega
Oct 7 2022
Oct 7 2022
Also it's not really a feature request since it's unintentional. It used to let you do anything even accept but accepting would give a creation error.
@Universal_Omega This is not low priority. There are currently two requests that this affects.
Jun 17 2022
Jun 17 2022
@Reception123 Actually, even Wikimedia phabricator confirms that the default skin is not vector-2022 in 1.38: phabricator.wikimedia.org/T301527
Jun 16 2022
Jun 16 2022
Possible fix at https://github.com/miraheze/mw-config/pull/4764 by Universal Omega
In T9389#190224, @Reception123 wrote:As for the actual issue, since the skin is the default we didn't "set the skin" to a new one without consulting the community, we simply adopted the changes imposed by the upgrade (making the skin default). If the community disagrees with such changes they are free to make their opinion known.
Naleksuh renamed T9389: Revert default skin change back to vector from Set default skin to vector to Revert default skin change back to vector.
Apr 17 2022
Apr 17 2022
I was directed to this task over IRC. It appears to already be closed, and have little relevance to me at all. What is going on here?
Feb 7 2022
Feb 7 2022
I never suggested adding ReCaptcha!
How did you somehow turn "Adding ReCaptcha is a terrible idea" into "having a captcha is a terrible idea"?
Naleksuh changed the status of T8375: Migrate to ReCaptcha Enterprise, a subtask of T8335: Investigate issues with ReCaptcha v3, from Open to Stalled.
This needs consensus. Adding ReCaptcha is a terrible idea for multiple reasons and needs consensus onwiki, not just add it behind the scenes
Jan 23 2022
Jan 23 2022
Also, I apologise for not realising it was your wiki though.
@Universal_Omega To clarify, that's not my site I linked, I just noticed it on there. I can't actually change that config value.
Ah okay, that makes sense. I thought you meant Miraheze sending you the certificate. Yeah, just generating one makes more sense.
How do I make tasks without auto subbing people?
if Miraheze would provide us with a LE Cert.
Jan 20 2022
Jan 20 2022
Naleksuh renamed T8621: Consider creating an import usage policy from Consider creating a fair use (imports) policy to Consider creating an import usage policy.
What exactly does this have to do with fair use?
Jan 18 2022
Jan 18 2022
Naleksuh changed the status of T8622: Rename edgewiki > mirrorsedgecompendiumwiki from Invalid to Resolved.
The scope later changed, but the initial task was not invalid. Stop changing this and frankly just stay away from tasks I create in general.
https://mirrorsedgecompendium.miraheze.org/wiki/Main_Page is now ready, and I've requested deletion of the previous wiki. Thanks for letting me know.
Yeah, it would be easier. But I saw you made some edits. If you are really sure you want to delete that one and create another one, let me know and I can create a wiki for you on the new domain and a steward can delete the previous one
Jan 17 2022
Jan 17 2022
Dec 30 2021
Dec 30 2021
@RhinosF1 This is not long term, it is currently impossible to review wiki requests unless you copy and paste someone else's text. That is a big problem which has gone on for way too long already and it definitely is not something that should just continue for even longer
Dec 18 2021
Dec 18 2021
Yeah, I just recently found out that they were being used for AI purposes. I opposed the AI being a thing at all to begin with, but if it's actively hindering the experience for humans that is definitely a big problem
Mar 22 2021
Mar 22 2021
Feb 15 2021
Feb 15 2021
In T6852#135081, @RhinosF1 wrote:The relay is restored. Further discussions will occur today
In T6852#135079, @RhinosF1 wrote:I have revoked Zppix's access per https://phab.MirahezeBots.org/T193 and will restore the relay
Ah. I'm not really aware of how bot system works. I just wanted to know if it would be run by specific user or on shared resources and/or if the bot is controlled by multiple people.
I'm not totally aware of how bot servers work but will the bot be officially accessible by dev.miraheze.org?
Jan 9 2021
Jan 9 2021
In that case I would likely put this on hold until more extensions are avaailable
It is my understanding that the list of extensions is currently empty. If that is the case, what is the deal with other similar requests?
Dec 24 2020
Dec 24 2020
No problems found here, looked a bit for common problems and examined code, no problems found. Anyone else noticed anything?
Dec 23 2020
Dec 23 2020
In T6360#129984, @John wrote:@Naleksuh any updates on this from your end?
Nov 14 2020
Nov 14 2020
You may add a custom URL using the instructions at https://meta.miraheze.org/wiki/Custom_domains . Be aware you will need to acquire the domain yourself, though
Nov 10 2020
Nov 10 2020
" But @Naleksuh already did." Considering he used "they" I would assume you are supposed to answer, perhaps based on the history of #miraheze. It's also possible to try via reviewing extensions that are proposed for addition, which I could do. Are there any in mind?
Nov 8 2020
Nov 8 2020
While my work in core has been primarily propositions, I like to work on solutions to problems and I have contributed to a number of floating extensions with my specialty being access levels. Me and Universal Omega were also going to make an extension that fixes bypassing create protection, although this is postponed due to IRL issues.
Oct 29 2020
Oct 29 2020
It seems like he got unblocked for a fourth time, which has now removed the block. This may be resolved as a one-time issue caused by the update, but it may be reopened if others face similar problems.
Oct 18 2020
Oct 18 2020
Naleksuh added a comment to T6325: Updated subdomain/database name in RequestWiki, prior to said wiki's approval and creation, does not update.
In T6325#123726, @Dmehus wrote:@Naleksuh may be interested in following this ticket
Sep 20 2020
Sep 20 2020
Are you sure this is not standard caching?
Aug 20 2020
Aug 20 2020
Naleksuh added a comment to T6075: Mass deletion of pages in the attached list, subject to the exceptions described in the separate list.
I'll be honest I kinda wish you had used a full URL instead of just the ticket number ,as "T6075" is useless to people who don't know how phab works. Not a huge deal though.