Hi, nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8

As you suggested William, I tried logging of the nostr:npub1rznlzpg529u8j39a8qe7tapsygd54qp5qyr5jyue7whwpw79rsjqmzr4ly identity off nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 and tried logging into Damus with my personal identity nostr:npub1n6xaj8fpapnaa3rys69g6862ylqwzy798ce090kq5lrwykkja82sv7pnh9

Results:

- Damus startpage loads a quicker compares to when I tried to log in with another nsec.

- It takes extremely long time to load the notifications tab.

Improvement proposal:

I would love if nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 prioritized to add more optionality with the feed-algo. Why is this a improvement proposal?

I believe that one of the reasons why Damus currently has the nostr-client-record in longest time to load the startpage, is that it’s popping up new notes in the latest-notes feed. Especially when you’re following the amount of nostr identities that I’m following.

My favorite nostr-client-algo-feed is the Trending-algo that’s available on nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg, nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q etc.

If you integrated the Trending-algo into Damus, the Damus-startup page wouldn’t need to fetch new notes from relays extremely often (e.g every second).

I would therefore guess that making more nostr-feed-algos available in nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 would improve the speed and Damus UX enormously.

Best regards