ok so the streaming server gets a json string {event: type, payload: ... }, decodes the json, makes the exact same json with the payload encoded a second time as a string

why in the fuck. garg i demand answers for those 25 minutes i lost

anyway my streaming server "works" (no auth yet) and uses like 7MB of ram with a few connections

@CobaltVelvet I'm betting there's an explanation that contains the word "Javascript"

@CobaltVelvet I never, ever know what it is you're working on. I imagine a firehose somewhere, and instead of water its just numbers, and you're furiously hammering on the nozzle.

@CobaltVelvet It implements some filtering for some types of streams based on that data

Did you re-implement it in Rust or what's up?

@gargron ye

it's still a bit bad and ugly but it's basically working and i expect to put it on github soon

@CobaltVelvet Can you merge it with tootsuite/ragequit? I'll pay you

@gargron oof it's very differently made. i started with that method but i switched to a much simpler/flatter one. i'm not sure which is better or worse though.

i suspect mine is slightly less scalable over a single process with many threads, but also lighter for small instances and with less dependencies, and maybe supporting permessage-deflate which i think actix doesn't yet)

@CobaltVelvet Hm. Okay. Maybe it still will be useful as an example for the current developer

Sign in to participate in the conversation

Octodon is a nice general purpose instance. more