The mind blowing part here is not my unix tool, it is showing that nostr is a practical decentralized alternative to Usenet NZBs (torrents are a different thing)
- Blossom servers do not need to store a whole large video file
- Blossom servers do not need to stream an entire large file
- Blossom operators have plausible deniability in terms of content as the segments are encrypted (and they may not have all) and they don't control the key
- Video clients now have mutiple failovers if a segment is stored in multiple servers
- There are bandwidth savings if the video is not watched entirely
- Content creators can exchange the AES key against a zap
Youtube, here we come.
Awesome
nostr:nprofile1qqs0dqlgwq6l0t20gnstnr8mm9fhu9j9t2fv6wxwl3xtx8dh24l4auspz4mhxue69uhkzat5dqhxummnw3erztnrdaksz9nhwden5te0d4kx26m49eex2ctv0yhxcmmv9uq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7dj6rpa give this project some credits, that search would be much better with Vertex (like it is on npub.world)
nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhkcmmrdd3x77pwve5kzar2v9nzucm0d5hszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tc4rdlnm can nak event generate an unsigned event? Would be useful
Developers, you soon will be able to sign your apps with keys on your browser extension.
Works for any other event too!
Demo:
https://cdn.satellite.earth/c50fa53cebd193c9a83e71245923179ad152be730d2a4837d5315399e43cecf0.mp4
Repo:
Sign any nostr event from the command line with a NIP-07 browser extension. Works great with nak
Trying out NIP07 signing from the command line
It's a POC so don't take too seriously.
But having a the key separate from the content gives Blossom operators plausible deniability which is massive.
Agents are good at creating small, very focused, composable Unix programs
I just built a tool.
Video on-demand from encrypted chunks on multiple Blossom servers 🤯
If you have (or can install) nak, nodejs, ffmpeg can you check it works for you?
nak req --id ec1688e87843e8774d1813c371fe65af890be090bdb831f03ceefdd2144ad679 wss://relay.damus.io | npx --yes github:franzaps/n2m3u8 | ffmpeg -f hls -allowed_extensions ALL -protocol_whitelist file,http,https,tcp,tls,crypto,fd -i - -f mpegts - | mpv -
This:
- Fetches a nostr event with hashes of video chunks
- Input into my tool that finds the working chunks in Blossom servers and outputs a HLS playlist
- Input to ffmpeg that decrypts and decodes the stream
- Input to video player. (Replace mpv with vlc or other video player, can also save to a video file)
Volume UP!
#asknostr #blossom #devstr
I need to check, but a lot of developers unfortunately modify releases after the fact. It's a possibility and need to consider how to handle that
Ah, I didn’t realize that (either of those things).
nostr:npub1kpt95rv4q3mcz8e4lamwtxq7men6jprf49l7asfac9lnv2gda0lqdknhmz do you want a competitor to offer personalized PageRank via WoT DVM? The point would be to demonstrate interoperability, which I think is important.
Or is the dvm spec gonna die on the vine? I’ve only partly been listening to the dvm debate. Most of my attention has been focused on trying to optimize the sync pipeline between strfry and neo4j.
Why don't you just do it? DVMs are pretty simple to implement.
I want all the benefits of the internet but with less screens and EMF
Running versionCode 235, is that the latest?
I only saw the first screen to log in. Now when I open the app I'm stuck in this loop, whether I accept or reject.
Try starting from scratch, removing the app from Amber. And maybe try rejecting signing kind 10000300 to see what happens.
Hey Marko! I am not trying to sign anything.
As soon as I log in with Amber I am prompted to sign that random event. (Which I think is not good, I should not be signing if I didn't perform any action but lets put that aside)
Maybe you can't reproduce because you granted Amber access to always sign that event kind?