Assaf Arkin
Assaf Arkin
Yes, you cannot run Zombie on older versions of Node
Yes, please send a path
Look at CPU utilization, if it jumps to 100% and stays there, that would explain why everything times out. That's usually a sign of a memory leak.
Node has a memory limit of 1GB (see https://github.com/joyent/node/wiki/FAQ).
I can't think of anything other than a memory leak exhibiting "time bomb" behavior.
Have a look at resources: http://zombie.js.org/#resources
Maybe this is a good opportunity to rework the streaming API to be an async iterator? I can imagine something like: ``` for await (const status of masto.streaming.public) { ......
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. I generally avoid `EventSource` — it...
This is the code I use for reading the public timeline: https://gist.github.com/assaf/e76a85e1cf434b61e02079335b98b04f > This sounds critical because the doc says streaming home timelines notifications requires the `Authorization` header. So says...
> I thought it’s worth considering simply throwing an error in event of a connection drop and delegating the catch-ups to the users, That's what I'm proposing, and how the...