(Go: >> BACK << -|- >> HOME <<)
Jump to content

User talk:GeneralNotability

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Archives (Index)

Wikidata weekly summary #634[edit]

Here's your quick overview of what has been happening around Wikidata over the last week.
This is the Wikidata summary of the week before 2024-07-01. Please help Translate.

Discussions

  • New requests for permissions/Bot:
    • DifoolBot 4 Task(s) - Split single references containing multiple reference URLs into multiple references.
    • Bot Bozze Task(s) - Add sitelinks to itwiki draft articles after they've been moved to the main namespace.
  • New request for comments: Spelling convention for labels and descriptions in English - RfC started 2024-06-25. This RfC requests feedback and input for finding consistency in spelling convention as English has multiple regional variations.

Events

  • Past: The Lexicodays 2024 was an online event designed to offer a discussion space for the Wikidata community about Lexicographical Data. An archive of some of the slides and session recordings are here c:Category:Lexicodays 2024. More will be added as they become available.
  • Upcoming:
    • The next Wikidata+Wikibase office hours will take place on Wednesday, 16:00 UTC on Wednesday, 10th July 2024 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
    • Talk to the Search Platform / Query Service Team—July 3, 2024
    • Botany-focused Wikidata online workshop online as part of the #IBC2024. Date: Tuesday 9th July at 9pm NZST (GMT+12) / 11 am central Europe. Register here!

Press, articles, blog posts, videos

Tool of the week

Other Noteworthy Stuff

  • The second iteration of the Wikidata:Open Online Course has begun. Class will continue until August 11. Whether you're a beginner taking your first steps, an individual in need of a refresher on Wikidata concepts, or a seasoned trainer looking to level up your skills - this course is right for you.

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • EntitySchemas:
    • We worked around an issue where EntitySchema pages were no longer considered “content” and had become unsearchable (phab:T368010)
    • We prepared for the release of the new datatype on July 2nd.
  • mul language code: We are working on the last remaining blocker before rolling out the first stage to Wikidata (phab:T362917)
  • Wikibase REST API: We are continuing to rework API errors (phab:T366911, phab:T366239)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Weekly Tasks

