#m3api — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #m3api, aggregated by home.social.
-
New m3api-oauth2 release! (m3api-oauth2 is still an m3api extension package to authenticate users using OAuth 2.)
This just declares compatibility with the newly released m3api-rest v0.2.0, nothing special :blobfoxhappy:
https://gitlab.wikimedia.org/repos/m3api/m3api-oauth2/-/releases/v1.0.5
-
New m3api-rest release! (m3api-rest is still an m3api extension package to use the MediaWiki REST API.)
THIS is what this has all been building up to! m3api-rest now supports the following:
• request methods: GET, POST, PUT, DELETE, PATCH
• request body content types: JSON, URLSearchParams, FormData
• response body content types: JSON, (plain) text, HTMLresulting in 17 instead of 4 exported functions, a 325% increase!! :D
https://gitlab.wikimedia.org/repos/m3api/m3api-rest/-/releases/v0.2.0
-
New m3api-oauth2 release! (m3api-oauth2 is an m3api extension package to authenticate users using OAuth 2.)
This likewise updates the library to work with latest m3api, and also introduces a new HTTP-level error handler, to handle the fact that Wikimedia infrastructure now responds differently to requests with expired access tokens, which broke our previous automatic refresh functionality 😔
https://gitlab.wikimedia.org/repos/m3api/m3api-oauth2/-/releases/v1.0.4
-
New m3api-rest release! (m3api-rest is an m3api extension package to use the MediaWiki REST API.)
From an external point of view, this is just a patch version bump to make the library compatible with the latest m3api. (Internally, this of course meant quite a few changes, as the m3api maintainer changed the whole network interface this library was using, that thoughtless prick.) The promised new features will come a bit later :blobfoxinnocentcute:
https://gitlab.wikimedia.org/repos/m3api/m3api-rest/-/releases/v0.1.1
-
New m3api release! (m3api is a JavaScript library to use the MediaWiki Action API.)
This version overhauls the internal network interface, which will unlock many new features in the m3api-rest extension package, and introduces a new internal option that will allow m3api-oauth2 to fix an issue with automatic retrying of requests with expired access tokens. (Stay tuned for new releases of those packages in the coming hours :blobfoxfloof:)
https://gitlab.wikimedia.org/repos/m3api/m3api/-/releases/v1.1.0
-
unfinished thought: it would be quite good to have something like the Toolforge Abandoned Tool policy (https://wikitech.wikimedia.org/wiki/Help:Toolforge/Abandoned_tool_policy) for non-tool Wikimedia code, such as libraries (e.g. #m3api) or applications (e.g. Pattypan?)
this could be a step towards “Off-the-shelf governance models for small FOSS projects” (@pintoch, https://antonin.delpeuch.eu/posts/off-the-shelf-governance-models-for-small-foss-projects/) – if a codebase opts into it (README.md?), there would be an established process for adopting it if the maintainer goes inactive