pull down to refresh
100 sats \ 2 replies \ @adlai OP 8h \ parent \ on: Coping with haters meta
The way my client is rendered, it's almost too easy; "mute" is often the item closest to the mouse after clicking the three dots by a stacker's name. Although this only happens when the username in question is close to the bottom of the screen, that's where comments appear when they are scrolled into view one-by-one... not being a UX professional, I don't have much to do right now beyond complain, unhelpfully far away from the site developer's notifications, and maybe reread all my relevant complaints in some quiet hour next week.
reply
I'm rarely convinced that the first response to any UX complaint should be, "file a bug report", because quite often the specific bug would most accurately be labelled "wontfix" after changing the mechanics that caused it to occur in a way that the entire flow isn't triggered anymore.
In this case, I'm guessing the sites like this in general work better when the comments are loaded directly1, rather than scrolled into view; I have found myself prefering a similar navigation flow with structured pages like Wikipedia articles, where I can save anchored links at any moment that are quite close to my current region-of-interest. Scrolling in general is a huge false friend, because although it feels familiar from physical media, it is also stupidly inefficient from an implementation perspective... however, it's what people have mostly come to expect.
Footnotes
-
like the action resulting from the blue circle by the notification bell ↩
reply