User talk:Aristeas
Add topic
This is a Wikimedia Commons user talk page.
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.
- Click here to start a new topic.
|
|
Вікі любить пам'ятки 2025 в Україні / Wiki Loves Monuments 2025 in Ukraine: ще тиждень конкурсу!
[edit](text in English at the bottom)

Привіт! Дуже сподіваємося, що у Вас та Ваших рідних усе добре, наскільки це можливо. Нагадуємо, що конкурс триває до 31 жовтня, отже залишається ще тиждень. З початку конкурсу в українській частині конкурсу завантажено понад 23000 фото, взяли участь більше ніж 160 конкурсантів та конкурсанток, а Україна зараз посідає четверте місце у міжнародній табличці за кількістю завантажень.
Попереду — останні вихідні жовтня, а отже й конкурсу. Можете переглянути свої фото- та відеоархіви, поширити інформацію про конкурс серед друзів та знайомих, а також сходити на фотопрогулянку і завантажити фото інтер'єрів пам'яток, адже світлини внутрішнього убранства пам'яток можна подавати без обмежень за датою створення. Також у нас тепер є веб-додаток для завантаження світлин, можете спробувать чи так зручніше брати участь: https://app.wikilovesmonuments.it
Приєднуйтеся!
Більше інформації про конкурс читайте тут – Оргкомітет «Вікі любить пам'ятки»
Ви отримали це повідомлення, оскільки Ви брали участь у фотоконкурсі «Вікі любить пам’ятки» чи допомагали (наприклад, редагували файли з конкурсу). Якщо Ви не хочете більше отримувати повідомлень про конкурс «Вікі любить пам'ятки», додайте свою сторінку користувача до відповідної категорії чи напишіть Оргкомітету. Дякуємо!
You have received this message, because you had uploaded pictures to one of the Wiki Loves Monuments in Ukraine editions or helped (for example, edited files from the contest). If you do not speak Ukrainian, but you are interested in the contest, you can check out our page in English here. If you do not want to receive messages related to Wiki Loves Monuments — add your user page to this category or write to the Organising team. Thank you!
Мирного неба!
З повагою, Анатолій (обг.) від імені Оргкомітету «Вікі любить пам'ятки» 19:05, 24 October 2025 (UTC)
Tech News: 2025-44
[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 Wikipedia iOS app has launched an A/B/C test of improvements made to the tabbed browsing feature for select regions and languages. The test, named “More dynamic tabs”, explores new tab experiences and includes “Did you know” and “Because you read” article recommendations. You can read more on the project page.
- Autoconfirmed users on small and medium wikis with the CampaignEvents extension can now use Event Registration without the Event Organizer right. This feature lets organizers enable registration, manage participants, and lets users register with one click instead of signing event pages.
View all 31 community-submitted tasks that were resolved last week. For example, the issue of flashing colors when holding or pressing the arrow keys under the dark mode settings in Vector 2022 has been fixed. [1]
Updates for technical contributors
- The CampaignEvents extension will be deployed to all remaining wikis during the week of 17 November 2025. The extension currently includes three features: Event Registration, Collaboration List, and Invitation List. For this rollout, Invitation List will not be enabled on Wikifunctions and MediaWiki unless requested by those communities. Visit the deployment page to learn more.
- The SwaggerUI-based REST sandbox experience is now live on all wiki projects. The sandbox can be accessed through the Special:RestSandbox page. Please report any issues to the MediaWiki Interfaces team board, or join the discussion on the project launch page. [2]
- Transform endpoints with a trailing slash path in the MediaWiki REST API are now marked as deprecated. They will remain functional during this time, but removal is expected by the end of January 2026. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found and tested using the REST Sandbox. See the MediaWiki REST API Deprecation page for more detailed information about the API deprecation policies and procedures.
- A dedicated changelog now exists for the MediaWiki REST API. The changelog provides an overview of these changes, making it easier for developers to keep track of improvements and iterations. Announcements will also continue to flow through the standard communication channels, including Tech News and email distribution lists, but can now be more easily referenced from a central location. If you have feedback about the style, structure, or content of this changelog, please join the discussion.
- Administrators can delete the tracking category which was previously added by the JsonConfig extension, as it is no longer used. See the categories linked from Q130635582. It is OK if there are still pages listed in the category as that is just a caching issue, and they will be automatically cleared out the next time each page is edited. [3]
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 19:27, 27 October 2025 (UTC)
Tech News: 2025-45
[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
- Administrators will now find that Special:MergeHistory is now significantly more flexible about what it can merge. It can now merge sections taken from the middle of the history of the source (rather than only the start) and insert revisions anywhere in the history of the destination page (rather than only the start). [4]
- For users with "Automatically subscribe to topics" enabled in their preferences, starting a new topic or adding a reply to an existing topic will now subscribe them to replies to that topic. Previously, this would only happen if the DiscussionTools "Add topic" or "Reply" widgets were used. When DiscussionTools was originally launched existing accounts were not opted in to automatic topic subscriptions, so this change should primarily affect newer accounts and users who have deliberately changed their preferences since that time. [5]
- Scribunto modules can now be used to generate SVG images. This can be used to build charts, graphics and other visualizations dynamically through Lua, reducing the need to compose them externally and upload them as files. [6]
- Wikimedia sites now provide all anonymous users with the option to enable a dark mode color scheme, featuring light-colored text on a dark background. This enhancement aims to deliver a more enjoyable reading experience, especially in dimly lit environments. [7]
- Users with large watchlists have long faced timeouts when editing Special:EditWatchlist. The page now loads entries in smaller sections instead of all at once due to a paging update, allowing everyone to edit their watchlists smoothly. As part of the database update, sorting by expiry has been removed because it was over 100× slower than sorting by title. A community wish has been created to explore alternative ways to restore sort-by-expiry. If this feature is important to you, please support the wish! [8]
View all 31 community-submitted tasks that were resolved last week. For example, the fixing of the persisting highlighting when using VisualEditor find and replace during a query. [9]
Updates for technical contributors
- Since 2019 the Wikimedia URL Shortener at https://w.wiki is available for all Wikimedia wikis to create short links to articles, permalinks, diffs, etc. It is available in the sidebar as "Get shortened URL". There are 30 wikis that also install an older "ShortUrl" extension. The old extension will soon be removed. This means
/s/URLs will not be advertised under article titles via HTMLclass="title-shortlink". The/s/URLs will keep working. [10] - On Thursday, October 30, the MediaWiki Interfaces and SRE Service Operations teams began rerouting Action API traffic through a common API gateway. Individual wikis will be updated based on the standard release groups, with total traffic increased over time. This change is expected to be non-breaking and non-disruptive. If any issues are observed, please file a Phabricator ticket to the Service Ops team board.
- MediaWiki Train deployments will pause for the final two weeks of 2025: 22 December and 29 December. Backport windows will also pause between Monday, 22 December 2025 and Thursday, 2 January 2026. A backport window is a scheduled time to add things like bug fixes and configuration changes. There are seven deployment trains remaining for 2025. [11]
Detailed code updates later this week: MediaWiki
In depth
- In 2025, the Wikimedia Foundation reported that AI systems and search engines increasingly use Wikipedia content without driving users to the site, contributing to an 8% drop in human pageviews compared to 2024. After detecting bots disguised as humans, Wikimedia updated its traffic data to reflect this shift. Read more about current user trends on Wikipedia in a Diff blog post.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 19:30, 3 November 2025 (UTC)
Information on temporary account IP viewer rights
[edit]Hello Aristeas,
On November 12, temporary accounts will be enabled on Commons. The IP of unregistered users will then be hidden for most users. You, as a patroller or license reviewer, are eligible to request the new temporary account IP viewer right, if you need it to continue fighting vandalism and abuse on Commons. If you want to request the right, please file the request here. Please be aware that you also have to accept the Wikimedia Access to Temporary Account IP Addresses Policy in your preferences. For more information about temporary accounts, look at the project page. MediaWiki message delivery (talk) 18:34, 7 November 2025 (UTC)
- Many thanks for the notice, GPSLeo! I have requested the specific right. – Aristeas (talk) 19:08, 7 November 2025 (UTC)
Temporary account IP viewer granted
[edit]

Hello, Aristeas. Per your request, your account has been granted temporary-account-viewer rights. You are now able to reveal the IP addresses of individuals using temporary accounts that are not visible to the general public. This is very sensitive information that is only to be used to aid in anti-abuse workflows. Please take a moment to review Commons:Temporary account IP viewer for more information on this user right. It is important to remember:
- You must not share IP address data with someone who does not have the same access permissions unless disclosure is permissible as per guidelines listed at Foundation:Policy:Wikimedia Access to Temporary Account IP Addresses Policy.
- Access must not be used for political control, to apply pressure on editors, or as a threat against another editor in a content dispute. There must be a valid reason to investigate a temporary user. Note that using multiple temporary accounts is not forbidden, so long as they are not used in violation of policies (for example, block or ban evasion).
It is also important to note that the following actions are logged for others to see:
- When a user accepts the preference that enables or disables IP reveal for their account.
- Revealing an IP address of a temporary account.
- Listing the temporary accounts that are associated with one or more IP addresses (using the CIDR notation format).
Remember, even if a user is violating policy, avoid revealing personal information if possible. Use temporary account usernames rather than disclosing IP addresses directly, or give information such as same network/not same network or similar. If you do not want the user right anymore then please ask me or another administrator and it will be removed for you. You may also voluntarily give up access at any time by visiting Special:Preferences. Happy editing! GPSLeo (talk) 19:42, 7 November 2025 (UTC)
- Thank you very much, GPSLeo! I have read the policy. In the next days I will study the details. In any case I will make use of this user right only if it is required in order to investigate likely cases of vandalism. Best, – Aristeas (talk) 20:37, 7 November 2025 (UTC)
- @GPSLeo kannst du mir die Rechte bitte auch geben. Viele Grüße Z thomas 21:14, 7 November 2025 (UTC)
- @Z thomas Mach ich, kannst du das dafür auch auf COM:RFR offizielle anfragen, damit es ordentlich dokumentiert ist. GPSLeo (talk) 08:21, 8 November 2025 (UTC)
- @GPSLeo danke. Hab ich sogar schon gemacht. Aber ich finde diese unter der Hand Taktik auf Aristeas' Seite viel cooler. Danke an Aristeas, dass ich deine Seite nutzen konnte :-) viele Grüße Z thomas 08:40, 8 November 2025 (UTC)
- @Z: Nichts zu danken ;–). Viel Erfolg und alles Gute, Roman / – Aristeas (talk) 11:04, 8 November 2025 (UTC)
- @GPSLeo danke. Hab ich sogar schon gemacht. Aber ich finde diese unter der Hand Taktik auf Aristeas' Seite viel cooler. Danke an Aristeas, dass ich deine Seite nutzen konnte :-) viele Grüße Z thomas 08:40, 8 November 2025 (UTC)
- @Z thomas Mach ich, kannst du das dafür auch auf COM:RFR offizielle anfragen, damit es ordentlich dokumentiert ist. GPSLeo (talk) 08:21, 8 November 2025 (UTC)
- @GPSLeo kannst du mir die Rechte bitte auch geben. Viele Grüße Z thomas 21:14, 7 November 2025 (UTC)
Hier noch ein simpler, aber ggf. wichtiger Hinweis für mich und etwaige Mitleser ;–). Zwischen all den Hinweisen, warum und wofür die neuen temporären Accounts gedacht sind und wie das Recht ‘Temporary account IP viewer’ genutzt werden darf, habe ich erst gar keine Beschreibung gefunden, wie die Namen der neuen temporären Accounts zu erkennen sind. Das finde ich aber wichtig zu wissen, damit sie uns sofort auffallen und wir sie ggf. näher unter Lupe nehmen. OK, wahrscheinlich war ich einfach blind, aber jetzt habe ich den Hinweis doch gefunden:
- Temporary account names follow the pattern:
~2025-12345-6(a tilde, the year of creation, dash, an auto-generated serial number broken up with hyphens grouping 5 digits at a time).
Hier wäre ein Beispiel für einen solchen temporären Account. Sie werden max. 90 Tage lang verwendet. – Aristeas (talk) 19:37, 16 November 2025 (UTC)
- @W.carter: The hint above may also be interesting for you (if you did not already know this). So if we spot any edits to FPs or FP gallery pages made by users with names following this pattern, we know that these are temporary accounts and that we should (if possible) take a closer look at these edits (anonymous users are know for a especially large amount of nonsense edits/vandalism). I have already teached my program fpgallerist to look out for such edits, too. Now my program also recognizes the new temporary accounts when it checks FPs and FP galleries for potentially problematic edits. (Hint for admins and privacy advocates: fpgallerist does NOT access the IP address of these accounts, it is intentionally not even able to do that, it just checks for potentially problematic edits and lists them so that I can check them more easily.) Best, – Aristeas (talk) 21:06, 16 November 2025 (UTC)
Tech News: 2025-46
[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
.jpg/250px-Talk_pages_default_look_(April_2023).jpg)
- Starting November 12, users will see a change in the appearance of talk pages on some Wikipedias. Almost all wikis have received this design change; English Wikipedia will get these changes later. You can read more on Diff. Users can opt out of these changes in their user preferences in "Show discussion activity". [12]
- MediaWiki can now display a page indicator automatically while a page is protected. This feature is disabled by default. It can be enabled by community request. [13]
- Using the "Show preview" or "Show changes" buttons in the wikitext editor will now carry over certain URL parameters like 'useskin', 'uselang' and 'section'. This update also fixes an issue where, if the browser crashed while previewing an edit to a single section, saving this edit could overwrite the entire page with just that section’s content. [14][15][16]
- Wikivoyage wikis can use colored map markers in the article text. The text of these markers will now be shown in contrasting black or white color, instead of always being white. Local workarounds for the problem can be removed. [17]
- The Activity tab in the Wikipedia Android app is now available for all users. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. [18]
- The Reader Growth team is launching an experiment called "Image browsing" to test how to make it easier for readers to browse and discover images on Wikipedia articles. This experiment, a mobile-only A/B test, will go live on English Wikipedia in the week of November 17 and will run for four weeks, affecting 0.05% of users on English wiki. The test launched on November 3 on Arabic, Chinese, French, Indonesian, and Vietnamese wikis, affecting up to 10% of users on those wikis. [19]
View all 27 community-submitted tasks that were resolved last week. For example the inability to lock accounts on mobile sites has been fixed. [20]
Updates for technical contributors
- Nominations are open on Wikitech for new Toolforge standards committee members. The committee oversees the Toolforge Right to fork policy and Abandoned tool policy among other duties. Nominations will remain open through 2025-11-28.
- The JWT issuer field in OAuth 2 access tokens for SUL wikis has been changed to
https://meta.wikimedia.org. Old access tokens will still work. [21] - The JWT subject field in OAuth 2 access tokens will soon change from
<user id>tomw:<identity type>:<user id>, where<identity type>is typicallyCentralAuth:(for SUL wikis) orlocal:<wiki id>(for other wikis). This is to avoid conflicts between different user ID types, and to make OAuth 2 access tokens and thesessionJwtcookie more similar. Old access tokens will still work. [22] - MediaWiki's block messages (blockedtext, blockedtext-partial, autoblockedtext, systemblockedtext, blockedtext-tempuser, autoblockedtext-tempuser) now support additional parameters indicating whether the user is blocked from editing their own user talk page
$9or emailing other users$10. [23] - A
REL1_45branch for MediaWiki core and each of the extensions and skins in Wikimedia git has been created. This is the first step in the release process for MediaWiki 1.45.0, scheduled for late November 2025. If you are working on a critical bug fix or working on a new feature, you may need to take note of this change. [24] - The process for generating CirrusSearch dumps has been updated due to slowing performance. If you encounter any issues migrating to the replacement dumps, please contact the Search Platform Team for support. [25][26]
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 20:35, 10 November 2025 (UTC)
St. Martin
[edit]Grüß Dich. Derzeit finden ja St.-Martins-Umzüge statt. Vielleicht kannst du, bei Gelegenheit, Bilder vor Ort erstellen. Siehe Category:St. Martin's Day in Baden-Württemberg. Eventuell diese Nachricht an befreundete Nutzer in weiterleiten. Viele Grüße -- Triple C 85 | User talk | 08:42, 11 November 2025 (UTC)
A barnstar for you! (2)
[edit]| The Original Barnstar | |
| Danke für die wertschätzende Art der Kontaktaufnahme, die mich bei meiner Tätigkeit als Hobbyfotograf für Wikipedia unterstützt. Dadurch ist es einfacher, an all das zu denken, was ich übersehe. Ich weiß nicht, ob Barnstars hier eigendwie Sinn ergeben, aber ich mach das jetzt mal einfach. Hobbyfotowiki (talk) 18:00, 16 November 2025 (UTC) |
- Vielen herzlichen Dank, Hobbyfotowiki! Ich fühle mich sehr geehrt :–). Ich melde mich (hoffentlich) in den nächsten Tagen nochmal mit ein paar weiteren Tips zum FP-Prozess usw. Herzliche Grüße und alles Gute, – Aristeas (talk) 20:57, 16 November 2025 (UTC)
Tech News: 2025-47
[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 experimenting with reading lists on mobile web, allowing logged-in readers with no edits to save private lists of articles for later. The experiment is running on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias since the week of 10 November, and will begin on English Wikipedia the week of 17 November.
- Users who can’t receive their email verification code during login can now get help by submitting a form on a new special page. This update is part of the Account Security initiative. If your account has an email address, please make sure you still have access to it. When logging in from a new device or location without 2FA, you may be asked to enter a 6-digit code sent by email to finish logging in. Learn more.
- One new wiki has been created: a Wikisource in Minangkabau (
s:min:) [27]
View all 23 community-submitted tasks that were resolved last week.
Updates for technical contributors
- As part of the Parser Unification project, the Content Transform Team rolled out Parsoid as the default parser to many low-traffic Wikipedias and is preparing the next step to high traffic ones. This message is an invitation for you to opt-in to Parsoid, as described in the Extension:ParserMigration documentation, and identify any issues you might encounter with your own workflow using bots, gadgets, or user scripts. Please, let us know through the "Report Visual Bug" link in the Tools sidebar or create a phab ticket and tag the Content Transform Team in Phabricator.
- Unsupported Tools: Several issues with Video2Commons have been fixed, including filename-related upload failures, black-video imports, and retry handling. AV1 support has also been added. Ongoing work focuses on backend stability, ffmpeg errors, subtitle imports, metadata handling, and playlist uploads. To track specific tasks, check the Phabricator board.
Detailed code updates later this week: MediaWiki
Meetings and events
- Save the date for the next Wikimedia Hackathon happening in Milan, Italy from May 1–3, 2026. Registration will open in January 2026. Scholarship applications are currently open, and will close on November 28, 2025. If you have any questions, please email hackathon@wikimedia.org.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 17:23, 17 November 2025 (UTC)
FP Promotion
[edit]|
The image File:Bad Wimpfen - LSG Altenberg-Mittelberg - Streuobstwiese mit Raureif.jpg, that you uploaded is now assessed as one of the finest pictures on Wikimedia Commons, the nomination is available at Commons:Featured picture candidates/File:Bad Wimpfen - LSG Altenberg-Mittelberg - Streuobstwiese mit Raureif.jpg. Thank you for your contribution. If you would like to nominate, please do so at this nomination page. |
/FPCBot (talk) 13:03, 19 November 2025 (UTC)
Massenbach vs. Massenbachhausen
[edit]Hallo @Aristeas Danke fürs nochmal rüberschauen. Auf der Karte (in OSM gesichtet) liegt die Kamera-Position ja wesentlich dichter an Massenbachhausen und habe daher vermutet, dass die Kategorisierung in Massenbach ein Versehen oder Typo war, wegen der ähnlichen Wortanfänge beider Orte, und habe deswegen nach Massenbachhausen geändert. Die Ortsgrenzen der beiden Dörfer konnte ich leider nicht so gut erkennen, nur dass beide im Gebiet von Schwaigern liegen. Aber da es ja dein Foto ist und du dich vor Ort vermutlich besser auskennst wo welcher Ort an- und aufhört, vertraue ich mal auf deine Einschätzung. :)
Apropos, ich habe den Vandalismus in der Datei von heute morgen reverted und den user Drexcreatur203 mal reportet.
Viele Grüße und schönes Wochenende! Nylki (talk) 10:08, 21 November 2025 (UTC)
- Jetzt hab ich doch nochmal aus Spaß in die offizellen Karten von BW angeschaut (Schwaigern, Massenbach, Massenbachhausen, leider muss man die Orte nochmal in der Seitenleiste beim Geoportal anklicken um die Grenzen zu sehen). Vermutlich wäre ein Einsortierung nach Schwaigern nach diesen Karten vom Geoportal BW am korrektesten, da dort die Kamera-Koordinaten weder in Massenbach noch Massenbachhausen liegen, sondern zur Ebene darüber gehören (soweit ich das sehe). Falls du das auch so siehst, überlass ich das dir, das ggf. nochmal anzupassen. Aber so wichtig ist das in diesem Fall wahrscheinlich auch nicht, ist ja doch alles sehr dicht bei einander. Nylki (talk) 10:53, 21 November 2025 (UTC)
- Hallo Nylki, vielen Dank für Deine Mühe und Recherche -- insbesondere natürlich für das Reverten des dreisten Vandalismus von Drexcreatur203!
- Das generelle Problem ist, dass diese Karten (nach BW-Sitte) die Grenzen von kleineren Ortsteilen/Teilorten meist nicht anzeigen bzw. nur, wenn diese einen Ortschaftsrat besitzen (oder so ähnlich; die genaue juristische Formulierung mag jemand anderes finden). Die Anzeige bei Massenbach stellt daher lediglich die Grenzen des Ortsetters dar, nicht das Gebiet des Stadtteils. Das ändert nichts daran, dass das Land zwischen dem Ortsetter von Massenbach und Massenbachhausen zum Stadtteil Massenbach gehört. Und selbst falls juristisch in diesem Fall der Stadtteil Massenbach gar kein Land mehr umfassen sollte (juristisch könnte es natürlich alles Mögliche geben, je nachdem, was 1971 vereinbart wurde, als Massenbach Stadtteil von Schwaigern wurde), ist Commons doch keine juristische Spitzfindigkeitendatenbank, sondern ein Medienarchiv, das benutzbar sein sollte. Die Grenze zwischen Schwaigern und Massenbachhausen ist klar und auf zahlreichen Karten ersichtlich, daher würde ich das Bild jedenfalls in keiner Weise bei Massenbachhausen einsortieren. Das Gemeindegebiet von Schwaigern wiederum ist nicht ganz winzig, sondern umfasst immerhin auch die Stadtteile Massenbach, Niederhofen und Stetten am Heuchelberg. Daher halte ich es sowohl sachlich für plausibel als auch für praktisch, das Bild in Category:Massenbach zu belassen. Es erscheint ja zusätzlich auch in Category:Fields in Schwaigern u.ä. Kategorien, sodass es auch auffindbar ist, wenn jemand es nicht unter Massenbach, sondern direkt unter Schwaigern sucht.
- Herzliche Grüße von – Aristeas (talk) 12:43, 21 November 2025 (UTC)
- Hallo @Aristeas, Danke für deine ausführliche Antwort. Ich bin mit dir nach dem Lesen d'accord; dann passt das so wie du es ursprünglich schon hattest! (habe noch den Herstellungsort in den structured data nachkorrigiert).
- Schade, dass die offiziellen Karten von BW da nicht nicht so genau sind.
- Viele Grüße und Danke für deine tollen Bilder! -- Nylki (talk) 14:11, 21 November 2025 (UTC)
- Vielen Dank Dir für Dein Verständnis und die netten Worte, Nylki! – Ah, Moment, ich habe rein zufällig doch noch etwas gefunden. Wenn wir Massenbach im Geoportal aufrufen und die Liste links eine Weile herunterscrollen, gibt es auch noch den Eintrag „Massenbach / Gemarkung (Schwaigern)“. Wenn Du diesen Eintrag anklickst, bekommen wir doch die Grenze der Landmasse angezeigt, die zu Massenbach zählt, und es zeigt sich, dass sowohl der Aufnahmestandort als auch das kleine Gehölz zur Gemarkung Massenbach zählt. Wir müssen uns also merken, dass das Geoportal zwischen dem Eintrag „Massenbach / Stadtteil (Schwaigern)“ und dem Eintrag „Massenbach / Gemarkung (Schwaigern)“ unterscheidet – sicher ist das bei vielen anderen Stadt/Ortsteilen ähnlich, und wir finden die Gemarkung = die zum Stadt/Ortsteil zählende Landmasse nicht beim Eintrag „Stadtteile“ sondern beim Eintrag „Gemarkung“. Diesen Unterscheid hatte ich beim Geoportal auch noch nicht verstanden. Also habe ich dank Deiner Nachfrage wieder etwas gelernt ;–), Nochmals herzliche Grüße, – Aristeas (talk) 15:16, 21 November 2025 (UTC)
- Oh ha, guter Fund! Nylki (talk) 16:36, 21 November 2025 (UTC)
- Vielen Dank Dir für Dein Verständnis und die netten Worte, Nylki! – Ah, Moment, ich habe rein zufällig doch noch etwas gefunden. Wenn wir Massenbach im Geoportal aufrufen und die Liste links eine Weile herunterscrollen, gibt es auch noch den Eintrag „Massenbach / Gemarkung (Schwaigern)“. Wenn Du diesen Eintrag anklickst, bekommen wir doch die Grenze der Landmasse angezeigt, die zu Massenbach zählt, und es zeigt sich, dass sowohl der Aufnahmestandort als auch das kleine Gehölz zur Gemarkung Massenbach zählt. Wir müssen uns also merken, dass das Geoportal zwischen dem Eintrag „Massenbach / Stadtteil (Schwaigern)“ und dem Eintrag „Massenbach / Gemarkung (Schwaigern)“ unterscheidet – sicher ist das bei vielen anderen Stadt/Ortsteilen ähnlich, und wir finden die Gemarkung = die zum Stadt/Ortsteil zählende Landmasse nicht beim Eintrag „Stadtteile“ sondern beim Eintrag „Gemarkung“. Diesen Unterscheid hatte ich beim Geoportal auch noch nicht verstanden. Also habe ich dank Deiner Nachfrage wieder etwas gelernt ;–), Nochmals herzliche Grüße, – Aristeas (talk) 15:16, 21 November 2025 (UTC)
Tech News: 2025-48
[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
- Last week, the Wikimedia Search Team recreated the "DWIM" (Do What I Mean) gadget functionality server-side, for Russian and Hebrew Wikipedias. This feature adds cross-keyboard suggestions to the standard search-box suggestions. For example, searching for cxfcnmt on Russian Wikipedia will now add suggestions for счастье ("happiness") that the user probably intended. They plan to enable this feature for other Russian and Hebrew wikis this week. [28]
- Later this week, users of the "Improved Syntax Highlighting" beta feature will have syntax highlighting available in DiscussionTools. This requires that the "Enable editing tools in source mode" preference be set. [29]
- Campaign events extension – the set of tools for coordinating events and other on-wiki collaborations has now been deployed to all Wikimedia wikis. A new feature known as Collaborative contribution to help organizers and participants see the impact of activities has also been added. Join the upcoming learning session to see the new feature in action and share your feedback.
View all 24 community-submitted tasks that were resolved last week. For example, the bug which stopped CodeReviewBot from working, has now been fixed. [30]
Updates for technical contributors
- Users of Wikimedia API can join a usability study to help validate the new design of Wikimedia REST API sandboxes. Interested participants should fill the recruitment survey. [31]
- The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support for
format=xml&xlst={stylesheet}will be removed from Wikimedia projects by the end of November, 2025. In addition, it will soon be disabled by default in MediaWiki release versions: v1.43 (LTS), v1.44, and v1.45. Support for XSLT stylesheets will be fully removed from MediaWiki v1.46 (expected to release between April and May 2026). [32] - The WDQS legacy endpoint (query-legacy-full.wikidata.org) will be decommissioned at the end of December 2025, and finally closed down on 7th January 2026. After this date, users should expect requests to query.wikidata.org that require the full graph to fail or return invalid results if they are not rewritten to use SPARQL federation. The team encourages users to ensure that tools and workflows use the supported WDQS endpoints (https://query.wikidata.org/ - Main graph or https://query-scholarly.wikidata.org/ - Scholarly graph). For support with migrating use cases, please review the Data Access and Request a Query pages for details and assistance on alternative access methods.
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.
