doesn't let you down

Censorship-resistant video sharing 🤯

👀

Exactly

Epic Rick Roll. Bravo, sir.

Top 😍

I don't get it: why encrypt the segments when you put the AES key on the nostr event?

Earlier this year, I fell victim to a devastating cryptocurrency scam that cost me $79,000 worth of Dogecoin (DOGE). I met a scammer through a Telegram investment group—a woman named “Clara” who posed as an experienced crypto broker. She shared impressive-looking client testimonials and promised a 35% return in just seven days. Her website looked professional, and despite my initial doubts, I eventually transferred 500,000 DOGE, worth about $79,000 at the time. For the first week, everything looked fine—the trading platform showed my balance growing steadily. But when I tried to withdraw my funds, I was told I needed to pay a $12,000 “withdrawal fee.” Clara reassured me this was standard and fully refundable, so I paid it. Unfortunately, that was just the beginning. More unexpected charges followed: a tax clearance fee, a network fee, a security deposit. Before I knew it, I had lost an additional $8,000. I was crushed—emotionally and financially. My savings were gone, and I blamed myself for ignoring the red flags. A friend eventually suggested I reach out to JBEE SPY TEAM RECOVERY, a company known for helping scam victims recover stolen cryptocurrency. Although I was skeptical, I was also desperate. I contacted them and provided every detail I could: wallet addresses, transaction history, chat logs—everything. Their team got to work right away. Using advanced blockchain tracking techniques, they traced the stolen DOGE, identified the scammer’s wallet, and worked with relevant authorities to freeze the funds before they were moved any further. Throughout the process, they kept me informed and reassured. After days of relentles s effort, JBEE SYP TEAM RECOVERY successfully recovered the majority of my stolen Dogecoin. Their professionalism, expertise, and transparency turned what felt like a hopeless situation into a story of redemption. If you’ve been a victim of crypto fraud, I highly recommend contacting them: Email conleyjbeespy606@gmail.com Telegram +44 7456 058620 you can also contact on instagram

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.

Gotcha

/cc @Jeroen ✅ @Constant

And I built this on top of it:

Oooh

Bookmarked thanks!

GD! Real time video from blossom servers already works?! Nostr development is really accelerating. I feel like we're getting close to the next killer app/onboarding phase View quoted note →

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.

Bookmarked. Will test later

👀

Very smart.

nice idea, works perfectly!

cool, m3u8 in a nostr event?

buen trabajo hermano!

So this uses the DRM AES encryption feature of HLS? This might work with hls.js in the browser too.

Love it, really well done 👏

Neat!

Awesome!!!

Yeah, we were talking about this a while back, when we started splitting up and indexing publications that contain non-text data, but I don't know if the plausible deniability thing actually works in a court of law because everyone low-key knows you've implemented it to help traffic kiddie porn.

I didn't even realize that nobody was doing this, already. Sort of funny. We do this with PDFs and stuff, too. Break it up into a stream, including the pictures and videos and games (people put computer games into PDFs because of course they do). But the whole thing makes me nervous, so we only store Asciidoc and export the embedded media to a media server, and call it from there. We don't work with anything encypted, but you do you. The police know where we live. LOL

Breaking it down into a stream also means you can set anchors into the stream, and refer to those anchors in a highlight, which is seriously awesome.

Have you seen this?

GitHub

NIP-5E: Nostr Live Streams by v0l · Pull Request #1790 · nostr-protocol/nips

Distribute live content via nostr and blossom! Read Original Gist Idea

What a way to Rick roll everyone 😂

I have not. Thanks!

@florian you were aware of this one?

Nope, doesn't surprise me though, that @Kieran is way ahead of everyone 😂

Putting each segment into it's own NOSTR event makes a lot of sense for live streaming but for videos that would be an unnecessary overhead. There is also a chunked blobs BUD10 draft

GitHub

blossom/buds/10.md at chunked-blobs · hzrd149/blossom

Blobs stored simply on mediaservers. Contribute to hzrd149/blossom development by creating an account on GitHub.

but that is more for generic files with fixed blob sizes.

Agree. Also Hzrd likes the idea of just linking to the m3u8 instead of having an event replicating it. The m3u8 should have relative paths that are the hashes

It's like Space Monkey from 2011 is back 🎉

Space Monkey (company) - Wikipedia

View quoted note →

Yooo