I think thatâs bad, and a âfailureâ in the general model. Because you keep looking for where each person creates their notes, besides being laborious, itâs uninteresting. I like to access my client and see the recent thoughts of those I chose to follow - but that doesnât happen; which makes me have a job of decorating old-fashioned ânicknamesâ. đŹ
Haha, but the notes I usually don't see is from users that I should see, the example was from nostr:npub120rmmsl94v2g9utt77gu2mp5mv6lv83l6573m6cg0vnkcldm7kuqunx44g
profile.
Discussion
Yeah, itâs definitely a hassle. But for the sake of decentralization, itâs a trade-off worth exploring. Otherwise, everyone might as well just use a single server.
If you donât mind, you could try putting your most active relays at the top of your mailbox relays list. That way, itâll be easier for more people to find you. đ¤
This is definitely a client flaw on the part of nostr:npub120rmmsl94v2g9utt77gu2mp5mv6lv83l6573m6cg0vnkcldm7kuqunx44g's client since he is advertising publishing to 12 relays, but he actually only publishes to the 4 big ones.
What client are you using, nostr:npub120rmmsl94v2g9utt77gu2mp5mv6lv83l6573m6cg0vnkcldm7kuqunx44g?
In my library I've decided that people who advertise more than some number (I think it's 8 or something) of relays are clueless and their relay list shouldn't be trusted, so we default to reading from the big hardcoded relays from them.
> In my library I've decided that people who advertise more than some number (I think it's 8 or something) of relays are clueless and their relay list shouldn't be trusted, so we default to reading from the big hardcoded relays from them.
That's a good approach. Iâll make the change later.
Please add this to people that have only onion relays too.
Hi nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl I saw some commits that looks like fixed this problem right? if yes, why I'm not seeing posts from this profile: nostr:npub1ggfzdxa8xrrzhaut6venkrmjtw8wl25y6l0wramkc7d4dlyaflzsxxrfcq
Thanks
Two relays werenât detected as onion relays because their format was completely wrong
ws://ws/oxtrdevav64z64yb7x6rjg4ntzqjhedm5b5zjqulugknhzr46ny2qbad.onion
ws://ws/nfrelay6saohkmipikquvrn6d64dzxivhmcdcj4d5i7wxis47xwsriyd.onion
It means?
Jumble treats them as regular relays and tries to fetch notes from them, but ends up getting nothing.
Is there any improvement on Jumble that can be implemented to mitigate this problem? Thanks.
We're unlikely to introduce special handling for every edge case, as doing so could unintentionally affect regular users. If someone wants their notes to reach a wider audience, it's important that they maintain a healthy list of relays.
Understood. Please nostr:npub1ggfzdxa8xrrzhaut6venkrmjtw8wl25y6l0wramkc7d4dlyaflzsxxrfcq fix these two relays url you added wrongly. Thanks.
Try now
I think take some time to update. Did you remove the relays? If yes, great. In some minutes I test again to see if your notes shows to me.
But I have the impression that if someone add a wrong url, shouldn't affect the other ones. Maybe he client shouldn't have allowed him add this wrong url?
When something is decentralized, it's very hard to not think about the edge cases, because many clients could implement things wrong, no?
Its URL complies with the standard, and the trailing xxx.onion is part of the URL pathname. I cannot identify it as an onion URL. If I simply classify all URLs containing "onion" as onion relays, some normal relays with "onion" in their domain names might also be misclassified as onion relays.
Edge cases like these are impossible to cover completely. An error in one client should not be the burden of other clients.
.onion/ is the term you are looking for. There must be prefix/suffix match text comparison functions, if it breaks the URL down. Scheme, address, path and query. I find it hard to believe that JavaScript lacks an equivalent of Go's url.URL type. Then it is literally just a suffix match on the address element.
ws://ws/oxtrdevav64z64yb7x6rjg4ntzqjhedm5b5zjqulugknhzr46ny2qbad.onion
The issue is that there's an extra ws/ in the URL, which actually makes xxx.onion part of the path, not the host.
JavaScript does have a URL class too. To be more rigorous, I should extract the host and match the suffix there.
Since I arrived here, I always thought that having a number of relays would not be a problem, since the idea would be to have materials from specific people, as is your own case; from what I understand (a specific one).
Although my list is longer than 8, as far as I remember, I only added two more, or one; I donât remember well. But to my humble thought, making a choice of relays as dictated to me, I would continue with the same problem, losing materials - and having more, I classify myself as spam?!
It doesnât make sense!
For example, as Legend, I have the privilege of using the premium Primal, if I deleted some of the relays I use now (and that already came by default), 100% sure, I would lose notes.
Iâm sure youâre wiser than me, but where am I not observing correctly - or else not complementing my friendâs note nostr:nprofile1qqsxrxhk5c9nlex8xw4v5psu2gkvn370rkr77nys37kvtmvnd5aa7gcpzemhxue69uhkummnw3ez6un9d3shjtnpwpcz7qg5waen5te0xyerwt3s9cczuvf6xsurvwf00ej0mk initially?!
The only problem here is that your list advertises a bunch of relays but you're not publishing to all of them, only to some.
No client can connect to all these relays to fetch your notes, they generally connect to only 2 or 3 or 4. And it happened that the 4 (?) Jumble connected to didn't have any notes newer than from September 2024.
Perfect! Iâll reevaluate now. If there is an excess and with little added value, I was taught back there totally wrong, and I have continued to replicate this since then.