This is going to be a bit long but hope it answers your question...

bolt.fun is a client that has a specific purpose. Knowledge sharing and community of builders and designers. We have two types of feeds on the site. Our own built in Story feeds which use a traditional database + various Nostr feeds where we do filter certain kinds of content that we fetch from other relays. We're experimenting with something called a "Community Relay" - since the global Nostr content won't be so relevant.

Here are some examples of where we fetch events from Nostr that fit a specific criteria.

**Nostr Devs + Nostr Design**

\- https://makers.bolt.fun/t/nostr?feed=nostr

**Folks on Nostr from the bitcoin design community**

\- http://makers.bolt.fun/t/bitcoin-design?feed=nostr

**Hackathon participants who use #NostrDesign in their nostr posts externally**

\- http://makers.bolt.fun/tournaments/2/feed

Reply to this note

Please Login to reply.

Discussion

Now why you have this problem is a different situation...

When you post a story, we promote it from our own boltfun Nostr account.

nostr:npub1funq0ywh32faz0sf7xt97japu8uk687tsysj8gndj4ehe825sq4s70gs0p

This promotion becomes the root event for our comments. This only and all the events that we actively store on the bolt.fun relay ATM. Idealy you should still be getting them in your feed so not sure if it's an issue with our relay... We haven't publicised that we run a relay yet.