I still find it incredible there are grants at all for nostr. very non-standard for oss.
though it’s a shame they’re going to dime a dozen, proof of concept webapps. your work tends to focus on the harder problems and I appreciate that.
best of luck on your journey.
I have like a solid 8 hours of mandatory training shit to complete before next month. I figure if I keep avoiding it until the last minute I can maximize the pain 😐
clients issue an ever growing number of concurrent requests with each new feature
relays increasingly rate limit concurrent requests
clients swallow the notice and fail in weird ways
ux deteriorates
gm
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.
Notes by ben | export