Wiktionary:Grease pit/2026/June
Will I be able to log in?
[edit]Hello, need help from a bureaucrat, if there is a simple solution. I got a message telling me to give a 2-way-authentication or a passkey. I am very stupid with computers, I do not use phones (I use a laptop) and the login 'change password' will not accept anything.
I have described my sad -and perhaps laughable- story at https://meta.wikimedia.org/wiki/Talk:Mandatory_two-factor_authentication_for_users_with_some_extended_rights#KeeWeb_cannot
The passkeys i get with 4letter words do not work as passwords. e.g.
- Recovery codes created: 18:44, 1 June 2026 (2026-06-01T18:44:13Z)
- MG4K etc....
I fear that I will not be able to log in at all in the future with my current username. Will I be able to log in? (never mind the rights). Thank you, sorry to bother: if it is too complicated, never mind ‑‑Sarri.greek ♫ I 19:21, 1 June 2026 (UTC)
I changed my previous password to 'a safer, stronger' and it gives me captcha, but still, I cannot log in. Probably, because I am already logged in. O! I'll never log out, to make sure I am alive. ‑‑Sarri.greek ♫ I 19:58, 1 June 2026 (UTC)
Tech News: 2026-23
[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.
Updates for editors
- The Reader Experience team is conducting an experiment to show the reading lists feature, which is still in development, to logged-out mobile readers to test whether it encourages account creation at a higher rate compared to the watchstar button. The experiment was launched on May 18th on German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu wikis, and it will run for a month.
- The Wikimedia Apps team released Phase 1 of the redesigned Home Feed to the Android Beta app. The new Home Feed includes a refreshed "Community" tab and a personalized "For You" tab featuring daily updated reading recommendations. The redesign is part of a broader effort to improve content discovery and create more engaging learning experiences in the Wikipedia apps.
View all 18 community-submitted tasks that were resolved last week. For example, an issue where images could fail to load for some suggested edits on Special:Homepage, leaving the thumbnail stuck in a loading state, has now been fixed. [1]
Updates for technical contributors
- Detailed code updates later this week: MediaWiki
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 21:08, 1 June 2026 (UTC)
Unicode Abuse Autoflag
[edit]I was surprised that Wiktionary autoflags ̏̏̏ for Unicode abuse (when I tried to use it for my user page) even though I had never had this error with my Wikipedia user page. Can anyone explain this to me? TooMuchofAnything (talk) 00:13, 2 June 2026 (UTC)
- @TooMuchofAnything: See WT:USER and WT:NOT. Wiktionary user pages are for specific purposes related to users' work on the dictionary- not for showing off their personal style. If the abuse filter hadn't stopped you, there's a good chance the page would have been deleted. Chuck Entz (talk) 05:56, 2 June 2026 (UTC)
- Fair enough; I'll just not have a user page for now. TooMuchofAnything (talk) 16:29, 2 June 2026 (UTC)
I notice that this page is showing up in the "Pages included on this page:" of just any page with a translations table that I spot-check, e.g. remember, minoritary (and it appears that just any and every such page is showing up in the Whatlinkshere of the page). It is not present on pages that lack translations tables, like alembravas and Aleppo soap. So, it's not useful as a tracking page, since it's tracking lots of pages that don't use lzh or indeed any zh at all. Is it still needed, in which case, can it be improved to only track lzh? - -sche (discuss) 05:52, 2 June 2026 (UTC)
Object animacy in translations
[edit]Adding translations of English terms is really easy thanks to the translation tool, but the one problem I have with the resource is that there seems to be no way to describe the animacy of a noun without an unassisted edit. This particularly annoys me as a Polish speaker, however some more widely spoken languages like Hindi and Arabic could also be affected by this issue. While I can't speak for those two, I know that nouns like "członek" (member) or "miś" (bear) change their animacy depending on which context they are used in, so a translation of English member in the sense of person who belongs to a group and in the sense of body part have different animacies.
My suggestion is to add an optional parameter that lets the user select animate, inanimate and animal as a noun's animacy (or deselect it, if they clicked the option by accident) to the translation template.
(Reupload, because I mistakingly posted this in the beer parlour) To te umarłe słowa (talk) 17:52, 2 June 2026 (UTC)