If you see a post or reply in your timeline and you want to find out which thread it belongs to, just click on it! This will take you to the post or reply within its own thread, where you can then scroll up and down to see the rest of the thread.

(I know this might sound obvious to some of you but I have had several people ask about this, and there's no such thing as a silly question 👍 )

#FediTips

@FediTips

Prior to the 4.3 rollout your notifications would have the text of your own post in it; now usually you have to click on your own name link to be taken to your post (very counter-intutitive). I'm also seeing some variation in my notifications' behavior, likely due to version differences between the notifying instance and my own instance.

@artemesia

That's weird... it's still showing the text of my posts on notifications?

Are you using the web interface?

@FediTips

Yes, web UI.

@artemesia

This is what I see on my server for notifications, are you not seeing this?

@FediTips

This is what I see, with very rare exceptions where the text of my own post does show up (pre-4.3 style).

@artemesia

That is very odd... haven't seen that happen on my own server or another server I use, which are both on 4.3.

Can't find anything in user settings that would relate to this either. 😦

Might be worth asking your server admin about this? It should be showing your post, I wonder if they have custom CSS running or something? Custom CSS can sometimes mess up how things are displayed on the website.

@FediTips

FWIW I run firefox with ublock origin on OS X. That's not an uncommon combination with the mastodon crowd. It's not urgent for me since there is a workaround (clicking on my name link or on the empty space where the post text should be). Maybe I'll dredge in the vault of my memory and turn on some firefox debugging, perhaps a CSS glitch or javascript exception is being thrown.

@FediTips @Uncleharvey I’ve noticed that method doesn’t work sometimes. If I see “Followers Only”, that’s understandable. But about half the time when it doesn’t show the preceding comment or thread, what is a reason that happens?

@cobalt

Are you using an app or the web interface? If it's an app, which one?

@FediTips App: Ivory for iPhone #Ivory

@cobalt

Hmm... can you try logging into your server's website (awscommunity.social) and see if clicking a post works okay there?

Would be useful to find out whether this is a problem in Ivory or on your server.

@FediTips I think you mean I should look at the Local stream for awscommunity.social, right? I’m always logged in there desktop and on phone app. It may not happen there because it is primarily a business and tech account but I’ll try. Thanks for looking into this.

@cobalt

No, not the local stream, I mean log in on the website with the same account and password you are using on Ivory, where you've noticed these problems.

You could then try clicking on posts in Ivory and then the same posts on the web, to see if they take you to the correct threads or not.

If they work on the web but not Ivory, then the problem may be on Ivory.

If they don't work on the web or Ivory, then the problem may be on your server.

@FediTips Ahhh okay. I just spent 20 minutes looking for any individuals posting on the local and in a week I found only 6 individuals and one was me. Most posts are @radio from awscommunity so it’s more like announcements. I will try your method ofvtracking this down the very next time on my phone I try to follow a threaded reply. Thanks for your help.

@cobalt

It doesn't have to be on the local timeline, it can be any post on any timeline, it will work the same 🙂

@FediTips Silly question from me below ;)

One of the "pain points" that I'm finding is that the threads I interact with outside my instance don't show the full history of other replies.

I understand that this is the decentralised nature of it where I need to visit the other instance in order to see more of the replies but is there a way to make the replies "federate" more?

Personally I find it a little annoying to use another instance and get used to a different layout and all.

@hammy

Yes, this is a much discussed point. It is possible to manually force your server to notice the other replies, by copying the web address of a reply into the search box on your server, but that's cumbersome if you want lots of replies to be noticed.

There ought to be some kind of process that loads an entire thread's replies to your server when you ask it to.

There is an item on the Mastodon roadmap ("Explicit controls to fetch more data from origin server") which sounds like this.

@hammy

p.s. If you're comfortable using Github, you can vote for this feature to be added by giving a thumbs up at https://github.com/mastodon/mastodon/issues/9409

There is an unofficial browser add-on called Substitoot which acts as a workaround at https://addons.mozilla.org/en-GB/firefox/addon/substitoot/ for Firefox and https://chromewebstore.google.com/detail/substitoot-%E2%80%94-improved-mas/oedncfcpfcmehalbpdnekgaaldefpaef for Chrome.

Fetch whole conversation threads ¡ Issue #9409 ¡ mastodon/mastodon

I'm replying to a message on, say, Prismo, and I see this in Mastodon: Then, I go to Prismo page and see the whole thread: Turns out, there's a lot more messages in the conversation, and Mastodon s...

GitHub
@FediTips
But why can I see replies (by the original poster) to replies to the post, but not see the one from the person they're responding to? I hope this is clear. It happens so often...
Example:
Post text from @example (I see this)
(Nothing that I can't see, but obviously a response from @responder)
Response to @responder
Response (which I see)
Etc
Etc

@elliek @example

It's difficult to say without seeing it, but it sounds like they're responding to an account that has been blocked by you or by your server? In that situation, you would see the replies but not the blocked post.

@FediTips
And now I can't see a single example. I've possibly asked you this before, but I'm pretty sure I've gone to the actual profiles being replied to and seen them fine.
I'll keep my eyes peeled for another example.
Thanks for the reply, as always.
Ellie