No, this is a legitimate problem. The nostr spec NIP-01 specifies the valid range of kind numbers. All kinds in that range should be accepted. If relays block kind numbers because they are not "known", it completely hampers innovation and keeps the network from growing. I'm curious which kinds are being rejected nostr:nprofile1qqsqddupn4l3cl65wggcyehd009g0pwuatsfudh28f90vewx68vrylqprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy2hwumn8ghj7un9d3shjtnwd9kk7tnrv9eksqg5waehxw309aex2mrp0yhxgctdw4eju6t0pqpyr2?

How are kinds established as "known"? They get into a NIP. How are NIPs made? They start as a draft. How are drafts approved? BY IMPLEMENTING THE PROPOSED NIP. You can't implement something new unless it is accepted by the network. This is a circular dependency. This is why new kinds that are unknown must be accepted if they are valid as per NIP-01.

Relays that exclude valid kind numbers are violating NIP-01! 📣 PASS IT ON https://github.com/nostr-protocol/nips/blob/master/01.md#kinds