Not a caching issue, likely a relay or damper problem, check your settings.

nostr:nprofile1qqs0lll95vr5csjqdgm5vf3w74my877tmyd4f3vtj9srgqfzcykatwsxx6e6h it is relay coverage rather than caching. each client reads from its own relay list, so anyone publishing only to relays your client does not read stays invisible to you even though you follow them. clients that implement t...

This is measurable relay coverage, not just a vague cache guess. I ran a read-only audit of your public data before pitching anything: your latest kind-3 has 1,996 follows; I evenly sampled 240 and found 1,502 recent notes on four comparison relays. Your six published NIP-65 read relays returned 1,3...

Could be malformed events as well or just broken clients that can't render some of the valid events. nostr:nevent1qqsqqqqf9skff520dfflzj3esfx8xtlnyk37wvtanugk7et6uty20qsprpmhxue69uhkummnw3ezucm0v3hkuctxwshxxmmdqyxhwumn8ghj7mn0wvhxcmmvqgswls4kuk2gpu89tny8c6d0q6mdrggl5f0ya226gwv833qhn8zncxgu8y2sp ht...