[02:28:02] lucaswerkmeister not sure if you're there (most likely not), but I believe Telegram keeps the message history, anyway if someone can pass the note along to them… [02:28:02] I did a lot of what I wanted to do with m3api and m3api-oauth. In fact, you can find TypeScript versions of the two (and m3api-rest) in https://www.npmjs.com/package/@gouvernathor/m3api and https://www.npmjs.com/package/@gouvernathor/m3api-oauth [02:28:45] let me know if there's any licensing issue with it, and of course feel free to take it all back into your version of the code. [02:29:43] For your consideration, here is a problem I ran into while making my non-confidential oauth app that wasn't addressed in the example : https://codeberg.org/Gouvernathor/ParliamentDiagram-Angular/issues/2 [02:30:24] In any case I don't plan on doing anything with the rewritten versions of m3api except using them in my web app [12:13:21] Gouvernathor: I wish you’d asked me before publishing new m3api packages on npm… :/ [12:13:43] I’m still waiting for a reply at https://phabricator.wikimedia.org/T429845 / https://gitlab.wikimedia.org/repos/m3api/m3api/-/merge_requests/1 btw, that’s why I haven’t done anything else with m3api (or extension package) types yet [12:14:00] oh, I don't see notifications on those [12:15:03] (I thought that might be the case on Phabricator, that’s why I decided to also post a comment on the MR) [12:16:03] yeah, I got neither of those [12:17:11] I did some other changes to my version of the code (the first that come to mind are a different way of managing the mixin and a new getOptions method in m3api, and a method to reset the code validator on oauth2) [12:17:49] also I completely changed the oauth2 interface to use a subclass of Session rather than functions, that played better with typescript (and I find it personally easier to use) [12:20:09] now I don't know how I can use those in my web app project without publishing them on npm (under my own username fork, not as the global m3api package), so it's a bit necessary for me [12:20:42] and I thought it was ok due to the free license [12:25:12] I mean, it’s legally okay, sure, but socially I’m not thrilled about the circumstances [12:25:22] if you need the code for your web app project, you could just include it in that project [12:26:30] (also I’m guessing that a Session subclass works well enough for you if you’re only porting the browser version, whereas m3api has multiple exported classes for Node and browser, and if you want subclasses of each of those for oauth2, and then perhaps more subclasses for m3api-rest and m3api-query etc., that starts to explode pretty quickly) [12:27:01] anyway I replied on the codeberg issue, I’m curious what error you’re referring to [12:31:43] for the session subclass : if you have my mechanism of switching between importing browser.js or node.js as m3api depending on the environment, then the OAuthSession subclasses the correct class automatically :) [12:40:40] I gave more details on codeberg