If you know someone who wants help using this place, feel free to ask, I can answer their questions directly. This account aims to be an unofficial help desk, especially for new or non-technical people.

If they're having trouble signing up, they can email me at [email protected]

Also, please tell new people about the website at https://fedi.tips (especially the Quick Start section at the top). This has lots of non-technical advice for beginners and will help them get started.

#FediTips

Fedi.Tips – An Unofficial Guide to Mastodon and the Fediverse

An unofficial guide to using Mastodon and the Fediverse

@FediTips
Is there an android client where you can reverse the scroll direction?
It doesn't make sense seeing the very end of long posts first. Quite peculiar.
Thanks for the really helpful work.

@ianp5a

I'm not sure, I'm going to boost your question in case others can offer suggestions.

By the way, when you say "end of long posts first", do you mean the final posts of threads?

@FediTips On the timeline or home, posts appear bottom first. In a thread, it's OK. Newer posts are at the bottom.

@ianp5a

You mean the newest posts appear at the top?

@FediTips Yes. You need to scroll them downwards to read them. It's the opposite to the thread direction.
@ianp5a @FediTips
there is a setting for this in @Tusky .
@yuvalne @FediTips @Tusky
Thanks, but no, that only changes where you are in the main list. It doesn't reverse the direction of the list.
@FediTips @ianp5a I think this is what they're asking for: chronological vs. Reverse chronological.
https://github.com/mastodon/mastodon/issues/22667
@rspfau @FediTips No this does not specify whether chronological should be upwards or downwards.
Pachli 2.8.0 released

Pachli 2.8.0 is now available. This release introduces experimental support for reading the timeline in reverse order and significantly improves notification reliability, as well as the usual bug fixes and other small improvements.

Pachli
@rspfau @FediTips
Thanks. That looks promising.
Sadly they confuse the option by saying "newest first" and not newest at top or bottom. As First could be anywhere.
@ianp5a I'm curious...do you sort emails newest on bottom?

@rspfau
It's because I read from top to bottom. (weird!).
Imagine reading a Kindl or a long web page. I will scroll it upwards, so the text moves upwards. more text appears from the bottom of the screen. Chat clients do it that way too. So does Mastodon inside threads.

Maybe very short posts don't have an issue. But people post long posts a lot.

@ianp5a Oh, I wasnt being critical. It has me wondering why things are the way they are and what is optimal.
@FediTips
No. If a post in the timeline is, say, 20 rows of text, the last line at bottom of the post appears first, at the top of the screen as you scroll it downwards.
You will read "... the butler murdered him. The End" first.
@ianp5a I haven't tried it, but I'm using @Tusky which has a reading order setting
@FediTips
@ianp5a @FediTips On Tusky, newer replies are put at the bottom.
@RachaelAva1024 @FediTips
Inside a thread the direction is OK. The main timeline has the problem. Even in Tusky
@ianp5a @FediTips I use Tusky set to oldest post first. I also have it set to stop at where l was last reading.
@miniosiris @FediTips Thanks I set Oldest first. But cant see the "last reading" option.
Even with oldest first, the timeline did not change direction.

