💾 Archived View for bbs.geminispace.org › u › skyjake › 1577 captured on 2023-09-28 at 19:56:55. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-07-22)
-=-=-=-=-=-=-
Re: "Notifications sort order... Any reason it's not newest..."
Which context do you mean?
In the Dashboard and Notification History, they are listed newest-first.
In the emails, they are "most important first" (@mentions being considered highest priority) and ones with the same priority are oldest-first, i.e., natural chronological reading order.
In the per-page notification list, they seem to also be oldest-first.
The order of notifications in the emails could be made a user preference.
2023-06-05 · 4 months ago
Main page shows number of notifications followed by 'all posts' in random sorting order. I kept thinking that these are the notifications for some reason... I get mis-cued sometimes with titles (notifications follow) vs. buttons (click to see notifications)... Subspaces messages are in random order too, it looks like.
2023-06-07 · 4 months ago
I also often click on 'new post in s/SpellBinding' thinking it's 'new posts in s/SpellBinding'... As a thought, maybe it's better to use action words that are unambiguous: 'Compose a post'?
Ah I see what you mean. The current labels certainly tend toward being less verbose. It might make sense to have a separate "advanced" UI mode with terse wordings and redundant actions omitted, allowing the normal UI mode to be more verbose and clear.
2023-06-08 · 4 months ago
Actually, I like the way this page is formatted, separating 'Actions' from 'n Comments'. In other places the actions are not explicitly labeled as such... Also, I noticed that the wording is slightly inconsistent for posting -- I can think of 'Comment', 'New post in ...', and 'Compose draft in ..' off the top of my head. Sorry if I am nitpicking, but I'd love to see more of a consistent, unified interface, as much as gemtext can allow...
Notifications sort order... Any reason it's not newest first? I feel I must be missing something here.