I don't like having to lookup a configuration .json file first.
People that think subdomains are too precious can get fucked. Using the root path only is a great idea. Subdomains are free.
api_url seems over-specified, since it doesn't have to even be the same domain name!
delegated_to_url then seems weird. Why reinvent HTTP redirect? Or if you really have to do this, just use api_url with a different hostname and bingo! ... So it's really TWO different re-inventions of HTTP redirect
What is supported nips for? Isn't it just NIP-96? There are no other NIPs for a file server.
Complex plan structure, and then "content types" is outside of that structure, but other restrictions like max filesize are inside of it. Seems very poorly thought out.
I don't get the media transformation thing at all. If media needs "transforming" that should be a separate thing prior to uploading to a file server.
NIP-98 auth is ok though
upload response giving all the metadata doens't seem useful. Download should provide metadata, but it doesn't.
Delete supported, server must remember all the pubkeys that uploaded the file.

But Blossom has some of the same issues

No way to get metadata, except a small amount of it on a per-uploader basis (far too many files at once).
AUTH event doesn't seem to contain the same protections as NIP-98 does

We may do #731 instead. - I don't like having to lookup a configuration .json file first. - People that think subdomains are too precious can get fucked. Using the root path only is a great idea. Subdomains are free. - api_url seems over-specified, since it doesn't have to even be the same domain name! - delegated_to_url then seems weird. Why reinvent HTTP redirect? Or if you really have to do this, just use api_url with a different hostname and bingo! ... So it's really TWO different re-inventions of HTTP redirect - What is supported nips for? Isn't it just NIP-96? There are no other NIPs for a file server. - Complex plan structure, and then "content types" is outside of that structure, but other restrictions like max filesize are inside of it. Seems very poorly thought out. - I don't get the media transformation thing at all. If media needs "transforming" that should be a separate thing prior to uploading to a file server. - NIP-98 auth is ok though - upload response giving all the metadata doens't seem useful. Download should provide metadata, but it doesn't. - Delete supported, server must remember all the pubkeys that uploaded the file. But Blossom has some of the same issues - No way to get metadata, except a small amount of it on a per-uploader basis (far too many files at once). - AUTH event doesn't seem to contain the same protections as NIP-98 does

mikedilger commented

2024-11-20 11:03:20 +13:00

(Migrated from github.com)

I went forward with blossom so I'm closing this one.