Video in nostr is a f*ckn mess right now. We have several server implementations that are not working properly or have size restrictions. Uploading errors are not handled or not explained to a user. We have specific video notes (that flare.pub/zap.stream use) which are not supported by the social apps.
Your best bet right now is to get the creator plan from nostr.build and upload there.
I’m currently working on an app to upload and manage your media on nostr and hope I can improve things a bit but it’s not something one app can solve alone.
You could link to cloudflare‘s IPFS gateway already. The issue with video is that no one can run a CDN with that kind of bandwidth for free.
Almost all video players need an HTTPs server somewhere.
It looks like nostr.build and files.v0l.io have issues with your video.
Try to go to "manage servers" and disable them, so that only nostrcheck.me remains.
@Kieran
Some apps allow the author to set a content warning. Some hashtags may also lead to the warning.
Unfortunately not all popular apps support it yet and the behaviour varies.
There are also user reports for offensive content. But I am not sure if / how they are used by apps.
It’s been in there a few weeks. Coming up… working on the publishing after upload. Then file meta (1063), video and audio events can created as well.
Also experimenting with nip96 support right now.
We will definitely needs some kind of sharding when the user number and the amount of data grows.
I'm wondering if partitioning by ID fragment is a good idea. If you read a list of events almost every event needs to be read from a different relay.
It might be better to optimize for reading multiple events of a particular author and by partitioning by pubkey instead.
For anyone looking for a comparison to TOR, as far as I understand it:
It’s comparable to the TOR hidden services that can be reached by onion addresses. Here we have the nostr npub to address a service.
Since both entry and exit node only connect to relays, they are the only part that needs to be publicly reachable. Services can run behind firewalls on machines that are not reachable from the outside.
But it’s not like TOR in term of being an anonymous browsing tool for any website. It’s (currently) only for exposing a single service in a censorship resistant way.
You need a mobile browser with a nostr signing extension that has your key. On Android Kiwi is a convenient choice, on iOS safari + Nostore extension ist the only option afaik.
Notes by florian | export