Yep, I'm just playing around. Now idea if it's feasible. I'm thinking podcast dedicated relays would probably change the max event size, and only store events with a certain kind to indicate it's an rss feed. I can also see them being paid relays to store messages that the podcasters using them support. Free to fetch, paid to store sort of thing.
This wont work for many reasons, but mainly because as you pointed out the RSS feeds are generally larger than the max event size most relays have set
Also using kind 1's for data is generally a bad idea since it conflicts with social clients (bad UX) but I'm guessing your using them mostly to test
nostr:npub1yvgrrzf4dnmu30qfhw95x87ruu0g2kpv3a64h8hpvqsre8qeuspsgd6pv9 if you want to distribute RSS feeds via nostr then something like blossom + nsite ( https://github.com/nostr-protocol/nips/pull/1538 ) might work better since its a lot closer to traditional http. but its still early days and it while it "works" the documentation isn't written 😀
I've talked to nostr:npub1yvscx9vrmpcmwcmydrm8lauqdpngum4ne8xmkgc2d4rcaxrx7tkswdwzdu about this a little
Discussion
random question, but what nostr client are you using? I'm noticing some issues with the events your publishing and I'd like to let the dev know
FWIW, here's a link to a podcast player the get's the xml from a nostr relay.
https://svelte.dev/playground/ff177c532f0743e490bdfaaaa2884d40