That's a downside of Nostr's decentralized nature. Centralized platforms have solutions to this, but Nostr so far hasn't fixed this, the work is left to the end user. I've posted about it many times in the past ๐Ÿ˜‚ Support for video compression is included in some clients, Amethyst being one I use.
Ryan's avatar Ryan
Unlike centralized social media your videos aren't automatically optimized on Nostr. Here are some good tools to compress your videos for smaller size and better streaming before upload. "Make sure to make it web optimized and no more than 720p. Or even 480p is great for a long news like segments ๐Ÿถ๐Ÿพ๐Ÿซ‚๐Ÿซก๐Ÿ’œ" - @The Fishcake (nostr.build) ๐Ÿ”นAndroid Light Compressor enhanced by @โšก Dee Kay โšก๐Ÿ‡ธ๐Ÿ‡ช๐Ÿ‡ฌ๐Ÿ‡ง๐Ÿ‡จ๐Ÿ‡ฟ๐Ÿ‡ง๐Ÿ‡ท๐Ÿ‡ฆ๐Ÿ‡น https://github.com/davotoula/LightCompressor-enhanced Proton - Google Play Store https://play.google.com/store/apps/details?id=com.arthur.hritik.proton.video.compressor ๐Ÿ”นiOS @nostr.build Shack by @The Fishcake (nostr.build) https://testflight.apple.com/join/qgkAMPgU ๐Ÿ”นDesktop - available for Linux, Mac & Windows Handbrake https://handbrake.fr/ Handbrake looks complicated, but there are presets available. Under General, Fast 720p30 & Fast 480p30 will be good options. I would also enable the Web Optimized option for better streaming. FFmpeg https://ffmpeg.org/ If you are comfortable with the terminal FFmpeg is a best in class option. LLM's are useful to formulate your commands.
View quoted note →

Replies (2)

it's all part of the process of owning your own content. many people don't realize all of the tiny bells and whistles that go into these things though. they'd normally have their content managers or producers or social media teams doing these things for them. if we're trying to empower people, themselves, instead of corporations with these teams of people, then i think we can do better as an ecosystem and work on some of these services for people. i don't know how nostr.build would do it with blossom files. it would have to be uploaded first, then transcoded, and after the file is finally changed, then signed. that's not a good user experience. they could probably do this for the normal nostr.build uploaded files though since they're not signed.
Yeah I'm pretty sure it would require some work on the client end too. Depending on video size transcoding will take some time. Working that into the note signing flow would need feedback and the client end to be able to get the right file name in the note, etc.
โ†‘