There is a lot of content out here that I’m just not seeing. I’m assuming it’s because I’m not subscribed to the relays that these users are on? I’ll browse a profile directory and 90% of the profiles will be devoid of NIP-05 usernames, profile pictures, bios, display names, or posts. But, I can see that my mutuals are following them. So, I’m guessing they certainly exist but that my client just cannot ingest their content because of relay differences? 🤔
Login to reply
Replies (12)
As many clients we have, there are different approches how to discover / fetch events from relays.
Most clients follow some heuristics from NIP-65
https://nips.nostr.com/65
But you should try different clients to see if it makes sense to you what is happening. Are you just wandering / in a discovery mode or are you looking for specific types of content?
Mostly wandering/in a discovery mode. I’m trying to discover content and users I can follow so that I have a healthy, enjoyable, and active following feed. I’m using `nos.social` as my client as it’s *far and away*, hands down, the best client experience I’ve come across yet.
Compared to some web clients like `iris.to` it’s quite dead (but only comes with 3 default relays available to subscribe to) but is also “clean” insofar as not inundated with spammy crypto stuff.
Really wanting to try going “all in” with Nostr. I’m huge on Activity Pub, host my own Fediverse instance, and love the community therein. But, I’m not a huge believer in the Activity Pub protocol. Recently tried AT Protocol via Bluesky and I am also extremely skeptical of the AT Protocol architecture. Also, the entire ATP community (+90% Bluesky, de facto) is extremely hostile and toxic. Meanwhile, while I think Nostr has a lot of problems with their community (or, lack thereof, kinda), onboarding, and clients, I believe in the architecture of the protocol and I think Nostr is “the way to go” when looking for viable decentralized networking alternatives. It’s the best-designed protocol of the lot which pre-solves a lot of conceptual problems I have overall for what I want. Also has the greatest potential for facilitating a client experience I am looking for and wanting to vanguard (something SSB like). I really like Nostr, conceptually. I want to commit to it.
You could try nostr:npub1n0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5es5mk6h0, it’s my daily app on iOS
And discovering takes time / effort, but there are some tools which can help you
https://following.space
https://noogle.lol
https://nostr.band
Client nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q
Webclient nostr:npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez
Shameless self-plug tool: nostr:npub12pj5g0370uz3f49flpz8scs85p8s9c7l6ueutjhkyc3jnggrlafsmmljva
We can shake hands 🤝
I totally agree, as I also was quite active in the fediverse as an instance admin and running my own personal mastodon instance. When trying to do stuff on my own with the protocol, I didn’t clicked. At that time (autumn ‘22) I also found Nostr but ignored it at first for a couple of months (the Twitter migration took quite some energy). But later on when I saw how easy the protocol was, it was also easy to go further with Nostr. And now, we are still very early and things are evolving quite rapidly in some areas (but we need more hands to do the works!)
See, I’d love to check these things out, but most of them are just `npub`s with empty profiles. I can see they exist, and I can see that some people I follow are following them already, but beyond that there’s zero content—entirely empty. 😰
Is that with the nos.social client?
I suppose it’s unable the fetch the metadata (profile) of a npub…
Yes, this is on the `nos.social` client. I just checked on `iris.to` (not a great interface!) and the majority of this content is loading, but still not in an entirely complete sense.
Hmmm
This is what I see in nos.social and it not great indeed
Now compare that same content in the Nostur client (second screenshot) to see the difference


Okay, yeah, we’re essentially seeing the same thing. So, good to know it’s not just on my end!
Easy fix: add wss://relay.damus.io to relay list in nos.social
Nice! I'll try that. I'm trying out a different client now (more macOS-friendly) called Nostrmo and things are working better already.