Ah, but you are already using nostr.build without realizing it. 😉

Your last post with a video on it was uploaded to nostr.build via whatever client you used:

nostr:nevent1qvzqqqqqqypzqj3s2uktul2tky0h6fytpf3nnj6zm7pkexftvmv3l4zkwwqhdpwmqqsrcs09thvyhpezcvgp0vz9ls6ssgzsgqnjddpm8gx2365xm6mvwrspa2p8q

Examining the text-only version of this note revealed this:

Reply to this note

Please Login to reply.

Discussion

Remember, clients are just glorified front-ends displaying data that is stored somewhere else entirely. Notes are stored on relays, but media such as photos and videos needs to be stored somewhere too. The client itself doesn't store it. They rely on media hosting services like nostr.build to host your media.

Nostr.build is the most common one, because it has been around the longest, but there are others. Additionally, Blossom servers are becoming a more and more popular way to host media, as it helps make media storage more decentralized.

I run my own Blossom server, for instance. Which means I am hosting my own photos and screenshots. But, if my server goes down, that media won't be accessible either. So there are tradeoffs.

Then again. On Blossom, media is content addressable, so if I have my uploads mirrored to other Blossom servers, clients can fetch them from there, even though my server is down.

Okay, well if I can't upload videos directly to clients from my hard drive, I guess I would need the most simple, user-friendly solution, being that I have very little tech skills as well as very little time, energy, and resources, personally.