My suggestion would be to display messages in the messaging system from bottom to top (recent at the bottom, older at the top) instead of top to bottom, so that comments are read in the correct order when there are several.
It should obviously be sent at the bottom of the page. This suggestion isn't essential, but it can be useful.

This would require Scratchers to scroll trough many pages of messages just to get to new ones.

Presuming you mean this specifically for new messages, I do see your point.

We need to filter old to recent or recent to old

Catscratcher07 wrote:

This would require Scratchers to scroll trough many pages of messages just to get to new ones.

Presuming you mean this specifically for new messages, I do see your point.

The scratchers must be sent at the bottom of the page, where they are new messages.
(sorry for my bad english :/ I try to write correctly)

IMAG0od wrote:

Catscratcher07 wrote:

This would require Scratchers to scroll trough many pages of messages just to get to new ones.

Presuming you mean this specifically for new messages, I do see your point.

The scratchers must be sent at the bottom of the page, where they are new messages.
(sorry for my bad english :/ I try to write correctly)

Wouldn't this defeat the point of the suggestion if their are more message than can fit on a screen? A better way to fix the issue I brought up would be to only sort new messages oldest first, with the new messages still being on top of the old messages.

Such a system where only new notifications are in the correct order could lose the scratchers. Why is it impossible to send the scratchers to the bottom of the page? I don't understand .

IMAG0od wrote:

Such a system where only new notifications are in the correct order could lose the scratchers. Why is it impossible to send the scratchers to the bottom of the page? I don't understand .

I don't see how my proposed system would “lose the Scratches” whatever that means. Neither am I saying that it is impossible to send Scratchers to the bottom of the page (although it might require difficult backend improvements, as I know that comment sections fail to load if you go too far down and wouldn't be surprised if the same happens to messages), but rather that my proposed solution is better, since it requires less loading and avoids requiring users to scroll through perhaps hundreds of pages of old messages to get to new ones if none are detected as new or the autoscrolling fails for whatever reason.

I'm not sure I understood everything, once again I don't speak English but you also have to reverse the direction of the messages, so the new messages will be at the bottom of the page, the scratcher will be sent to the bottom of the page and will see the new messages including the comments in the correct order since in the majority of languages, we read from top to bottom.

If it is too complex to send the scratchers to the bottom of the page, it would be possible to create (as you suggested from what I understood) two pages, one with the new messages in the correct order (recent at the bottom and old at the top), easy to read and another with the messages in the wrong order but the one currently used by scratch.

However, you should avoid putting new messages in a different order from old messages and on the same page because otherwise the scratcher may not understand why some messages do not read like the others (While they are on the same page).

IMAG0od wrote:

I'm not sure I understood everything, once again I don't speak English but you also have to reverse the direction of the messages, so the new messages will be at the bottom of the page, the scratcher will be sent to the bottom of the page and will see the new messages including the comments in the correct order since in the majority of languages, we read from top to bottom.

If it is too complex to send the scratchers to the bottom of the page, it would be possible to create (as you suggested from what I understood) two pages, one with the new messages in the correct order (recent at the bottom and old at the top), easy to read and another with the messages in the wrong order but the one currently used by scratch.

However, you should avoid putting new messages in a different order from old messages and on the same page because otherwise the scratcher may not understand why some messages do not read like the others (While they are on the same page).

No, I am not suggesting splitting the messages page, that risks forcing users to sit through multiple loading screens rather than just one. I am suggesting that this suggestion is amended to only affect new messages. I do not find “the scratcher may not understand why some messages do not read like the others” to be valid argument against my amendment, as if we consider potential of confusion a sufficient cause to dismiss a suggestion, then this suggestion is not good; not only does change inherently create confusion, but this is a change away from what is normal across the internet. Like it or not, Scratch's message order is how most websites handle them.

Okay, no problem, it was just a suggestion.
Edit : wrong account :/

It can be an option to filter it.

VedanshS933 wrote:

It can be an option to filter it.

I agree.