it's not a nostr issue, this is a nostr.build issue. if you read what i said, you would see that i said two different times that this is something that nostr.build should look into adding for users. i agree that nostr and adjacent services can do a lot to help user experiences.

It is Nostr issue, yes. We are constrained by the sha256 requirements for uploaded content. This means that once you upload something, we cannot change a single bit of that file. Handbrake is a good software that will allow you to produce shareable media.

Yes. Get out of the weeds and into your customer's shoes. Never not going to point to JTBD. https://jobs-to-be-done.com/ View quoted note →

Personally I don't think nostr.build should be on the hook for media compression. But putting the creator on the hook isn't great either because they don't usually know anything about video formats. A separate caching and compression service is probably the play. Some kind of paid service that clients look to for optimized media. Then the viewer is on the hook, voluntarily employing a middleman to compress, store, and serve content from other providers.