developers: disable javascript execution by default in your web browser. start building your website with these constraints. progressively add interactivity if javascript is enabled.
does zap.stream store the streamed content for future playback? if yes can you disable that? I’ve tried to find some kind of FAQ a few times about how it works.
so it sounds like if you use the basic plan you can stream video and not have it persisted?
I’m interested in streaming applications but don’t want the stream recorded. (obviously a user could manually record the stream)
the distributed systems I’ve worked on outside of nostr typically offload the large data into an external store and plug a reference id into the event. the downstream consumers either find the data embedded in the event or an id to resolve it externally.
yo @petermccormack you’re a great interviewer and I hope you’ll reconsider naming your new podcast anything other than “mr obnoxious”.
I’ve actively avoided the youtube recommendations for “mr obnoxious” for at least a week. I just now realized that was your show.
it’s a bad name mate. you’re not obnoxious. call it “the peter mccormack show”. or something else. anything else.
let me know if you run into any issues, I’ve been connecting to nostr through my instance exclusively for many months. there are a few improvements I plan to make soon ™️:
- support sqlite instead of only lmdb for storing notes. the latter can be annoying as it may require c libs not on openbsd
- configuration options to only store specific kinds
- support proxying AUTH from upstream relays
Notes by ben | export