nostr doesn't necessarily suck for this, but many clients are probably not doing QoS on requests to prioritize notes over media on low bandwidth links.
Discussion
Nostr does suck. The NDK that much of the nostr protocol is running on is BAD. Very, very non-performant. nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq32amnwvaz7tmgd9ehgtnwdaehgu3wd3skueqyluj3x and nostr:nprofile1qqsyeqqz27jc32pgf8gynqtu90d2mxztykj94k0kmttxu37nk3lrktcpz9mhxue69uhkummnw3ezuamfdejj7qg3waehxw309ahx7um5wghxcctwvshsz9nhwden5te0d4kx26m49eex2ctv0yhxcmmv9ume3twc are doing ridiculous amounts of work to improve for relays can run.
All Clients that I'm aware of are junk in terms of how data is used. Redownloading stuff, poor caching practices, etc. Are killing performance unless you have really good hardware on a really good network. This needs to change. Fundamentally, data efficiency needs to be addressed, or nostr will never be able to grow as it should.
I am testing on very low bandwidth links in notedeck and it seems to be working well
Corny Chat caches notes and profiles for the session, updating periodically. It's main burden is the initial client download.
Corny chat isn't slow, except for the messaging inside of the room. Dragged a bit, last week.
