nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy curious to see what traffic to the nostr.band api will look like now that trending users has been added to snort :)
Discussion
It's been around 30 hits per hour so far, I guess people aren't aware of the feature and don't visit the search page all that much yet.
I’ve noticed that apart from media upload, NIP and LN stuff, there’s been a lot of resistance to use HTTP APIs.
Maybe it’s trust on data, avoiding a dependency that could disappear, no standard APIs - so people have lock-in, or few APIs providers are available today, etc. Maybe none are paid, but the ecosystem can’t really support paid today.
Not sure. I’m keen to understand this better, as I see value and underdeveloped Nostr opportunities.
I haven't seen the explicit resistance, but I'd assume it exists, at least it just doesn't feel right to use non-nostr protocol for a nostr client. And all the points you mentioned are valid too, plus having to support yet-another protocol/API is just costlier for app devs.
I think it would be great to have many features as NIPs, but then there wasn't much demand for them before, and so investing in complex non-obviously useful NIP made no sense to me. Now that some features are starting to get traction my hope is that 'someone' comes up with a NIP and I'd just convert some of API endpoints to the new format.
'Trending' or other algo-generated lists seem like a simple enough concept to fit into a NIP, probably a top one on my todo list.
Yeah if I had to guess, it's because of the location.
Just FYI there are also API endpoints for trending posts/images/etc on api.nostr.band :)