Turned a lil high today but slowly pushing it lower until I find that sweet spot for power
The hardest part in coding a nostr app is the nostr part, shocking. This chart is a comparison of the pros and cons of three different nostr apps fetching styles. The thing I've suffered with the most in building a client is knowing what is the correct process to fetch a dataset from relays and how to serve that data. How much data to fetch at once and how compartmentalized should my fetching be.
Primal is the only app that I know of that uses a caching relay and this leads to stale data, centralization, and censorship but this is why they're able to leverage accurate event counts on their users profiles and notifications. I'm assuming it's aggregating events on the server side to condense these counts into a single fetch. Working with nip-45 outside of caching doesn't seem scalable in my limited experience with it.
No matter what, vibe coding can't build a production worthy nostr app and It's time I commit to stop taking shortcuts if I want to realize my vision. So I'll be spending the next however long it takes to learn how each web apps fetching strategy works to find an optimal conclusion.
I'd appreciate it if anyone wants to share any advice while I'm still figuring this out. Also it's quite awful at times learning this skill set solo, so thank you if you've ever been supportive to me.
