why dont nostr:nprofile1qqs874el2hv8tn5wm3fgahuz99yl624el8r9my22gq39vcas56tmupcpr9mhxue69uhhxetwv35hgtnwdaekvmrpwfjjucm0d5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7zfpjt6 and nostr:nprofile1qqs879mhq6kkuzh2wk57xdzanl76uem8d7hlyjd7v4a4jcm4u88d8ygprdmhxue69uhhyetvv9ujucnfw33k76twwpshy6ewvdhk6qgcwaehxw309ac8yetdd96k6tnswf5k6ctv9ehx2aqpqkmmn videos show up in search?
Discussion
Too much signal
Because it's like wavlake and these are not nostr events
Also doesn't even let me post so far 
I can't even log-on to have a look around but I saw enough as-is.
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: nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx
why not kind1? there are a ton of videos already posted that way
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.
This is the way, also kind 16 "shares" can be useful
sounds good in theory but in practice you just end up with olas
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
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.
Yeah, clients would need to deduplicate somehow. Maybe we need a new kind.
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
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"
it did
Please don't overload kind 30023, this is how your videos look in habla:
👀 I stand corrected