@Pigsonthewing it seems like both of the tools are currently working. Given that they was marked as broken at the same time I'm guessing it might have been a temporary issue with WMCS at the time.

I wouldn't expect the API to interact with actual redirects at all and if it's decided that the CORS-webserver option is better I wouldn't expect that either to effect anything other than the initial redirect, thus an user could still get a CORS error down the chain as intended by the downstream target(s).

I would somehow expect it to be the full URL, as it fits with the mental model of a URL shortener but in practice it probably do little to no difference.

@TheDJ sums up the situation well. Changing the way the encoding works at the moment would probably break more than it fixes.

A query like "action=query&list=shorturl&suurl=https://w.wiki/1" would however only return the URL behind the one given? From my point of view that would resolve the use case.

Would having the prefix-definations checking against an array with named keys before defaulting to the existing values be an acceptable interface?

I'm not entirely sure how to migrate this one as the jobs part was implemented by WMF staff. I'm not sure how much it's in use today but in the past various OSM tools relied on it so it might break things if it go away.

Thank you @dcaro, I will however migrate this tool off Toolforge and just put up a static "this tool has moved page" to catch people accessing the old urls.

Thank you @dcaro! I will give it a try over the weekend.

Jumping in to say that I want the tool to stay up past the 14th of December.

Jumping in to say that I want the tool to stay up past the 14th of December.

Jumping in to say that I want the tool to stay up past the 14th of December.

Jumping in to say that I want the tool to stay up past the 14th of December.

Incase someone else comes looking here, the ontology source can be found here: https://gerrit.wikimedia.org/g/mediawiki/extensions/Wikibase/+/4d3950fc2dd8c618b238d50f5f74123e9cc053a5/docs/ontology.owl

If it is in the document served by WikibaseManifest, then as a tool author I have the same problem as currently: if I wanted to make sure that all of my tool's configuration can be derived from the contents of the WikibaseManifest, then whenever I need to introduce a configuration parameter to implement a new feature in my tool, I first need to submit a patch to WikibaseManifest for it to expose this information (be it namespaced or not), get it merged, get a new version of the extension be released and deployed on the wikis I want to interact with.

So, even if we are assuming that the WikibaseManifest extension serves its information by following some particular ontology, the tool-specific information will not be available there. That means we cannot make it possible to just set up a Wikibase instance in OpenRefine just by providing the URL of the Wikibase instance and letting OpenRefine discover the configuration there. Or how would OpenRefine discover this additional information it requires?

I'm interested in working on this across OpenRefine, the WikibaseManifest extension and "TIB's" reconciliation service but I wonder if this work wouldn't benefit from being migrated to a proper vocabulary for describing APIs and knowledge graphs. Like Hydra and DCAT or schema.org instead of relying on a JSON file with more or less tool specific fields. It would have a lot of benefits like interoperability and extensibility, so one could for example have an Wikibase manifest describing multiple reconciliation services, or describing any API with an OpenAPI spec, or a W3C URI, etc. We could then just describe the reconciliation and for things like the template for edit summaries one could just use a custom property?

Not 100% sure it's Podman's fault but on Fedora(where the default docker package now being podman) mw docker mediawiki create fails with:

Hey, @Abbe98. Charlie justified the changes done to the original ticket description in the following comments: https://phabricator.wikimedia.org/T296135#7548801, https://phabricator.wikimedia.org/T296135#7549054

I'm not sure what happened here, the original description is gone and the solution isn't even related.

Will there be any attempt at migrating tools automatically?

@Aklapper as far as I know this is still blocked by T187582. No sign of your email btw.

Lite off-topic men vet någon vilken del av BBR som ingår i WLM? Bara byggnadsminnen eller allt?

@Susannaanas the Wikidata Image Positions tool supports "named place on map"!
https://wd-image-positions.toolforge.org/file/Map_India_and_Pakistan_1-250,000_Tile_NF_45-4_Faridpur.jpg

@Lucas_Werkmeister_WMDE did you find a good solution?

This currently makes it hard to migrate various tooling to SDC as one can not reliably expect media uploaded with Upload Wizard to have basic SDC-data.

Is there any public documentation regarding the selection of the statuspage.io service and which users this is supposed to serve?

Pattypan version 22.02 is now available.

Pattypan version 22.02 is now available. Pattypan now does not need OpenJFX to be installed and it supports Java 11+.

Pattypan version 22.02 is now available.

I have implemented it on the Kulturlämningar one on FornPunkt.se (example), and will do the same on Kyrksök.se before writing something about it on my blog. Let's see then if WMSE would be interested in doing a version of such a post on the wikimedia.se blog?