@ianp5a I don't know of an app that does this, but if you run across what is very obviously a thread, you can go into the first one you come across (which would be the last one in the series) and then I think that it will show the thread in order from old to new. That's how it looks for me in a browser. (If it doesn't look that way for you, it may be because my server is running "Glitch-Soc" which is a slightly different flavor).

@FediTips

@ianp5a @FediTips I use the default Mastodon android app and read posts in post order. Because new posts show up at the top, I start a session where I left off last time, with some number of new posts above, then scroll up until I run out of new posts. Because I'm scrolling up I see the bottom text of each post before I see the start of it or the author's name/picture, then scroll back down as I read it. It'd be nice if new posts were below so I didn't have to constantly switch scroll direction.
@tewalds @FediTips
Yes this is the problem I'd like to find a solution to.

@ianp5a @tewalds

I think this is because a lot of people don't read every post, so they just want whatever is randomly latest at the top, whereas other people do read every post so they want to start where they left off (i.e. the oldest first).

I guess there ought to be options for both groups?

@FediTips @ianp5a That sounds correct. I fall into the read every post camp, and unfollow anyone who overwhelms my feed. It'd be nice if the app was optimized for both directions/preferences.
@FediTips @ianp5a @tewalds If possible, I read all posts, starting with the last one I read. Fedilab for Android offered this option. This is not available in the Friendica web app, but I hope it will be added to improve the quality.
@franky_tegeler @FediTips @tewalds
Thanks but I didnt find any setting in Fedilab for this, and by default newest posts arrive at the top. Not at the bottom as I'm trying to do.
@ianp5a sadly, it appears that the only Fediverse client that lets you read bottom-up and keep track of your reading position is @ivory for iOS. That difference is alone will keep me buying iPhones.
@jemal @ianp5a @ivory I actually tried to find the settings in Ivory… could you point me to the setting? 🙏
Try the Phanpy app. It always shows new posts at top of screen and you scroll down to read older posts. Or you can use the Mastodon website as a web app on your phone. Or maybe I also misunderstand.
@rspfau @FediTips
I just want the newest posts at the bottom of the main timeline. (like threads already do), Newer timeline post should arrive below them. I will scroll them to move upwards as I've read them. As we read text top to bottom.
@ianp5a @FediTips This doesn’t help you (sorry!) but in case someone else has the same wish on iOS: Mona can do this. I.e. you open the app where you last stopped reading, and then scroll down to get to newer unread posts.
@ianp5a @FediTips this is available on the Pachli client in the "lab" section in settings. It's experimental so it might not always work but it is there. #pachli #pachliapp

@ianp5a @FediTips Pachli does have an option called "Reverse timeline order" under "Lab experiments", but I'm mainly using Moshidon for the design.
Another useful feature of Pachli is saving the point in your timeline where you exited the app (so you don't have to catch up everything at once).

I can't understand why such a basic feature is not considered as a standard on most apps.

@ianp5a @FediTips As best I can tell, the behaviour you're describing -- which also irritates me a lot, too -- is caused mainly by the fact that all posts are Public by default, meaning they stand on their own and will be seen by anyone associated with that user, independent of the context of the post.

I've recommended that posts be Quiet by default for this reason, and about once a month recommend that people set that as their default, so far with limited success.

@wesdym @ianp5a

Your home timeline shows all posts from people you follow no matter what visibility setting they are. Your DMs show up in the same timeline, for example.

It's just because apps show newest unread posts at the top by default, and they're asking for an option to show the oldest unread at the top.

(What you say is true on the Local timeline though!)

@ianp5a @FediTips
I've been thinking of this problem since my first few days on Mastodon.

There's no easy way to fix the problem since, here, threads and timeline are intertwined. Only reversing the scroll direction won't make much of a difference since you’ll come across the latest post before the first one anyway.

The kind of option you're looking for is a "conversation mode" where new replies to a thread would bring the whole thread back in your timeline while still showing the first post on top with some sort of notification of new replies within.

To achieve that, each post would need to be scanned to the find the first of the thread and then show this first post in your timeline instead of the latest one. It is most certainly technically possible, but I haven't seen anything like that in a Mastodon client.

@EricBeaudry @FediTips it's not about reversing the order. But reversing the direction of the main timeline. So newest at the bottom. The threads already have newest at the bottom. It would be trivial to do it in a client.
@ianp5a @FediTips ok, so scrolling down would get you closer to the present time from where you left of. Important nuance here, the client has to remember where you were otherwise you'll be move to the bottom (present) and scrolling up into the past. Meaning you'll still see the latest post of the thread before the first one. Am I getting it?
@EricBeaudry @FediTips
Try this, click on a post that has several replies. You see the thread. This is how the main timeline should look.
See the newest replies are at the bottom. See that you first see the oldest reply at the top. You then scroll the posts upwards, revealing newer ones at the bottom.
This. But in the main timeline.

@ianp5a @FediTips yep, we're at the same place now.

Then, we close the app and come back a couple hours later. At that moment, where should the app put us in our timeline?
- Where we left, and we keep scrolling down getting closer to present. In which case, we would get the desired behavior.
- Or at the bottom and we start scrolling up (into the past), in which case we come accross the latest post before the the first of the thread.

I'm with you that it would feel more natural to read in the same direction in both timeline and threads. However, if the app moves us to the present when we open it we end up with the same problem.

To summarize, newest at the bottom WITH a marker to get back where we left is what would be required to ensure we always scroll towards the present.

There would still be some "out of order cases" when someone you follow replies to a thread you've never seen before. For those, I only see the conversation mode explain earlier as a solution.

@EricBeaudry @FediTips
Changing the direction of the scrolling does not affect anything else. All the behaviour can be the same as now. It doesn't add any new problem.
@EricBeaudry @ianp5a @FediTips "Conversation mode" is a good idea for long threads but perhaps not as a global setting. It sucks to see post 20/20 of a long thread in my timeline first, then 19/20, then 18/20, etc. The author of a long thread should have an option to collapse their thread at the time of posting - i.e. acknowledging up front that "this is 1/x". Then *only* post 1/x is visible on anyone's timeline. When you click open 1/x you see the entire thread laid out perfectly.
@dnnsconroy @ianp5a @FediTips I'm with you. For this to really work great, it kinda requires that new posts be a the bottom, we get back to where we were when we left and that conversations resurface with the original post as the main one seen on the timeline.
Ideally entering the conversation would also bring me to the last read in there. With this, post numbering becomes almost irrelevant. It would mainly serve to indicate that the original writter is not finished.