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
it's very simple to also serve regular HTTP over the same socket, the websocket connections start the same as normal HTTP requests, with an upgrade header, which initiates the websocket handshake
https://mleku.realy.lol will return you a little message that i set to include the NIP-11 information (which all the clients don't seem to update very often btw)
i should also add that both khatru and relayer ( https://github.com/fiatjaf ) have got little slots to let you put arbitrary web handlers in them to do such things as the http server you need for RSS documents, really you just need another process running that fields the updates and rewrides the static files that the webserver can serve)
i haven't done this terribly much with my fork of all this but i made it do some basic things, thanks to your nostrudel relay page showing the content of the normal https socket i put something in there