Tech News: 2024-27[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • Over the next three weeks, dark mode will become available for all users, both logged-in and logged-out, starting with the mobile web version. This fulfils one of the top-requested community wishes, and improves low-contrast reading and usage in low-light settings. As part of these changes, dark mode will also work on User-pages and Portals. There is more information in the latest Web team update. [1]
  • Logged-in users can now set global preferences for the text-size and dark-mode, thanks to a combined effort across Foundation teams. This allows Wikimedians using multiple wikis to set up a consistent reading experience easily, for example by switching between light and dark mode only once for all wikis. [2]
  • If you use a very old web browser some features might not work on the Wikimedia wikis. This affects Internet Explorer 11 and versions of Chrome, Firefox and Safari older than 2016. This change makes it possible to use new CSS features and to send less code to all readers. [3][4]
  • Wikipedia Admins can customize local wiki configuration options easily using Community Configuration. Community Configuration was created to allow communities to customize how some features work, because each language wiki has unique needs. At the moment, admins can configure Growth features on their home wikis, in order to better recruit and retain new editors. More options will be provided in the coming months. [5]
  • Editors interested in language issues that are related to Unicode standards, can now discuss those topics at a new conversation space in MediaWiki.org. The Wikimedia Foundation is now a member of the Unicode Consortium, and the coordination group can collaboratively review the issues discussed and, where appropriate, bring them to the attention of the Unicode Consortium.
  • One new wiki has been created: a Wikipedia in Mandailing (w:btm:) [6]

Problems

  • Editors can once again click on links within the visual editor's citation-preview, thanks to a bug fix by the Editing Team. [7]

Future changes

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 23:56, 1 July 2024 (UTC)[reply]

The Signpost: 4 July 2024[edit]

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 13:38, 4 July 2024 (UTC)[reply]

Administrators' newsletter – July 2024[edit]

News and updates for administrators from the past month (June 2024).

Administrator changes

added
removed

Technical news

Miscellaneous

Sent by MediaWiki message delivery (talk) 07:58, 6 July 2024 (UTC)[reply]

Voting to ratify the Wikimedia Movement Charter is ending soon[edit]

Copied from Wikipedia:Village pump (miscellaneous) § Voting to ratify the Wikimedia Movement Charter is ending soon because this page is listed on Wikipedia:Village pump (miscellaneous)/Subscribe.
You can find this message translated into additional languages on Meta-wiki. Please help translate to other languages.

Hello everyone,

This is a kind reminder that the voting period to ratify the Wikimedia Movement Charter will be closed on July 9, 2024, at 23:59 UTC.

If you have not voted yet, please vote on SecurePoll.

On behalf of the Charter Electoral Commission,

RamzyM (WMF) 03:45, 8 July 2024 (UTC)[reply]

Wikidata weekly summary #635[edit]

Here's your quick overview of what has been happening around Wikidata over the last week.
This is the Wikidata summary of the week before 2024-07-08. Please help Translate.

Events

  • Upcoming:
    • The next Wikidata+Wikibase office hours will take place on Wednesday, 16:00 UTC on Wednesday, 10th July 2024 (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
    • Registration for Wikimania 2024 is open! In-person participants: please register until 26 July, 11:59 p.m., UTC. Virtual participants can register anytime. If you received a scholarship from the Wikimedia Foundation, you will receive an email with a registration code and instructions.

Tool of the week

  • User:Teester/EntityShape.js - a userscript that adds an input box to a Wikidata page wherein you can enter an EntitySchema (such as E10). When you click "Check", checks whether each statement and property conforms to the schema. It then displays a summary at the top of the Item for each property indicating whether they conform or not. It also adds a badge to each statement and each property on the page indicating whether they conform or not.

Other Noteworthy Stuff

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • EntitySchemas: The new datatype to link to EntitySchemas in statements has been released.
  • mul language code: We are preparing the release.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Weekly Tasks

Tech News: 2024-28[edit]

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

Problems

  • A problem with the color of the talkpage tabs always showing as blue, even for non-existent pages which should have been red, affecting the Vector 2022 skin, has been fixed.

Future changes

  • The Trust and Safety Product team wants to introduce temporary accounts with as little disruption to tools and workflows as possible. Volunteer developers, including gadget and user-script maintainers, are kindly asked to update the code of their tools and features to handle temporary accounts. The team has created documentation explaining how to do the update. Learn more.

Tech News survey

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 21:29, 8 July 2024 (UTC)[reply]

U4C Special Election - Call for Candidates[edit]

Copied from Wikipedia:Village pump (miscellaneous) § U4C Special Election - Call for Candidates because this page is listed on Wikipedia:Village pump (miscellaneous)/Subscribe.
You can find this message translated into additional languages on Meta-wiki. Please help translate to other languages.

Hello all,

A special election has been called to fill additional vacancies on the U4C. The call for candidates phase is open from now through July 19, 2024.

The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members are invited to submit their applications in the special election for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.

In this special election, according to chapter 2 of the U4C charter, there are 9 seats available on the U4C: four community-at-large seats and five regional seats to ensure the U4C represents the diversity of the movement. No more than two members of the U4C can be elected from the same home wiki. Therefore, candidates must not have English Wikipedia, German Wikipedia, or Italian Wikipedia as their home wiki.

Read more and submit your application on Meta-wiki.

In cooperation with the U4C,

-- Keegan (WMF) (talk) 00:02, 10 July 2024 (UTC)[reply]

IPBE permanent status[edit]

Hello. You granted me IPBE status last year in August for a period of one year and my rights are about to expire so I wanted to make you aware that I have emailed the checkuser team to appeal/apply for permanent status in case you had any input about my asking for it again this time on a permamnent basis this time. Thank you for granting me the right for this past year. It has been very helpful for me. Huggums537voted! (sign🖋️|📞talk) 15:42, 11 July 2024 (UTC)[reply]

(talk page watcher) @Huggums537: you should probably be aware that the checkusers mailing list does not accept emails from non-members, so your message may not have gone through. In future you can email the functionaries' mailing list, which checkusers are also members of, at functionaries-en@lists.wikimedia.org. I saw your request here and I've extended IPBE for you for one more year from the previous expiry. Ivanvector (Talk/Edits) 16:08, 11 July 2024 (UTC)[reply]
@Ivanvector, I don't believe the functionaries list accepts outside email either. The correct address for IPBE requests is checkuser-en-wp@wikipedia.org (see WP:IPECPROXY). – bradv 16:15, 11 July 2024 (UTC)[reply]
I was just about to say that I got the email address by following the instructions given in the How to request section at WP:IPECPROXY which @Bradv had beat me to already. If it isn't accepting emails instructions need to be updated or someone needs to check it to make sure emails are getting through... Huggums537voted! (sign🖋️|📞talk) 16:28, 11 July 2024 (UTC)[reply]
Hmm, the private list is checkuser-l, not checkuser-en-wp. Maybe I've got it all mixed up. Whatever it is, I didn't see your email. I'll ask around and someone will update those instructions if need be. Ivanvector (Talk/Edits) 16:51, 11 July 2024 (UTC)[reply]
The request did go through to the correct channel, and I just closed the ticket. – bradv 17:10, 11 July 2024 (UTC)[reply]
@Bradv and @Ivanvector, I am also applying to get permanent GIPBE at: Steward requests/Global permissions and I am concerned that a mere one year extension here will affect that decision there since they waited to see if IPBE was established here before they would establish GIPBE there. Will you please reopen the ticket here and reconsider giving me the permanent IPBE I was requesting since there was a misunderstanding here where Ivanvector essentially granted a good faith extension without even seeing the actual request? Thank you very much. Huggums537voted! (sign🖋️|📞talk) 17:24, 11 July 2024 (UTC)[reply]
My understanding of the local policy is that we are only allowed to grant the permission for terms of at most one year, and then you should re-apply if you still need it. I see nothing wrong with granting it to you for a longer term or indefinitely, other than that I don't think I'm allowed. Anyway, global IPBE does not let you edit through local IP blocks, so you'll also need the local permission even if you're granted the global one. And checkuser-en-wp is the right address: that's the intake queue for the checkuser volunteer response team, which I'm not on for some reason.
I'm going to see what we can do for you here, but it might take a little while to figure out. You're good to go for now, at least. Ivanvector (Talk/Edits) 18:30, 11 July 2024 (UTC)[reply]
@Ivanvector, thank you for the immediate good faith extension here without having seen the "complete and official" request first, but only this cursory one here. Also, thanks for the strong vote of confidence for an indef status on my IPBE rights. It will be ok if it takes some time to figure out because I just realized they must have changed the rules over on Meta since I first established the rights. It appears they now require a minimum two week period before granting any requests, presumably for reasons related to deliberation/consensus. On a side note, I stumbled upon some interesting information that might be helpful to the case. When I was browsing the userpage of my former mentor @SMcCandlish, I found that @Jon Kolbert had given him GIPBE with no expiry so that got me to thinking to check this list for other examples of users that are not nor ever have been admins with no expiry set on IPBE and I didn't even get past the "A"'s when I found that @Materialscientist granted Ammarpad IPBE with no expiry since late 2017. Just to make sure this was not a one-off or some weird quirk, I went ahead and found one more example where @KrakatoaKatie also granted Antiqueight IPBE with no expiry since late 2017 as well. I hope I don't have to go through the whole list in alphabetical order all the way to the "Z"'s to find every single example here... Huggums537voted! (sign🖋️|📞talk) 09:17, 12 July 2024 (UTC)[reply]
Huggums537, in 2017 IPBE and other user rights were on/off; you had it permanently or you didn't have it at all. Expiration dates for user rights didn't come until just a couple of years ago. If you want to go find all examples of IPBE without expiration, be my guest, but it won't endear you to the CUs and it won't help your case for a longer term. Please do not ping me again to this thread. Katietalk 04:05, 13 July 2024 (UTC)[reply]
My apologies to all the users pinged in this thread. I just realized I provided the examples above to prove a point without actually making any point. The point I was trying to make is that there appears to be evidence of a wide latitude for discretion of the setting of expiry as in the example just a couple years ago where @Deepfriedokra granted APK the customary one year right, then no expiry after that. Huggums537voted! (sign🖋️|📞talk) 07:59, 13 July 2024 (UTC)[reply]
There is also another very similar example to that one right here where the customary one year IPBE was granted and then no expiry after that. I'm not really all that worried about endearing myself to CU's. I just want what makes sense to me and however I can show proof it appears to be customary and fair. Thank you. Huggums537voted! (sign🖋️|📞talk) 08:43, 13 July 2024 (UTC)[reply]

Comment: I don't usually give away a whole bunch of personal information, but if it will help the process to come to a decision more efficiently, I can share the fact that my primary profession is in the transportation industry and travelling for work IS what I mainly do for a living. The real estate investing, online selling, and other stuff are just side hustles. I think reasonable people can see I am a busy person on the road not living in my parents' basement so having no expiry set would relieve me from pointless periodic time wasting. (No offense to anyone living in the folks' basement. I'm all for saving money!) Huggums537voted! (sign🖋️|📞talk) 11:59, 12 July 2024 (UTC)[reply]

@Huggums537: I have a lot of experience of granting IPBE. Yes, we have a lot of discretion. Currently the longest I grant is I think about 3 years (maybe some a bit longer), which is generally for people who have had one or more year-long grants before, and have a network/block problem (i.e. a need) lasting that long. Our granting practices have changed over time, and vary by admin for other reasons, but there is a definite trend towards not granting risky rights indefinitely. This is because users do not last forever, and when they become inactive their accounts become a rich target for compromise attempts. Plus they confound attempts to maintain rights for others who may or may not need them. I think you'll find that checkusers are on average happy to grant IPBE in many cases, for as long as they are needed. They are not needed indefinitely, which in many cases is equivalent to forever, and so it's not really reasonable to insist on indefinite. Just ask for a longer period each time and you will soon have enough IPBE to not worry about it again. Come visit me in a year and I'll make sure the next grant is longer, if you still need it. Most meta stewards understand our rights-granting policies and it shouldn't affect what they grant you. -- zzuuzz (talk) 08:44, 13 July 2024 (UTC)[reply]
WOW. 3 years seems kinda strict compared to others who have set no expiry. I appreciate the offer, but I might wait for a better one to come along from a more freethinking admin since Katie already warned me my crazy idea of going through the whole list to find all the examples wouldn't help me so it seems my best option is to humbly wait patiently for someone to be kindly generous or freethinking since I have not made any effort to endear myself to anyone. I guess that is the rub. Maybe if I wasn't so cold and calculating, then you guys would trust me more and I could endear you to just give me what I want because you like me and trust me so much...😂 Huggums537voted! (sign🖋️|📞talk) 09:47, 13 July 2024 (UTC)[reply]
Trust and like don't really come into it, though I will say that it's easy to squander good opportunities. Ivan granted IPBE apparently even without reading your full request, and I'm in the same position. No, the question is one of need. You need IPBE? You have it. You need it forever? Unlikely. -- zzuuzz (talk) 10:44, 13 July 2024 (UTC)[reply]
Well, I will keep your opportunity in mind. It is appreciated. I just see things differently than most do I guess. IPBE has probably been around here longer than I have so it doesn't make any common sense to me that it suddenly became a security risk in just the past couple years. I think you probably described the situation very accurately when you said the idea of this has led to a recent practice where ...there is a definite trend towards not granting risky rights indefinitely. I'm of the belief that this is more grounded in the "trend" part of the description where a type of herd mentality led to others following the trend thinking it was some sort of brilliant idea when in fact it may have all been started just because one person wanted some way to put a restriction on some asshole. If it truly were such a great security risk, then we would have to ask ourselves about that question of need and why anyone outside of admins much less the 5 examples I gave would ever need it "forever". We would also have to ask ourselves why all of the people who currently have it "forever" and are not admins are not being restricted with time limited rights. Has there really been any serious discussion about this "risk" or is it truly just a recent trend in the community as you described? Huggums537voted! (sign🖋️|📞talk) 13:28, 13 July 2024 (UTC)[reply]
I think that it's time to drop this, before someone starts wondering why you would care so much about avoiding scrutiny a year from now. – bradv 17:35, 13 July 2024 (UTC)[reply]
Oh. I've heard this music before and the overture to this melody tells me my eardrums will be blown out of proportion before the end of the crescendo so it was real nice chatting with you fine folks... Huggums537voted! (sign🖋️|📞talk) 20:05, 13 July 2024 (UTC)[reply]

Arb case of ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ[edit]

Hello, I believed this one, ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk · contribs) is WMF-banned user, Gustin Kelly (talk · contribs). Will you tag their userpage as sock? -Lemonaka 03:45, 12 July 2024 (UTC)[reply]

The Bugle: Issue 219, July 2024[edit]

Full front page of The Bugle
Your Military History Newsletter

The Bugle is published by the Military history WikiProject. To receive it on your talk page, please join the project or sign up here.
If you are a project member who does not want delivery, please remove your name from this page. Your editors, Ian Rose (talk) and Nick-D (talk) 12:08, 13 July 2024 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:GeneralNotability&oldid=1234330093"