User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender @jeder@miau.jeder.pl
3y
why do people willingly use mastodon with its fucking garbage way to show replies and threads
⭐3
5
2
0
3
User avatar
kuna @kuna@social.hollow.capital
3y
@jeder mastodon itself is one thing, but clients that use masto api flatten everything even when accessing a backend that understands threads (such as when viewing an akkoma account through tusky)
1
0
0
0
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender @jeder@miau.jeder.pl
3y
@kuna yeah so i think that's just inherent to mastodon and making people just do whatever official frontend does
2
0
0
0
User avatar
kuna @kuna@social.hollow.capital
3y
@jeder Now that I think of it, it should be possible to piece together a tree of statuses by using "GET /api/v1/statuses/:id/context", but the frontends don't do that. Part of the problem might be that the masto api spams lots of info pointlessly (like full account info with bio for every status), and people might want to avoid making too many requests for this reason.

docs.joinmastodon.org/methods/statuses/#context
1
0
0
0
User avatar
Jeder neocat_floof_googly_woozy neocat_flag_agender @jeder@miau.jeder.pl
3y
@kuna yeah i don't get why both masto and misskey apis don't give just enough info, and instead are so stupidly verbose
⭐1
0
0
0
1