@Alicia_Fagerving_WMSE below are the two additional campaign configurations:

Considering that FastAPI, Django, and several other prominent Python frameworks support(and sometimes require) ASGI servers this would be great. The current alternative is Cloud VPS in case one wants to stay on WMFs cloud services.

Note that's experimental so start small :-)

Those coordinates are indeed just the center of the map which is in many cases useful as not all maps show coordinates in the title nor a single point, however, they are just confusing when used in <maplink> as per the example.

Do you (or another pattypan developer) subscribe to the mediawiki-api-announce mailing list? Or Tech News? What "normal channels" are you typically following?

These tools are all affected by T280806, and the outreach seems to have targeted bots and user scripts. I personally never caught any of the outreach through the normal channels as the framing has been "these things we deprecated back in 2014"(although these API calls have been widely used after the 2014 change) nor have any "warnings" reached me even though Pattypan is one of the most popular batch upload tools to Commons used by many chapters and GLAMs.

See also T293543.

The issue appears to have been resolved on Bing's end following the online coverage.

Note that for some users(like myself) an instruction on how to set up Curious Facts locally might be sufficient.

ResourceSync is indeed a protocol for informing other databases about one's contents or changes(similar scope as OAI-PMH) and as far as I know, it hasn't had many implementations.

Details are now available at https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/Data_Challenge

That was a very fun challenge to participate in and the format or just a part of it could as @Fuzheado say be an opportunity for engagement. I'm happy to volunteer(together with others) to make this happen.

From my perspective, there could be more than one alt-text per image and language in the SDC data. It would then be up to consumers to select which alt-text they would like to use.

@ChristianFerrer could you exemplify what functionality other tooling is missing for your particular use-case? Sometimes it's a matter of lacking documentation, for example, Pattypan can upload files from URLs but few people know about that capability.

There is now a property proposal: https://www.wikidata.org/wiki/Wikidata:Property_proposal/alt_text#alt_text

The template documentation has now been updated.
https://commons.wikimedia.org/w/index.php?title=Template:Fornminne/doc&oldid=460069658

Thanks @Lokal_Profil!

Looks good to me!

Nowadays other license options are hidden in UploadWizard unless one clicks the small link at the bottom of the form, so is this still a concern?

Actually following this someone will need to update the Campaign. So the UUID is presented as an alternative input.

Aren't the referenced patch blocking access to all services on maps.wikimedia.org and not only osm-intl? This issue and the deprecation message sent to maps-l only addresses maps.wikimedia.org/osm-intl/.

@Eric_Luth_WMSE yes per my comment in T260971. I do however not have the rights on commons to make or test the fix. Also I think some documentation might still need an update if implemented.

Yes it's broken. There is at least a "this is how a solution could look like" suggestion from me over at https://commons.wikimedia.org/wiki/Template_talk:Fornminne.

Workflow between Wikimaps Warper and the Map template. The Map template has a value for the warp status of the image in Wikimaps Warper. Warper writes to the Map template the changed value when it alters the map image.

Confirming it works and resolves my particular issue. Thank you @zhuyifei1999!

@Xqt when pwb is installed with "pip install pywikibot" I get a more recent version. Is the PAWS pwb actually up to date? To me it looks like the docker file were initiated with the stable branch but might have gotten out of date.

Closing as it's deployed and confirmed.

Worth noting is that this would make the template usages that pull data from Wikidata incompatible with many of the map tools including Wikimaps Warper.

@brion worked on glTF support a while ago. Looks to me like it got quite far, maybe possible to rebase it and take a stab at it.

In T246901#5965504, @Mrjohncummings wrote:

In T246901#5965272, @Ainali wrote:

In T246901#5965141, @Abbe98 wrote:

Could a solution similar to the one for MP3 files make sense? It would allow GLAMs to share vetted 3D content while still lock abusers out.

(To upload a MP3 file to Commons you need a specific user right.)

I think definitely this should be brought up as a possible solution for 3. in a community discussion. It essentially removes the burden from the sysops by only assigning the rights to users in good standing.

I also recall another more technical but yet similar reason, and that is that some 3D-formats allows for scripts also (which could possibly have malicious purposes). But I guess that is easier in a way by just saying that we will not support them at all (yet).

Does anyone know how or where the MP3 discussions happened?

Could a solution similar to the one for MP3 files make sense? It would allow GLAMs to share vetted 3D content while still lock abusers out.

There have been previous discussions on the subject of sanitation of 3D formats over at T131723.