Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

externals.io is unreadable #193

Open
javaDeveloperKid opened this issue Apr 10, 2024 · 0 comments
Open

externals.io is unreadable #193

javaDeveloperKid opened this issue Apr 10, 2024 · 0 comments

Comments

@javaDeveloperKid
Copy link

javaDeveloperKid commented Apr 10, 2024

Hi, I really appreciate opening PHP's internals mailing list to the outside. It's very valuable to be able to read discussions at a high substantive level. However the frontend is not friendly at all. There are two issues that bother me. The following relates to the scope of a message, where a message means https://externals.io/message/<message-number>:

  1. Finding new emails is very hard. One has to scroll the whole page and visually catch emails that have x hours ago where x is a number of hours since he has been reading the message conversation last.
    It's a little better when one logins via github. After opening a page there is a button on the right bottom "Next unread email" that moves us to the next unread email. However this works only on the first entry on the page, i.e. when I close the page this is gone - opening a page once again will not show us unread email. This is a disadvantage because one may or can read only a part of new emails and go back the next day or few days later.
  2. Reply to reply to reply to reply and so on. This is unreadable. Here is an example with 12 cascade replies.
    image
  3. Quoting an email that a reply relates to (that in turn also quotes a a previos reply and so on). I can see this often enough so I'm reporting this. There is no need to quote the whole email that one answers to.

My proposed solutions:
ad. 1. Remember the emails already read and unread on every page enter. Or add checkboxes so one can check a email as read.
ad. 2. Make replies in a single column collapsible. EDIT Ok, I can see replies are collapsible via this little circle with a minus sing inside.
ad. 3. I don't have an idea how to solve this one as I suspect this is just like mailbox providers work - one clicks reply button to reply an email and he doesn't modify anything manually then the previous email content (or all previous emails when it's a reply to reply to reply and so on) is included. Maybe a request to mailing list participants to remove the previous email content would help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant