User talk:Hazard-SJ
Hello Hazard-SJ, it looks like your bot is no longer archiving that page. Maybe you can have a look at it. Thanks and Best regards, --Ameisenigel (talk) 22:40, 26 November 2021 (UTC)
- Just came to report this myself, any updates? DannyS712 (talk) 01:51, 2 January 2022 (UTC)
- Thanks for reporting this, and for the reminder! I'll look into it. Hazard-SJ (talk) 13:41, 2 January 2022 (UTC)
- @Ameisenigel, DannyS712:
Fixed, thanks again! Hazard-SJ (talk) 14:12, 2 January 2022 (UTC)
- Thanks for resolving this! --Ameisenigel (talk) 14:15, 2 January 2022 (UTC)
- @Ameisenigel, DannyS712:
How we will see unregistered users
[edit]Hi!
You get this message because you are an admin on a Wikimedia wiki.
When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.
Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.
If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.
We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.
Thank you. /Johan (WMF)
18:20, 4 January 2022 (UTC)
Reminder to participate in the Ratification vote of UCoC Enforcement guideline
[edit]This message has been sent because you are administrator in this project. If you voted, Thank you and please ignore this message 🙂
Hello Hazard-SJ,
The Ratification vote of Universal Code of Conduct Enforcement Guidelinein currently taking place until March 21. If you didn't vote yet, please take a few minutes to participate the ratification vote! Your voice is important.
Best, —YKo (WMF) via MediaWiki message delivery (talk) 04:44, 15 March 2022 (UTC)
Smarter archiving of solved sections
[edit]Is it possible to expedite archiving of sections marked as solved? Or add such functionality to User:Hazard-Bot/Archiver?
that would be useful on Wikidata talk:WikiProject Ontology
Mateusz Konieczny (talk) 20:59, 29 November 2022 (UTC)
- @Mateusz Konieczny: Would
{{Autoarchive resolved section}}
do what you need? It can be used in parallel with{{User:Hazard-Bot/Archiver}}
. Hazard-SJ (talk) 07:56, 2 December 2022 (UTC)
Bad edit on RFD
[edit]This edit doesn't seem to be very useful and has resulted in misleading signatures. Bovlb (talk) 15:54, 20 June 2024 (UTC)
- Hi Bovlb, thanks for bringing this to my attention.
{{Rfd group}}
is a template that, as mentioned in its documentation, should always be substituted. Since you used that template without substituting it, the bot did the substitution on your behalf. But as it happens, substituting that particular template also adds the signature of the substituting user (so you wouldn't have had to sign manually if you had substituted the template yourself). If we want the templates to be automatically substituted when users don't do the substitution themselves, I don't think there's a current standard for handling this situation:{{Rfd group}}
has anosign
parameter that can cause the signature to be omitted when substituted.{{Uw-vandalism1}}
(and most/all other user warning templates) automatically add the signature on substitution without a way to disable.{{Currentuser}}
will (by definition) always be wrong if substituted by a different user than the user who added the template.{{Welcome}}
avoids the problem by requiring the signature to be provided via a template parameter.
- In contexts where a signature is expected (discussion pages), my uninformed hypothesis (solely based on the diff you share) is that users manually sign most of the times when they didn't substitute one of these templates. In such cases, the undesired effect - and current behavior - is that, in addition to the user's own signature, a second signature and timestamp (from the bot) gets added. That would also be true in some cases where a different human user manually performs the substitution (without making a 2nd edit to subsequently delete the undesired signature). Are we okay with the bot's signature sometimes showing up, based on that knowledge? If not:
- Is there a general solution that we can/should apply to all templates that include a signature to handle this scenario?
- Requiring users to explicitly add signatures after the template when they're needed (i.e. no more auto-sign) is an option, but might not be ideal for users who are accustomed to auto-sign and any automation that relies on that existing behavior.
- Would it make sense to expect all such templates to support a
nosign
parameter, and for the bot to always specify that (whether or not it is a valid parameter)?
- Alternatively, would we prefer leaving the task of substituting any unsubstituted usage of the various
{{Subst only}}
templates up to humans altogether?
- Is there a general solution that we can/should apply to all templates that include a signature to handle this scenario?
- Hazard-SJ (talk) 05:07, 28 June 2024 (UTC)