[bug] Mastodon API: Repeat/Reblog statuses have duplicated content #450

New issue

Closed

opened 2023-01-26 09:35:28 +00:00 by Fell · 1 comment

Fell commented

2023-01-26 09:35:28 +00:00

Your setup

OTP

Extra details

first installed Pleroma through OTP, then converted to Akkoma according to docs

Version

3.5.0-0-gd9508474b

PostgreSQL version

What were you trying to do?

When trying out Elk Canary (https://elk.zone/) I noticed that reblog/repeat statuses have duplicated content, like here:

URL of the depicted status: https://mastodon.social/users/KatM/statuses/109750713926989417

At first, I believed this to be a bug in Elk, but it looks like it's a problem in the Mastodon API.

So, bear with me, as my web development skills are stuck in 2009. When the status in question comes in as JSON from the API, it appears that status.content is identical to status.reblog.content. Elk then assumes, this means it's a "reblog with comment" type of action and displays them both.

You could argue that's Elk's problem, but (1) Mastodon seems to behave differently and (2) duplicated content is a waste of space.

What did you expect to happen?

When status.reblog.content is set, the API should not populate status.content unless they're different.

What actually happened?

status.content was an identical duplicate status.reblog.content

Logs

No response

Severity

I cannot use it as easily as I'd like

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

### Your setup OTP ### Extra details first installed Pleroma through OTP, then converted to Akkoma according to docs ### Version 3.5.0-0-gd9508474b ### PostgreSQL version 12 ### What were you trying to do? When trying out Elk Canary (https://elk.zone/) I noticed that reblog/repeat statuses have duplicated content, like here: ![grafik](/attachments/ab7f5c98-1281-4c9e-a9b1-365e6c808adc) URL of the depicted status: https://mastodon.social/users/KatM/statuses/109750713926989417 At first, I believed this to be a bug in Elk, but it looks like it's a problem in the Mastodon API. So, bear with me, as my web development skills are stuck in 2009. When the status in question comes in as JSON from the API, it appears that `status.content` is identical to `status.reblog.content`. Elk then assumes, this means it's a "reblog with comment" type of action and displays them both. You could argue that's Elk's problem, but (1) Mastodon seems to behave differently and (2) duplicated content is a waste of space. ### What did you expect to happen? When `status.reblog.content` is set, the API should not populate `status.content` unless they're different. ### What actually happened? `status.content` was an identical duplicate `status.reblog.content` ### Logs _No response_ ### Severity I cannot use it as easily as I'd like ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.

grafik.png

49 KiB

Fell added the

bug

label 2023-01-26 09:35:28 +00:00

floatingghost commented

2023-01-26 11:45:15 +00:00

Owner

hm, looks like this was caused by mastodon changing its implementation rather than an actual "bug" in the strict sense of the word - masto 3 filled in the content field

but i agree that we should match masto4 behaviour

hm, looks like this was caused by mastodon changing its implementation rather than an actual "bug" in the strict sense of the word - masto 3 filled in the content field but i agree that we should match masto4 behaviour