The difficult part is indexing them by type so you can fetch one without the other. If Olas fetches kind 1s, it has to filter out everything that doesn't fit the olas format. On the other hand, a client can support as many kinds as it wants. So granular distinctions are generally good.
Discussion
It’s a shitty user experience.
What in particular? The re-posting via kind 1? Because I agree with that. But in any case I think clients can still provide a good UX by reconciling the different kinds when needed.
Reposting via kind-1 is horrendous and needs to be removed as an option in Olas. It creates unnecessary clutter/duplicate posts in clients that support both kinds. But also, I understand why people do it. Having 2 different event kinds for images now means the content you post is siloed, which is the opposite of how nostr is “supposed” to work.
I do see the use case for having a curated photo album for our nostr profiles, so in that way kind-20 can make sense, but only if it is broadly supported by clients. Right now it feels disjointed and not really that useful. And I hate the reposted kind-1 copies. lol