For example, [email protected] has two threads pinned.
Browsing through lemmy.zip correctly shows them on top.
https://vger.app/posts/lemmy.zip/c/[email protected]
But browsing through piefed.zip does not.
https://vger.app/posts/piefed.zip/c/[email protected]
I think this might be a lemmy vs piefed API difference? Perhaps something needs to be adjusted on Voyager to support this on piefed?
That sounds like possibly a piefed bug, if the pinned posts aren’t being returned at the top.
Thanks, so Voyager is showing the posts in the order the APIs returned them? I guess I’ll play around with the APIs a bit and see if there is a difference between lemmy and piefed.
FWIW, pinned posts do show on top on piefed’s native web interface.
Yeah that’s one of the benefits of Lemmy API: it’s used for the official Lemmy UI so apps have access to the exact same data and functionality.
On piefed the official UI has special access and the API for apps is separate. Kinda makes it a second class citizen
Just a follow up, it is fixed with this pull request. I think piefed.zip has already deployed it and it is working for me now.
Thanks @[email protected] .
Great news!