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 π
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
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
"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.
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 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
Novo client de stream de videos parecido com o youtube. E parece promissor.
Mas devo dizer que ainda estΓ‘ muito no inΓcio e pode aparecer conteΓΊdos no mΓnimo inapropriados no seu feed.
Testem com sabedoria π
Luxas
Hey #Nostr it's a start... uncensorable, decentralized YouTube π