No name shown in 'replying to' section of post when using Mitra

[watamelonman]

General description of the issue

When using Husky with an account on a Mitra instance, replies do not show the target of said reply. There is only blank space next to the 'replying to' section. This blank space happens on all posts regardless of origin (e.g. whether it's from a Pleroma instance, Mastodon, Misskey, Mitra, etc.). This isn't a problem when viewing the same posts from Mitra's web UI.

Husky information

• Husky version: 1.5.4
• Android version: 14
• Android ROM version: CalyxOS 5.7.0

Mitra version of instance

• Mitra v2.18

Steps to reproduce it

Please, describe the steps to reproduce the issue:

1. Log into Mitra instance account on Husky
2. View any post that is a reply

Where did you get Husky from:

• [X] F-Droid.
• [ ] Self-releases.
• [ ] Play Store.
• [ ] Self-compiled (specify tag/commit).

[captainepoch]

If Mitra implements the ActivityPub API as Pleroma or Mastodon does, it should show it. I'll take a look, but it's probably not Husky's fault.

[silverpill]

@captainepoch Sure, looks like a problem is on the Mitra side. Could you tell where data for this UI element comes from? I'd expect it to be Status.in_reply_to_id or Status.in_reply_to_account_id, but Mitra provides both, so it must be something else?

[captainepoch]

If it provides any of those (but I think the correct one is in_reply_to_account_id), it should show.

Nevertheless, I still have my account in your Mitra instance, so I'll take a look.

[captainepoch]

As far as I can see, in_reply_to_account_id is null (see attached image).

[silverpill]

Yes, but on this image in_reply_to_id is also null, so it is probably not a reply?

[captainepoch]

You're right about that, I made the screenshot about the wrong value. It is, indeed, with information about the account.

It seems, in the end, a Husky issue, so I'll do more research on why this is happening.

[captainepoch]

I didn't forget about this, I'm still investigating why it's happening.

[captainepoch]

Hello!

I finally detected what's the issue is here.

Pleroma and Mastodon (I globalize also their forks) include the username in the reply's response Json by the field in_reply_to_account_acct. If the user is at the same instance, it doesn't show the @stereophonic.space (as an example), and if it's not at the same instance, it does (see screenshots attached).

Mitra should do the same.

[silverpill]

I haven't found this field in Mastodon responses, but Pleroma includes pleroma.in_reply_to_account_acct and I added it too. @watamelonman said that fixed the problem, so we can close the issue now.

Thank you!

[captainepoch]

You're totally right about this, and it happens on Mastodon instances using Husky, thank you very much for noticing it.

I'll try to come up with a fix, in case you want to remove this fied, so it works for both of the backends.

Again, thank you!

[captainepoch]

I tested this with Mitra 4.9.0 and Husky 1.7.0-beta1, I think it works now:

Could you let me know?

[silverpill]

Yeah, I think it was fixed. Nobody complained about the bug since then.

[captainepoch]

Closing it, then. Cheers!