> be me
> implement blossom protocol to the letter of the specs
> watch the error logs
> see many non-compliant requests
> think “watch doing bro?”
> remember that client devs don’t read the specs
> silently correct some errors on their behalf
> get beer and cry inside about wasting your time reading and trying to understand the specs
> move on with life
> be me reading some of the new and updated nips
> be like tephen, waste time reading NIPs that nobody read
> try to implement something that will not work with other implementations because nobody reads NIPs
> give up and go with beer instead or playing CoD
😂😂😂
It's not you, it's the docs.
> be me
> read badly written docs, that can’t maintain internal consistency on their own
> point out all the errors to the author
> get ignored for weeks
> say “fuck it” not wasting time again
> be happy with life
What type of requests or errors made you cry? I don't run a public blossom server so I have no insights into how clients are using it
Some are authentication headers (missing some structure, no expire tag, wrong signature), some are simple headers when mirroring (no size, or content type, or hash mismatch), some upload with wrong content type or generic one, and so on and so forth 😂
oh yeah... http metadata, its annoying how every client / http implementation includes different defaults. the browser will automatically include a lot of extra headers where as curl wont add anything
It might be worth being more strict on things like bad auth headers or missing content-length header since that "might" help the clients start to implement those things
itz nostr ice age 🐻❄️
