We already have good tools for that; some are design techniques, some utilitize AI. They're just not using them. They literally just hack wildly at some file.
Even just sitting and thinking a activity diagram through in your head would help.
Like:
Step 1: user goes to search field.
Step 2: user types in search parameters.
Step 3: user clicks search button.
Step 4: user gets results, if found.
What is obvously wrong with those 4 steps, in a Nostr environment?
--> You forgot to check if the user has the correct relays, or any relays, at all.
This is one of the most-common "user bugs" I see. The relays disappear or become paid-only or whitelisted, and then users try to write a note or search or reply and the client allows them to do everything and then just sits there with blank results. Not even a "Check your relays!" suggestion message, when returning a blank result.
Nothing.
Zip.
Nada.
I keep writing notes to nowhere and then I check my feed and I'm like, "Where are they?" Oh, relays disappeared again. ๐คฆโโ๏ธ
When you talk to the devs about it, they just say, "User error. Not my problem. They should think to set their relays (or reset them)."
I see what you mean. though noStrudel shows you a confirmation screen after posting a note, the relays it has been broadcasted to, the ones that timed out and any relay you have on your list but cannot write to.
I lost two paid relays recently because noStrudel was telling me that I'm not on the access list any more and to be frank, can't be bothered to follow up on the access.
I just spent 15 minutes trying to add relays to my search on Nostrudel, to find something that I'd written to specific relays.
Anytime I click the search button, it goes back to the previous setting.
Can only find the note by editing the URL directly.
And I had to resubscribe to my relays in nostrudel and next-nostrudel twice this week. Just gone. Poof.
And here's the problem:
If I report stuff like that, I get
"fork and fix the bug yourself, like the rest of us do"
or "Clone this other repo and edit these 5 files and then build this function."
or "Well, if the work-around worked, why are you complaining?"
or "you can't expect new software to actually work" (my absolute favorite because it shows how clueless they are)
or "User error" as a reply.
Or some midwit who only uses a couple features over and over, says "Well. I don't have that problem. Just ignore her. I still love you. She hatin."
Most users don't report or they only report and listen to that bullshit one time. They just get fed up and leave.
They. Just. Leave.
Yeah I hear you. I guess "we're early..." wont help either. Though I have to say that nostr has made impressive progress over the last year or so but yeah, still much work to be done before average mainstream people will see and graps the potentials of this protocol. In many ways just like Bitcoin.
Bitcoin was never this buggy, tho.
And I've worked at too many start-ups to buy the "early days" stuff.
Two lines of code is enough to start writing tests.
Thread collapsed
Thread collapsed
Thread collapsed
oh really? I had this happen a long time ago when I was jumping around clients to figure out which ones best suit my needs. Wiped my following a couple of times as well. Which reminds me, should do a backup with the end of the month.
As for relays resetting in search. I've noticed this too. Unsure if nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr is aware of that issue.
I've stopped reporting bugs. Got too many rude or indifferent responses.
Now, I'm just working on my own client. That way, if something is broke, I can fix it and don't have to make a fool of myself reporting bugs nobody wants to correct to developers who wish I would go away and stop using their stuff.
Published my first notes, yesterday. ๐
oh really? Maybe you're hanging with the wrong crowd. I can't say this about Hzrd, Kieran, Karnage or anyone else I've been involved with, so far.
I'm looking forward to check out your client or are you just building it for yourself?
It's part of something larger.
I was going to say something silly.... ๐
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
The stable version of noStrudel shouldn't have any issues with relays, although the next version is having issues with remember your relays.
I'm in the middle of rebuilding how the client works with relays so I can show more info on them and support different types.
But right now the UI is really bad. also the relays on the search view really shouldn't be there. they are misleading and I'm pretty sure it ignores them anyways ๐
I had to reenter the relays in the stable version. This week, I think it was.
hmm, that should not be happening. its really difficult to tell whats going on there though.
it could be other clients resetting something or noStrudel not being able to find your relay list when you login.
Either way I don't really know how to fix things like this, the best Idea i have is to implement a "history" feature similar to https://metadata.nostr.com to track the changes follows/relays/metadata
Can't we just have all of the clients read from that app or put everything in a list?
I've got 5 clients (6 with my own, now) and it's like ๐ฅด trying to keep them configured the same.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed