natjms / resin

The Pixelfed client you won't get addicted to [READ-ONLY MIRROR]
https://git.nats.solutions/nat/resin
GNU General Public License v3.0
46 stars 3 forks source link

Pixelfed API doesn't return remote statuses at the /timelines/public endpoint #20

Open natjms opened 3 years ago

natjms commented 3 years ago

When you request the following two URLs:

https://pixelfed.de/api/v1/timelines/public?local=true
https://pixelfed.de/api/v1/timelines/public?remote=true

They appear to return the same results, despite the fact that as per the Mastodon API documentation, the former should return a list of only local statuses and the latter should only return remote statuses. I've tested this on Mastodon.online which seems to suggest that I'm understanding the docs right when they say "remote" statuses.

In particular, both queries look like they just return local statuses. I've also tested this on Pixelfed.social which seems to be doing the same thing. This difference isn't listed in the Pixelfed docs.

The web UI of Pixelfed allows you to access a "network" timeline that displays remote statuses, so that makes me want to believe that the API ought to provide access to the same content. It might be worth looking into how other Pixelfed clients handle this and, if I really find myself pulling out hairs over this, opening an issue on the Pixelfed repository. As it stands in Resin, both the federated and local tabs on Discover display the same content when connected to a Pixelfed instance. Presumably this wouldn't happen on a Mastodon instance but I haven't tested that at all.