Well, it's not that it's bad. Just some interesting decision making in how the client works, user experience, and some quirks. I'll give you some examples.
When replying to someone, unless the note you're replying to is short, you can't see the whole thing when replying. Even pushing "show more" won't actually show you all of the note if it is long enough, and there's no way to scroll down.
There's also the issue of the block list. Everyone knows about this with Amethyst, there's a block list for spammers that gets passed around and updated as people report spam, but you can't see it. The user should be able to see it if they want to unblock someone just for themselves.
Every time you open the application, their kind 0 which is their "about me" and avatar URL and all that gets fetched, as well as the actual avatat. Every. Single. Time. There's no caching. There should be caching, at least of follows, that's a lot of data, on low bandwidth connections this makes it unusable. It even fetches your own information! The sane way would be to cache this information and then update if it pulls it and it's different.
It saves drafts as draft kinds to the relay automatically, so if you're typing a reply and you go do something else for a second, the draft goes out, there's no way to turn this off. I don't want my half written notes sent to the relay!
That's not exhaustive, just what I can remember right now off the top of my head.
There are a lot of options that seem like basic user friendly functionality that just aren't there. I can't think of many off the top of my head, and going into that would turn this into a feature request ramble, but generally speaking client developers in every corner of tech have begun to make decisions for the user and restrict their options instead of empowering them, it's a trend I've noticed and is getting worse, and amethyst does some of that, but almost every nostr client I've used does something like this.
I have my ideas for an ideal client, and I don't expect that without building it myself, but there are some things that are so standard or self evident that you've got to ask, why is it done this way?
mister_monster
npub1m5…jgjl3
2024-10-27 17:41:30
in reply to nevent1q…zvfd
Author Public Key
npub1m5s9w4t03znyetxswhgq0ud7fq8ef8y3l4kscn2e8wkvmv42hh3qujgjl3Published at
2024-10-27 17:41:30Event JSON
{
"id": "6b3f5633e698e50fe41aed59e3d637caa2b5c90ae6d3a963c5f009b51b1ad1b1",
"pubkey": "dd2057556f88a64cacd075d007f1be480f949c91fd6d0c4d593baccdb2aabde2",
"created_at": 1730050890,
"kind": 1,
"tags": [
[
"e",
"714ee1b386b353215bb568cd3b083ebb181a589d4b852d480047292d74780a5a",
"",
"root"
],
[
"e",
"2f8b8ef5e661c91c95c9ba34f0de97aa112697226f20091f48fcc017de3bf5de"
],
[
"e",
"389bb1954b912508fd384aab0d2fa1e31dfbf581c54729a24dc258d87b5ec121",
"",
"reply"
],
[
"p",
"dd2057556f88a64cacd075d007f1be480f949c91fd6d0c4d593baccdb2aabde2"
],
[
"p",
"ac3f6afe17593f61810513dac9a1e544e87b9ce91b27d37b88ec58fbaa9014aa"
]
],
"content": "Well, it's not that it's bad. Just some interesting decision making in how the client works, user experience, and some quirks. I'll give you some examples.\n\nWhen replying to someone, unless the note you're replying to is short, you can't see the whole thing when replying. Even pushing \"show more\" won't actually show you all of the note if it is long enough, and there's no way to scroll down.\n\nThere's also the issue of the block list. Everyone knows about this with Amethyst, there's a block list for spammers that gets passed around and updated as people report spam, but you can't see it. The user should be able to see it if they want to unblock someone just for themselves.\n\nEvery time you open the application, their kind 0 which is their \"about me\" and avatar URL and all that gets fetched, as well as the actual avatat. Every. Single. Time. There's no caching. There should be caching, at least of follows, that's a lot of data, on low bandwidth connections this makes it unusable. It even fetches your own information! The sane way would be to cache this information and then update if it pulls it and it's different.\n\nIt saves drafts as draft kinds to the relay automatically, so if you're typing a reply and you go do something else for a second, the draft goes out, there's no way to turn this off. I don't want my half written notes sent to the relay!\n\nThat's not exhaustive, just what I can remember right now off the top of my head.\n\nThere are a lot of options that seem like basic user friendly functionality that just aren't there. I can't think of many off the top of my head, and going into that would turn this into a feature request ramble, but generally speaking client developers in every corner of tech have begun to make decisions for the user and restrict their options instead of empowering them, it's a trend I've noticed and is getting worse, and amethyst does some of that, but almost every nostr client I've used does something like this.\n\n\nI have my ideas for an ideal client, and I don't expect that without building it myself, but there are some things that are so standard or self evident that you've got to ask, why is it done this way?",
"sig": "a9d97ff11b1b9361cbd819af03dc85531e462feaec0654ce7be7d8656bdc260073af8690abbc289fe5db871c0f8c02d382d8194b7e11461ebb5a4278dfa9d15a"
}