‍fuchsiaaaaaaaaaaaaaaaaa @f0x@pixie.town

another fucking morning...

next I do probably want to add some disk caching too so it's not all memory based

and prometheus metrics

and url previews ofc

and another published package: https://www.npmjs.com/package/stream-copier

good news: I did not really know what I was doing!

but now it is done, another biiiiig refactor commit with the new streams architecture https://git.pixie.town/f0x/synapse-media-proxy/commit/091e9dc346a23abdab2a4a660857fee30530c4df

aaaaaaa

also I got myself into quite a pickle with 24 cans of Nightwatch because they're perfectly aligned 4x6 and now it'd be wrong to take one :|

I put a bunch of ice cubes in my glass

and forgot to add anything else

at least I have some ice water to drink (and the cubes are mostly there)

this sounds dangerously like I know what I'm doing, we'll see if my coding proves that wrong

love it when a plan comes together

I did the proper thing and looked at existing implementations! and there's a module to split a stream to multiple consumers (nice), but nothing that keeps a buffer to backfill late-joiners. This will integrate *perfectly* with my current architecture because I'm already saving the whole stream into a buffer anyways (for later cache serves)

so:
- first request comes in, upstream starts streaming to the first client
- second client requests that file while it's still streaming, it gets a new stream with the buffer up till now + then the new data
- upstream request finishes
- new clients get the whole cached buffer

fucked up that I can't listen to the new(ish) ZHU album

I guess this is the second yakshaving time where I really dive deep into the internals of a Node subsystem (last time it was the module system, resulting in https://www.npmjs.com/package/@require-transpile/core)

I think I can do a cool stream splitting thing with late-joins but it'll be a bit more complex (and I have a (short) meeting in 20 mins..)

in short: shit

ok subscribing to streams when they come available works, subscribing to an already existing stream doesn't because some of the data will already be read-out from it (and thus removed).
And seems having multiple subscribers to the same stream isn't ideal either as varying network speeds/stream consumption would give a similar issue, hmmm

nice nice

don't ask me why

ok nice nice time to get this implemented before next meeting at 12:10