even as optimized notedeck is network wise, I still notice subtle issue on the lowest bandwidth links.

one that stood out was that even though the data getting returned from the relay was really small, profile picture and media loading was swamping the link bandwidth and the nostr responses were just lost.

one change I'm making is QoS on certain requests. For example: ensuring nostr data is returned before we start loading media. This should work well on all connection types.

Lesson here is always be testing on low performance and low bandwidth devices (via android or iOS network link conditioners) if you want to create a good experience for everyone on the planet.

Reply to this note

Please Login to reply.

Discussion

Thanks for these architecture decision updates and notes.

Nice catch!

Maybe you can cache profile pictures and then later request to see if there's a new one. Better to see something then to be 100% up-to-date.

yes we of course cache profile pictures 😅

💯