It's funny how every client's journey is similar: Kind 1 stuff gets developed really fast. Then it takes a long time until they implement Zaps because zaps are way too complicated compared to the rest. Then a second chasm happens when coding Nostr Wallet Connect because it requires a lot of async code, which is also too complicated. Then replaceable events make you redesign your indexing choices and your db becomes messy. With replaceable events, you can add lists, which take a leading position in the UI filters. Then you add DMs and other private decryption stuff that might need a new caching layer. Then labels and communities make you rethink what a feed is. And finally, if you are native, NIP-46/Android Signer makes you redesign the way you sign and encrypt/decrypt messages because everything is now async.
Discussion
Advise for people just starting out?
You are not going to design the perfect architecture from the start. So, get used to rewriting main parts of the app every now and then.
Have noticed the exact same thing with all the clients I’ve played with. The complexity is quite the steep learning curve from the point of a basic client that feeds content to zaps and caching.
It's on your lists. Click in the All Follows label in the top bar.
Yes but I had different relay sets for global in settings to minimize spam - with lists that doesn't seem to work 😬
I'm way too fond of Amethyst but that change radically shifted how I browse Nostr😅
I'm on a very old version v76.0- so maybe the relay settings works on newer versions
Do you need to change the relays used for Global here and there?
We implemented an additional filter to only show Global posts from Relays that are marked as Global in the Relay settings page. Before we would show everything that came in from other relays as well.
If you don't need to change the relay set for Global all the time, then this could be interesting.
Aww man! That touched the reality nerve 🔥