Replies (117)

Well maybe this will be the NewNewPipe note10lqz2yuep2qymfmukxe0ku9ssjz6lzezhqq2arxhdzp0ntngetdsqv7h9n
I’ve tested it primarily with extension and nsec.app which had to constantly open to approve. Maybe try with a browser extension and see how that goes?
I want YouTube mirroring support on this if it's possible. That way, I can keep my stuff on both #nostr and YouTube this way, just in case YouTube ever shuts down my three channels.
There's a small bug. When it first popups to login, close it and then click the little N icon again and it will register that extension login is possible.
Interesting, if you hard refresh browser does it show a profile to login with in the popup? I may have to test with that setup to see how the flow works
More-10's avatar
More-10 5 months ago
Can't get this to work with Amber on GrapheneOS. Stuck on the Connecting ..." with both Brave and Vanadium browser. Tried the trick with closing the initial window and clicking the little "N"
More-10's avatar
More-10 5 months ago
Even tried with the "I fully trust this application. Sign automatically every request." on the Amber side.
Haha so weird. I know that there are some intermittent issues with Amber sometimes not fully allowing it to Authenticate. Glad you got in!
More-10's avatar
More-10 5 months ago
Did get it to work on Vanadium now, but Brave seems to be blocking something (even when I take down all shields). 🤷‍♂️
Akashi Hyogo's avatar
Akashi Hyogo 5 months ago
We should have more specific tags for bad content. First "NSFW" is some guy testing flipper zero "in the wild" (maybe "illegal"), second one is CSAM ..
That one NSFW tagged video was just a test and can be ignored. Hopefully, most reasonable people will correctly tag with NSFW for any pornographic or other suggestively NSFW videos. For those who don't, the videos can be ratioed through community-driven moderation and help "conceal" them, allowing people to avoid viewing them if they choose. Of course, this system is by no means perfect, but it's a start.
A lot of media hosts do no moderation. So that fails. You need to design for a hostile environment and you can trust no one unless you have reasons to do otherwise
For sure, I thought about requiring a small sats fee in order to publish. Or, some sort of WoT. But, for now the ratioed option seemed like the best to start and gauge from there.
With the current number of nostr users, we are ok. But with a larger audience uploaders and/or users need to pay for storage / bandwidth.
Isnt a directly taken "offer to pay" a proof? What do I dont see in the context? Or you mean you need the proof for "accounting" purposes?
Valid point. And you mean having payment for spam is making it censorable, and you want a provably uncesorable sw. Right?
Cool! I think giving users the possibility to filter on different things will be really important for adoption, e.g. to ensure that users don't get CSAM or similar disgusting content in their feeds. Could be white/blacklisting of blossom servers, react/adhere to reports from your 1st or 2nd degree nostr network, etc.
Thanks! Absolutely, those align with some ideas I have going forward and for ways to mitigate gaming the various control systems by bots. It’s cookin’ time 😎
Yup yup basically just a proof of concept or MVP at this point, but with time I’ll keep tinkering away.
Would be great to watch it grow! It's a quite expensive service to build, still worth trying. Will share some sats as soon as I have more.
There is also Flare, which seems to work in a similar way 🤔 So I have a question... Why do you prefer to use content posted only by the client instead of also using videos that are already in Nostr? It always seems like starting over from scratch, having to post content one by one in a new client... But I apologize if I'm mistaken.
Sadly, Flare is completely centralized. I believe they were even using AWS for their uploads. The only thing Nostr related was a login iirc. Plebs is the first to use multiple Blossom servers and have automatic fallback support to other Blossom servers if one goes down
No, they are Nostr events. That’s literally the event ID in the URL. It’s currently using a 30023 long-form kind and tag to feature videos only posted through the Plebs app at the moment. I’ll be integrating NIP-71 too. CC: @ODELL
The problem exists when feeding in video published externally without thumbnails or who’ve not been uploaded through Blossom servers. The purpose of Plebs is that it uploads the videos and thumbnails to multiple Blossom servers and then has fallback support to trying the video’s sha256 hash with another host if one goes down to ensure redundancy.
nostr already has a lack of content and kind1 is lindy lack of thumbnails is less of an issue than lack of content cutting up our already limited network effect is questionable imo i will continue to post my shows blossom kind1
I don’t know of another way to prevent deadlinks if a general kind 1 event who didn’t use a known blossom server is shown through the Plebs app and the media host they used doesn’t exist anymore. It would just show a broken video 🤷‍♂️ Other clients can publish through to Plebs if they want as well, keeping the network effect. The mission is in trying to ensure that the videos uploaded have been to Blossom servers and more than only 1 to ensure redundancy. There’s also an issue of brigading and bot spam. If not for the small tweak made for Plebs app it could be filled with just absolute garbage like Global. We already see one person who used a bot to abuse the ratioed feature and allowed showing the little girl video again. But, I have a plan to hopefully solve this sort of problem and prevent bots abuse.
A good compromise is to post the use-case-specific kind, then quote it in a kind 1 to advertise its existence. This also encourages clients to either implement render support for the new kind, or advertise alternative clients via NIP 89.
Why is it using the long form article kind to begin with? I don't think this particularly hurts existing clients but it seems like its really going to confuse users
maybe, but I don't think the problem with olas was that it didn't use kind 1's But if every new client start building on a kind 1 and doesn't transition to their own kind. then its going to cause a lot of confusion with users. for example users uploading videos on plebs.app probably don't realize they are publishing long form articles in other clients
I was originally building it as a long-form client and then pivoted to only video. But, am planning to correct it for video-only kind.
"Yo, I feel ya! 🤔 But what’s the deal with the long form? Is it just to flex the deets or what? Think it’ll clear things up or just add to the chaos? #ConfusedVibes"
If every app starts using their own kinds the entire interoperable part of nostr goes down the drain. Imo if you publish a video on flare it should display on any other platform that supports video content. same for streams and co. If I go live on zapstream I expect to be live on the entire network and not on one site.
Personally I'm ok with this or a new event kind, just not 30023 The bigger problem is I don't see why you're using blossom with zero BitTorrent integration, that's not very censorship resistant or decentralized of you
I'm not sure I understand you. Plebs currently uses 3 different blossom servers for the uploads. So, there is no single point of failure or central host. If one of the blossom hosts goes down, it will try to match the video's sha256 hash with another provider to load it. That seems pretty decentralized and censorship-resistant to me.
Again, it seems like an increase instead of an elimination of censorability and centralization in previous tools like BitTorrent and Tor
Blossom requires blossom hosts to stay online and I haven't seen any evidence it handles a poor internet connection better than or even the same as BitTorrent Not sure what technicals you're asking me to explain though If BitTorrent only works for downloading and not streaming then a nostr video platform should still at least have built in support for BitTorrent infohashes to help people with downloading
Niel Liesmons's avatar
Niel Liesmons 5 months ago
One kind and per content tyoe. One community (daily driver) that handles multiple content types. The problem is that no one (else) is building for the latter.
There is nip07 login with extension. When the popup happens close out and then click the floating N icon and then the popup should show extension option. It’s a known bug that I will fix.
Clippycoiner's avatar
Clippycoiner 5 months ago
I agree. Interoperability is a huge thing for NOSTR. Videos on Primal or Amethyst I would think you'd be able to view on a NOSTR version of YouTube.