Ryō Igarashi (五十嵐 涼)

@blackspike Hello, thanks for reporting an issue. I'm still investigating it, but I suspect you are running it on a environment that doesn't have a native support for `FormData`, instead...

Closing as it doesn't seem to be a problem arising from Masto.js. Feel free to reopen if you think you still have a problem.

@AndreKoepke Thank you for sharing, it solved the issue in my case. I ended up thinking that the real issue here is Node.js module `form-data` does not meet with the...

@assaf I'd also like to move the event interfaces to Async Iterators. We've already had Async Iterators for pagination in our code base, so it'd be nice to integrate those...

@assaf > I don’t think it’s necessary to do both SSE and WS. It’s the same mechanism on the server, SSE just seems simpler to me. You're right but it'd...

@assaf Thank you for sharing! It’d help a lot to implement it. > `access_token` as a query parameter (This is totally off-topic but) Inherently HTTPS doesn’t encrypt request URLs, so...

Okay now I understand and agree with your proposal > HTTPS Ah... I've heard there are some drawbacks to using query parameters as a way of authorisation and previously I've...

@eramdam You would need to change tsconfig.json as follows since the sub-package is served by a feature called [package exports](https://nodejs.org/api/packages.html#conditional-exports) which was introduced in Node.js 16+. ```diff { "compilerOptions": {...

Hi @gmag11, thank you for sharing your tips. As of 5.0.0 (and 6.0.0 as well), we have dropped the support for Axios, replacing it with Node.js native Fetch API, so...

I believe this issue is fixed by #700. If you think you still have a problem, feel free to reopen it.