Missing reply chains on a federated toot

[riking]

Clicking into the single-toot view on a post from another instance isn't rendering the replied-to toots correctly.

Prior toots in the chain from the same author do render.

Guess: this happens when the other conversation member isn't being followed anywhere on this instance?

---

Screenshot of no reply chain:

versus

---

• I searched or browsed the repo’s other issues to ensure this is not a duplicate.

[riking]

Another example. I am on social.wxcafe.net, the displayed toots are on mastodon.social, and the missing toots are on social.lou.lt.

https://mastodon.social/users/sarahjeong/updates/1611755

[riking]

Another example. I am on social.wxcafe.net, the displayed toots are on mastodon.social, and the missing toots are on social.lou.lt.

https://mastodon.social/users/sarahjeong/updates/1611755

[Fastidious]

This becomes particularly a problem on user’s main page, like https://mastodon.social/@david. There are absolutely no references to what’s been replied, not even if replies are occurring on the same Mastodon instance. No good.

[Fastidious]

This becomes particularly a problem on user’s main page, like https://mastodon.social/@david. There are absolutely no references to what’s been replied, not even if replies are occurring on the same Mastodon instance. No good.

[nightpool]

this is a huge usability pain to me right now—i've started opening every tweet I want to see in a new window, so I don't miss anything

Is it possible to do client-side loading of statuses? Or does that not work with mastodon's architecture? That would be the the ideal solution in my opinion—load the status ephemerally client-side and only commit it to the mastodon database if a user interacts with it in some way.

this can also be extended to loading replies to statuses in the expanded view, which has also been a huge UX headache in my experience.

[nightpool]

this is a huge usability pain to me right now—i've started opening every tweet I want to see in a new window, so I don't miss anything

Is it possible to do client-side loading of statuses? Or does that not work with mastodon's architecture? That would be the the ideal solution in my opinion—load the status ephemerally client-side and only commit it to the mastodon database if a user interacts with it in some way.

this can also be extended to loading replies to statuses in the expanded view, which has also been a huge UX headache in my experience.

[ashfurrow]

This seems to be working for me on 1.2.2, can someone else verify that it's still an issue?

[ashfurrow]

This seems to be working for me on 1.2.2, can someone else verify that it's still an issue?

[wolfteeth]

I still have issues with this (v1.2.2). Remote replies don't load their parent toot.

[wolfteeth]

I still have issues with this (v1.2.2). Remote replies don't load their parent toot.

[wolfteeth]

Still seeing on v1.4.1. This went away when I was on v1.3.x but it is back now. I had forgotten about this thread and created a dup: #3455

[wolfteeth]

Still seeing on v1.4.1. This went away when I was on v1.3.x but it is back now. I had forgotten about this thread and created a dup: #3455

[wolfteeth]

This bug has been very annoying to me recently. Someone I follow had a lot of public conversations with people on other instances, and every one of their replies would end up as a context-free standalone toot on my instance. AND it would show up in my home timeline even though I don't follow the other person in the conversation.

There is a discussion on the Discourse board about this: https://discourse.joinmastodon.org/t/1-4-1-probing-of-conversation-issues/354/15

Could be a problem with conversation_id vs. in_reply_to.

[wolfteeth]

This bug has been very annoying to me recently. Someone I follow had a lot of public conversations with people on other instances, and every one of their replies would end up as a context-free standalone toot on my instance. AND it would show up in my home timeline even though I don't follow the other person in the conversation.

There is a discussion on the Discourse board about this: https://discourse.joinmastodon.org/t/1-4-1-probing-of-conversation-issues/354/15

Could be a problem with conversation_id vs. in_reply_to.

[MCMic]

Same problem here, a bit annoying.
I also open all toots on there originating instance as a workaround.

[MCMic]

Same problem here, a bit annoying.
I also open all toots on there originating instance as a workaround.

[Cassolotl]

Is this resolved since we switched to ActivityPub?

[Cassolotl]

Is this resolved since we switched to ActivityPub?

[Gargron]

Probably, yeah

[Gargron]

Probably, yeah