This is the way, also kind 16 "shares" can be useful
Discussion
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.