Show newer

wonder if this structure will work nicely, a local component that runs on the Synapse machine with filesystem and database access, and a remote component that caches files and handles user requests

Show thread

if you see [llf] in the name of a Leenode staffer, it stands for Live, Laugh, Freenode

caps 

@dumpsterqueer this time I started at VEGA Core lmao because someone linked a totally different youtube cooking video "for the vegas (vegetarians)"

got reminded of the DOOM ost

so that's what I'll be listening again

with the right amount of ‘nostalgia for things that never happened’ sprinkled on top

Show thread

in practice this means I really don't have enough time to do anything, but the time-distant things I am waiting for to change that aren't coming closer either

Show thread

days just fly by but on a larger timescale nothing is moving

@haskal so the pixie.town matrix server is hosted at my home, which is nice and all, but for media both uploading and downloading has to go through my rather limited VDSL bandwidth. Currently I have caching on the vps nginx proxy which helps a bit but only after a request has finished, so when a media link gets accessed the first few times they still all pull from my home simultaneously.
My media proxy will run on the vps and get all media requests proxied to it instead of Synapse, allowing it to handle both upload and download in an in-memory cache + filesystem cache on the fast network machine, while still forwarding requests to Synapse as well so the media proxy could be removed and redirected back to Synapse and still have all the media

ok lol my synapse-media-proxy project in progress is apparently the new code thing I brainstorm about in bed and under the shower

Show older
Pixietown

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