pmiossec
commented
1 month ago I can't agree more with this proposal: I switch to a new phone so I knew this setting exists but I spent nearly one hour trying to find it because I was dismissing this one due to the label that, I think, was completely misleading and I thought it was doing something else.
Because, if I understand well, it has an effect only on the 'load more' behavior, another proposal is to rename the option 'Loading order' or 'Loading behavior'.
In #89 @s427 wrote
I strongly agree with that, so I take it to a new issue. I tried Tusky in hope for just that handling of the "read more" loading, implemented with that feature and never would have tried out that option as I expected it to just reverse the timeline as an option with that name does in every other app I know. I even wrote a weepy text about the problem with the widespread gap-fill-loading-logic of microblogging clients (in German). Someone then noted that the "Reading order" (correctly translated to "Lesereihenfolge" in German) does just what I was looking for. Finally, my long lasting problem is solved and I was so close to that. Thank you btw. 🎉
Maybe a little help-annotation could already be helpful, explaining what that option really does.
I also second the proposed wording "reading direction" (or "preferred reading direction") instead of "reading order" and then "from bottom to top" (or "towards Now") and "from top to bottom" (or "towards the past").
For German that would be "Leserichtung" or more clear "Präferierte Leserichtung" instead of "Lesereihenfolge" and "Vom letzten Stand ins Jetzt" instead of "Älteste zuerst" and "Vom Jetzt in die Vergangenheit" anstatt "Neueste zuerst" (maybe that sounds a bit too lyrical, but it nails it).
Or, maybe just ditch the whole option and just use the the last scroll direction to decide in which direction the toot-gap will be filled as Metatext for iOS does (elegantly showing up and down arrows to indicate that, see the screenshots in this toot).