So mostr.pub pushes fediverse content to the following relays:

wss://relay.mostr.pub

wss://relay.shitforce.one

wss://nostr.coinfund.app

And the primal cache reads in posts from mostr.pub so I’ve you’re using primal, you’ll get mostr posts from the fediverse. We’ve got a couple issues to address. First, there’s a TON of content on mostr.pub, so lots of users won’t want to just add it to one of their read relays, but getting requests for content is how mostr.pub knows to go pull it down from the fediverse. If you’re using a client with a global feed, then you really don’t want relay.mostr.pub because it’ll overwhelm your feed with random stuff.

One option is for nostr apps to publish both the repost note, and the event that is getting reposted to its relays. Another is more use of caching services to pull that content in. In terms of making sure mostr knows what actual fediverse content nostr users are looking for, we need a fix for that too. 

I’m not sure this is so much an amethyst fix as it is a need to update some of how we’re running relays and caching relays. 

So, thoughts @Alex Gleason ?