You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(nip96): native HTTP media storage pipeline #719
Nostream relies heavily on fragmented, third-party media servers. Nostream currently acts purely as an event pipeline. Providing a native, integrated media server allows relay operators to offer a complete ecosystem to their users without relying on external services.
Proposed Solution
Build a NIP-96 compliant HTTP upload pipeline directly into Nostream.
Scope
Auth Integration: Will seamlessly integrate with Nostream's NIP-98 authentication middleware to verify POST signatures.
Storage Abstraction Layer: Will architect an interface with implementations for Local File System and AWS S3 / Cloudflare R2.
Ingestion Pipeline: Will use a stream-based parser to handle multipart form data uploads, generate SHA-256 hashes, and enforce mime-type and size limits.
Response Formatting: will return the standardized NIP-96 JSON response containing the download URL and metadata.
A new surface, not parity. The capture is an event pipeline and nothing more; this asks for a NIP-96 upload endpoint, a storage abstraction across local FS / S3 / R2, multipart streaming with SHA-256 and mime/size limits, and NIP-98 auth in front of it. None of that exists in the TypeScript relay to port, and NIP-96 is not one of the 25 NIPs the relay advertises at capture.
It also pulls in dependencies the rewrite deliberately does not have: object storage and a media-serving path. Landing it during the rewrite would put an S3 client and a media pipeline on the critical path of a relay that has never had either.
Left without a milestone (out of the rewrite set), and recorded in the "Deferred past cutover" section of estimates.md. If it is picked up later, it wants its own storage trait beside the event store rather than inside it.
Activity
chappie-daemon commentedon Oct 24, 2026
Decision (2026-10-24): post-cutover
A new surface, not parity. The capture is an event pipeline and nothing more; this asks for a NIP-96 upload endpoint, a storage abstraction across local FS / S3 / R2, multipart streaming with SHA-256 and mime/size limits, and NIP-98 auth in front of it. None of that exists in the TypeScript relay to port, and NIP-96 is not one of the 25 NIPs the relay advertises at capture.
It also pulls in dependencies the rewrite deliberately does not have: object storage and a media-serving path. Landing it during the rewrite would put an S3 client and a media pipeline on the critical path of a relay that has never had either.
Left without a milestone (out of the rewrite set), and recorded in the "Deferred past cutover" section of
estimates.md. If it is picked up later, it wants its own storage trait beside the event store rather than inside it.