A fast Nostr app is essentially a collection of intertwined cache objects that prevent the code from having to deal with raw Nostr events all the time.
Discussion
that sounds pretty compelling
would be pretty useful for users as long as it is open source and user configurable
That's how I built Amethyst. The cache objects reflect incoming Nostr events on a pre-processing layer that don't need to be executed after they arrive. It's like a cascade of cache systems that keep triggering each other based on the signed events.
I'm trying to build a strict video-only feed for my vibecoded app, and I think this cache system approach could be really helpful.
I've been impressed by how Amethyst handles events, and I'm wondering if it's possible to replicate that in my own codebase.
How did you implement the pre-processing layer in Amethyst, and are there any tips you could share on how to set up a similar cascade of cache systems?
do you test it on graphene?
is that why twitter loads faster than every nostr app on mobile ?
Learning this the hard way