Show newer

hey im @myconidiosyncrasy@efdn.club now. i manually refollowed ppl but my internet kept blinking out and which caused me to start openly weeping halfway thru and just try to follow ppl based on memory instead of moving through my follow list anyway if i missed you that's why it's not cause i hate you

if u can't follow me on my efdn account; freak.garden goes down monday (rest in power ✌️) so if u wanna stay in touch dm me for my discord before then. also still got @myconidiosyncrasy@redroo.ml in case of emergencies

#Tusky 15.1 is out! It is the same as Tusky 15.0, except it doesn't crash when captioning images.
@Tusky

unnecessarily early meeting done, might just go back to bed tbh fuck this

Show thread

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

Show thread

If anyone has leads on software engineering jobs in the Seattle area, I’d love to hear about ’em :heart_cybre:

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 git.pixie.town/f0x/synapse-med

Show thread

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 :|

Show thread

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

Show thread

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

Show thread

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 npmjs.com/package/@require-tra)

Show thread

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..)

Show thread

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

Show thread
Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.