This is not an article, file or the talk page of an article or file. If you find this page on any site other than the Wikimedia Commons you are viewing a mirror site. Be aware that the page may be outdated and that the user to whom this talk page belongs may have no personal affiliation with any site other than the Wikimedia Commons itself. The original page is located at https://commons.wikimedia.org/wiki/User_talk:Aristeas.
This is the user talk page of Aristeas, where you can send messages and comments to Aristeas.
Be polite.
Be friendly.
Assume good faith.
No personal attacks.
Please sign and date your entries by clicking on the appropriate button or by typing four tildes (~~~~) at the end.
Put new text under old text.
New to Wikimedia Commons? Welcome! Ask questions, get answers as soon as possible.
Latest comment: 29 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The Article guidance team invites experienced editors of pilot Wikipedias—Arabic, Bangla, Japanese, Portuguese, Persian, Turkish, Simple English, Spanish, and French—to help translate and adapt sample outlines. These outlines will guide editors in creating clear, well-structured, and policy-compliant articles when using the feature once it is launched in May 2026. Simple instructions on how to translate and adapt the outlines are available.
The number of available thumbnail size preferences in MediaWiki is being reduced to three standardized options—Small (180px), Regular (250px), and Large (400px), as part of ongoing efforts to improve performance and reduce strain on thumbnail services. As a result, existing preferences will be mapped to the nearest new size (for example, smaller selections like 120px or 150px will render at 180px, while larger ones like 300px or 360px will render at 400px). The preferences interface will soon be updated to reflect these changes, and users who wish to opt out or provide feedback can do so. [1]
From now on, even when a permission expires automatically, users will receive an Echo notification similar to the standard notification for permission changes. There is a difference between this and Global reminder bot in that the latter reminds users a week before the rights are due to expire, so that they can renew the rights.
View all 32 community-submitted tasks that were resolved last week. For example, the problem where the ULS language selector in Special:Translate would scroll vertically when it shouldn't, has been resolved. Previously, when users opened the "Translate to English" dropdown and typed certain inputs, the dialog would scroll vertically by a few pixels even when there was enough space to display all results. The dropdown no longer shifts unnecessarily when filtering languages. [2]
The Global Watchlist, which lets you view your watchlists from multiple wikis on a single page, continues to improve. For example, watchlists for Wikibase sites such as Wikidata now support EntitySchema elements for better tracking. The Live Updates mode now refreshes the special page every 60 seconds to comply with the updated global API rate limits for improved real-time responsiveness. Additionally, a directionality bug that displayed links as "changes 3" instead of "3 changes" in mixed-direction lists has been fixed. [3][4][5]
Updates for technical contributors
The second phase of global API rate limits has been rolled out to reduce the impact of AI crawlers and ensure fair, sustainable access to Wikimedia resources, prioritising human and mission-aligned traffic. Limits have been shifted from per-hour to per-minute, producing smoother traffic patterns and more predictable API load. Community users are not expected to be affected, and no action is required. Early indications show some User-Agent-based requestors are adjusting behaviour, and around 64% of automated API traffic has been identified. Monitoring continues, and Wikimedia Enterprise remains available for commercial support.
Latest comment: 24 days ago1 comment1 person in discussion
Hi everyone,
Wikimedia Commons is pleased to finally announce the winners of this year's Picture of the Year 2025 contest! We had some truly incredible finalists to choose from, but the community has spoken.
Here are your top three winning images:
First place: The aftermath of an Israeli airstrike in Gaza City on October 9, 2023, leaving widespread destruction in the Rimal area. Attribution: WAFA (Q2915969) / CC-BY-SA 3.0
Second place: Baby cape fur seal (Arctocephalus pusillus) sleeping at Cape cross, Namibia. Attribution: Giles Laurent / CC-BY-SA 4.0
Third place: A gigantic jet photographed from the International Space Station by astronaut Nichole Ayers. Attribution: public domain
You can view the full results and see where all your favorite images placed here: Full 2025 Results
I also want to highlight what an incredible turnout we had. In the second round, we saw a massive jump in both the number of users voting and the total votes cast. We had exactly 13,979 votes cast by 3,509 users! To put that in perspective, last year we had 7,403 votes from 2,837 users. It is amazing to see that level of growth and community engagement.
Thank you to everyone who voted, helped organize, and generally made the contest such a huge success this year!
Latest comment: 22 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
Community Tech has published new guidance explaining how wishes on Community Wishlist are triaged and prioritized. The documentation is intended to help contributors write stronger proposals by clarifying the factors that influence prioritization decisions. Beyond vote counts, the guidance highlights considerations such as potential impact on the community when determining which wishes move forward.
Updates for editors
The Reader Growth team is launching an experiment to test a new Share Card feature that allows readers to create visually engaging cards from Wikipedia articles or selected article sections and share them online, with each card linking back to the original article to help expand readership and article discovery. The mobile-only A/B test will be available to a portion of readers on Arabic, Chinese, French, Vietnamese, and English Wikipedia to better understand reading and sharing habits, and is scheduled to begin the week of May 18 and run for four weeks.
The Android and iOS Wikipedia apps recently released the 25-day reading challenge into Beta, as part of efforts to drive reader engagement by encouraging users to complete reading milestones. To track their reading streak during the challenge, App users can add a widget featuring Baby Globe to their home screen. The challenge officially begins May 11.
View all 17 community-submitted tasks that were resolved last week. For example, an issue where the global preference for enabling syntax highlighting in wikitext could unexpectedly disable itself after being turned on, has now been fixed. [6]
Latest comment: 9 days ago5 comments2 people in discussion
Hallo lieber Aristeas,
nun ist es wieder Zeit für eine neue Sony Alpha 7R-Kamera, und ich würde gerne wissen, ob sie aus Deiner Sicht ein Quantensprung ist, und beispielsweise für Deine Arbeit konkret ein Zugewinn wäre? Ich bin noch bisschen am Überlegen, einerseits gibt es sinnvolle Neuerungen, andererseits könnten Manche ein kritisches "Braucht's des?" hinterherwerfen. Liebe Grüße und angenehmes Wochenende! --PantheraLeo1359531 😺 (talk) 20:23, 15 May 2026 (UTC)Reply
Hallo PantheraLeo1359531 😺, ich muss mir die neue α7R VI noch genauer ansehen. Aber mein Eindruck anhand der technischen Daten und nach dem Lesen/Schauen einiger erster Berichte ist: Die α7R V hatte ja gegenüber der α7R IV v.a. den Autofokus, die Ergonomie, den Bildstabilisator und allerhand praktische Details verbessert, die reine Bildqualität war dagegen praktisch gleich geblieben. Daher war die α7R V zwar ein großer Fortschritt bei „bewegten“ Motiven, aber z.B. bei Landschaft und Architektur i.Allg. gleichwertig mit der α7R IV. Die α7R VI bringt nun nicht nur erneut deutliche Verbesserungen beim Autofokus usw., sondern diesmal wohl auch wieder bei der Bildqualität. Damit meine ich weniger die paar Megapixel mehr, vielmehr hoffe ich, dass Sony der α7R VI den DGO-Trick (Dual Gain Output) spendiert hat, mit dem sie bei der α7 V (ohne R) den Dynamikumfang bei ISO 100 deutlich verbessert haben (siehe dazu etwa hier oder hier). Ich warte noch auf eine Bestätigung dieses Details (DGO) für die α7R VI, hoffe aber sehr, dass es drin ist, und erwarte mir davon eine spürbare Verbesserung des Dynamikumfangs, z.B. der Möglichkeit, Schatten aufzuhellen, was auch für Landschaftsfotografie usw. wertvoll ist … Daher finde ich, nachdem ich die α7R V übersprungen habe, die VI sehr interessant. Soviel für heute, mehr ggf., sobald ich ein paar wirklich detaillierte Tests zuverlässiger Leute gefunden habe. Herzliche Grüße, – Aristeas (talk) 08:56, 16 May 2026 (UTC)Reply
Ja, die ausführlichen Tests werden wichtig. Die Auflösung hat man wahrscheinlich leicht erhöht, um bei den Datenblättern zu zeigen, dass sich was tut. Die Kamera setzt den Blinker aber auch stark Richtung a1 :D. Ich habe bisschen mit Mapillary angefangen, da ich der Dynamikumfang schon eine wichtige Verbesserung, da man aufgrund der Serienaufnahme keine HDR-Reihen schießen kann. Mal sehen! Liebe Grüße --PantheraLeo1359531 😺 (talk) 20:58, 16 May 2026 (UTC)Reply
Hallo PantheraLeo1359531 😺, hier gibt es jetzt eine Bestätigung, dass die Bildqualität der α7R VI u.a. beim Schattenaufhellen wirklich drastisch besser ist als diejenige der α7R IV/V: [8], springe zum Beitrag #68 von aidualk. Dazu das verlinkte Vergleichsbild: [9] (weiß aber nicht, ob der Link über Commons funktioniert, sonst bitte aus dem Beitrag im Forum heraus aufrufen). Das sind nur Ausschnitte aus der DPReview-Testszene, aber aidualk ist mit der Experte für solche Fragen der technischen Bildqualität, er weiß also wirklich, worüber er schreibt. – Der Vergleich lässt die α7R VI so deutlich besser aussehen, dass ich mich ernsthaft frage, ob ich doch irgendwie die 5000 Euro zusammenbekomme. Die α7R V konnte ich leichten Herzens überspringen, aber die VI ist wirklich verlockend. Hm, leider habe ich das Geld nicht, aber falls Du es zusammenbekommst, würde ich Dir jetzt doch zuraten. Herzlich – Aristeas (talk) 08:51, 24 May 2026 (UTC)Reply
Das klingt wirklich supi :). Mir ist das tatsächlich aufgefallen, dass der Dynamikumfang der aR V teils nicht ausreichend ist, als ich mit Mapillary anfing. Da haben vor allem die Wolken Probleme gemacht. Das habe ich über HDR-Brackets immer übergangen, aber es gibt Fälle, wo das nicht klappt. Damals habe ich auch überlegt, ob ich von der R IV zur R V wechseln soll, da hat vor allem der Bildstabilisator und die Videoaufnahme doch viel geholfen. Das eine Bild habe ich mir angeguckt, das wäre ja eine üble Verbesserung :o. Hätte ich bei der LFG-Con heute bisschen gebraucht, hehe :). Das Geld wäre weniger das Problem bei mir. Ich bin in meiner Stadt über ein Fotoprojekt eingespannt, das es sich zur Aufgabe macht, von nennenswerten Bauwerken eine Fotosammlung anzulegen, die, sofern wir die Erlaubnis haben, auch auf Commons veröffentlichen. Dort wird geprüft, ob ich eine "Ehrenamtsprämie" vom Freistaat Bayern bekäme, mit dem zusätzlichen Geld könnte ich die neue Kamera finanzieren und meine alte behalten. Das wäre gerade für Veranstaltung hilfreich, wenn ich nicht immer das Objektiv wechseln muss. Aber ich werde eh den Sommer abwarten, da ich im Falle eines Umtauschs nicht auf meine Kamera kurzzeitig verzichten kann. Zu viel los :D. Aber ich find's gut, dass wir eine sichtbare Verbesserungen haben. Jedes Jahr kommt ein neues Smartphone raus, und da werden selbst unter Labortests nicht wirklich Verbesserungen gemessen. Ich fand nur das Marketing des 8K etwas lustig, da das wohl kaum jemand nutzen wird :D. Für Archivarbeit ist es jedoch wiederum hilfreich. Wenn ich mir Sprengungen von Kraftwerken oder Hochhäusern angucke, ist das hilfreich, da es dir die Entscheidung nimmt, wann der "richtige Moment" ist, du eine Bewegtbildaufnahme hast UND ausreichend hochauflösende Standbilder hast, die den Sensor auch deutlich besser ausreizt, als das "mickrigere" 4K. Grüße! --PantheraLeo1359531 😺 (talk) 18:53, 24 May 2026 (UTC)Reply
Latest comment: 15 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The Abstract Wikipedia team has identified five potential pilot wikis to assess their interest in adopting abstract articles on their wikis. The pilots are Malayalam, Bengali, Dagbani, Arabic, and Indonesian Wikipedia. The feedback period will be open until May 22. If your community is interested in becoming a pilot, let us know on Meta.
Updates for editors
An experiment to show Reading Lists to logged-out readers on mobile web will launch on May 18 across German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu Wikipedias, and will run for one month. The effort supports broader goals of helping readers save and organize articles for later reading, while encouraging habits that could lead to future Wikipedia contributions.
To support a bookmark button in the Reading List beta feature, the "Tools > Action" menu has been updated to display icons, including the watch star indicator that helps editors identify temporarily watched articles. The icons now also match those used on mobile, improving consistency across platforms. The change is currently limited to the actions menu and mainly affects editors with privileged user rights. [10]
Suggestion Mode was released as an A/B test for newcomer editors on the mobile website at ~15 Wikipedias. The experiment will measure the impact that Suggestion Mode has on the proportion of newcomer mobile web edit sessions that result in constructive (un-reverted) article edits. The experiment will also evaluate the feature's impact on editor retention, and monitor changes in revert and block rates.
View all 27 community-submitted tasks that were resolved last week. For example, an issue in the Wikipedia Android app where images could sometimes fail to load after opening a recommended reading list notification, has now been fixed. [11]
Updates for technical contributors
The Wikidata Platform team has published its backend replacement recommendation and accompanying technical architecture for the migration of the Wikidata Query Service (WDQS) away from Blazegraph. Feedback is invited until May 25th 2026, especially on potential gaps and impacts on advanced use cases. Wikidata community members and WDQS users are also encouraged to help identify high-impact tools and workflows that may need attention on this page. Feedback can be shared on the Migration talk page or during the next office hour. See the WDP team newsletter for more details.
On English, French, Japanese, and a few other Wikipedias, there was a trial of hCaptcha, a third-party bot detection service. The trial showed that hCaptcha effectively detects and deters some bad-faith automated activity, on its own and by giving checkusers and stewards signals to look into. Because the results were positive, hCaptcha will be rolled out across all wikis over the next few weeks. See the hCaptcha project page for technical information about the implementation and privacy protections. Learn more.
The latest Community Tech update is now available, with progress across several Community Wishlist initiatives, including Reading Lists expansion from the mobile app to the website, new language support for "Who Wrote That" and the Personal Dashboard, improvements to 3D rendering and Charts, and upcoming work on talk page sorting, audio playback, and editing workflows. The update also shares current priorities, wishlist status trends, and opportunities for community feedback on future focus areas and the Wikimedia Foundation’s 2026–2027 Annual Plan. Read the full newsletter for details.
Latest comment: 13 days ago1 comment1 person in discussion
Dear member of the Commons Photographers User Group,
I hope you’re well and enjoy your time as a photographer on Wikimedia Commons. In my role of the new chair of the user group, I have a couple of updates to share with you.
After the election, the new board met for the first time on March 21 and immediately got to work. We elected the organization’s officers and decided to move from quarterly to monthly board meetings. We believe meeting more frequently will create more opportunities to serve our members effectively and help move the group forward.
We also successfully applied for a pre-conference at the upcoming Wikimania in Paris (July 21–25). If you’re planning to attend the conference, please consider joining us on July 21th for a day full of conversations about photography and Commons. Please sign up here if you’re interested.
And finally, it’s my pleasure to invite you to our first online meeting, which will take place on May 31. Our member Wojciech, an experienced concert photographer, will give a talk on photographing orchestras during live performances. I’m especially excited that we’ll have the opportunity to meet online again and am very much looking forward to this event.
Latest comment: 8 days ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
Following a successful account creation experiment, an improved logged-out edit warning message will be deployed to all Wikimedia wikis in the first week of June. The change will only affect logged-out users on mobile web who open an editing session. The updated experience is designed to encourage account creation more clearly, while still allowing users to edit with temporary accounts. Results from the experiment showed a significant increase in account creation, with a 27% relative lift among users shown the updated message. As expected, as more people funnel into account creation, temporary accounts decreased by a relative 16%. The experiment did not show any significant changes in constructive edit rates or other monitored contributor metrics. [12]
Updates for editors
For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Members of these groups will be unable to disable the last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the next few weeks, users without 2FA will be removed from these groups. Notably, this applies to bureaucrats. See the linked tasks for deployment schedules. [13][14]
After two successful experiments, the Reader Growth team is rolling out an Image Browsing beta feature for all Wikipedias on mobile on May 25. This means that anyone who has all beta features on by default will start to see this feature, and others can check the box to turn it on in their preferences. The beta feature will include a carousel of all an article's images at the top of the article, with controls for editors to exclude images from the article's carousel or to exclude an article from the feature entirely.
View all 30 community-submitted tasks that were resolved last week. For example, three dimensional STL files were being rendered incorrectly by the media viewer 3D extension which is now fixed. [15]
Updates for technical contributors
The legacy CSS classes tleft and tright have been replaced with floatleft and floatright as the former do not work consistently across all MediaWiki platforms, notably mobile web and mobile apps. Projects relying on these classes are encouraged to review related usage and plan for migration. Please note that floatleft and floatright may also be deprecated in future, although there are currently no plans to do so. Read more.
Latest comment: 9 hours ago2 comments2 people in discussion
Dear Aristeas, my comment of "the robot is dead, long live the new script" was just a joke, but I understand that it may have sounded dismissive, I am very sorry. The script is still in testing and I added a validation check to avoid conflicts when the bot already started the same task. I also agree that the final review and count should remain a human step, and let the bot help by showing the result before closing. Wilfredor (talk) 14:28, 1 June 2026 (UTC)Reply
Latest comment: 1 day ago1 comment1 person in discussion
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. [16]
Latest comment: 8 hours ago1 comment1 person in discussion
The Technical Barnstar
I want to give you a small recognition for your work on FPCBot archiving, which served as inspiration for fpc-archiver.js. Also, thank you for encouraging other developers and for your collaborative spirit.
View all 32 community-submitted tasks that were resolved last week. For example, the problem where the ULS language selector in Special:Translate would scroll vertically when it shouldn't, has been resolved. Previously, when users opened the "Translate to English" dropdown and typed certain inputs, the dialog would scroll vertically by a few pixels even when there was enough space to display all results. The dropdown no longer shifts unnecessarily when filtering languages. [2]
The ResourceLoader module _191220-0135-HDR.jpg){kind=link}
