<oembed><type>rich</type><version>1.0</version><title>Dawn wrote</title><author_name>Dawn (npub1cg…52ndy)</author_name><author_url>https://nostr.now/npub1cgcwm56v5hyrrzl5ty4vq4kdud63n5u4czgycdl2r3jshzk55ufqe52ndy</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>There&#39;s no reason not to limit those requests to trusted relays that host clean content. You could also maintain a list of foodie npubs, and/or your team and committed users (or a bot) could scan wider swath of the network &amp; republish content... then blend these things into a feed with the client&#39;s home relay. Continuing to pull directly from public-to-write relays for the main feed invites in spammers, which is a much worse experience for everyone than some new user not having a first post seen because it chases off the lurkers, too. &#xA;&#xA;More and more, existing users are withdrawling themselves from public relays and blocking them because they don&#39;t want to get spammed themselves or they don&#39;t want their notes to be associated with the nasty stuff that ends up hosted there. If someone wants to see those notes, they can follow the spammy &amp; nasty authors, who, by sane metrics, should be forced by the network into running their own relays for that stuff. That&#39;s kind of, in a strange way, the whole point of all this. &#xA;&#xA;Curated feeds should be strict and strongly opinionated, that&#39;s what makes them interesting and nice to browse. It&#39;s just really a shame to me that things like porn will randomly show up in a cooking app when simple preventative solutions exist and work.</html></oembed>