databases scary...

nice, I have basic file upload to the same memory cache as other served/proxied files working now :)

(configurable) max filesize implemented

Remote media download just works (tm) too, very easy to get the remote homeserver base url properly with https://www.npmjs.com/package/@modular-matrix/autodiscover-client-configuration

now working on access token validation for upload, which will need some work on the <local> server bit too, accessing the synapse db for things.
But this standin works, much secure such wow :P

- proper database access token validation
- saving uploaded files to <local> server disk

and initial commit published!
https://git.pixie.town/f0x/synapse-media-proxy

added progress explanation so far to readme as well

did a bunch of code cleanup and refactoring, tomorrow hoping to get started on thumbnailing, and url previews after that, which would finish the spec compliance for the media repo :)

nice nice nice file uploads work very well now, properly stored where Synapse would normally expect them too, and a listing in the database

now to limit the in-memory cache on <remote> and check up the federation spec, and then /upload and /download are fully implemented

oh yeah and also verifying the symbols in the requested mxc for 'security reasons' lol

oh and removing that lol

I love how the server-server spec for the media repo is "yeah just call their client-server endpoint" which is also how i implemented it already

ah fuck i reallly stumbled into a bad wormhole doing punycode domain testing, seems neither Synapse, Conduit nor matrix-media-repo can fetch media from those properly (and I can :3)

when the punycode is in the url literally like mxc://xn--puny--59d2hgc.dev.cthu.lu/testmedia, Synapse still fails, but Conduit and matrix-media-repo do fetch it correctly.
None of them do url decoding of the mxc right however..

time to write a nice memory cache

nevermind i can't be bothered anymore, I'll just make it remove the oldest entry...

the most basic of caches, it's a Map with an array tracking access order, removing the oldest accessed item from the map when it's about to get bigger than maxEntries

hmm debug() logging says trans rights? and the Validator says you're valid too!

:O I think I implemented the whole https://spec.matrix.org/unstable/server-server-api/#server-discovery Matrix server discovery flow!!! It's rather complex, with .well-knowns and SRV records and combinations of those.
Also nice that I could fork of the client-spec counterpart already made by someone else :) https://www.npmjs.com/package/@modular-matrix/autodiscover-client-configuration

@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

@haskal tl;dr it make cat pic go fast

@f0x Your database doesn’t want to hurt you. It’ll only bite if it thinks you’re threatening it or its cluster

@vy good to know :3

@f0x hell yeah f0x that's really cool!