You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you navigate to the Direct tab, regardless of whether or not you have conversations, they will not be rendered. If you log the fetched Conversation array, it turns out to be []
One more obvious culprit might be that Pixelfed hasn't implemented it yet, though I haven't tested this on any other instances so I can't be sure. Pixelfed does allow for direct messaging on the web interface, however, in the docs, it says here that endpoints that "are not applicable" return empty arrays. DMs should be applicable now that they've been implemented but it's possible the exposed API isn't up-to-date. There isn't an issue on the Pixelfed repository regarding this so if that turns out to be the case, we'll have to open one.
It doesn't appear that PixelDroid implements direct messages and the feature hasn't been requested, so that could be a bit more evidence, though it'd be worth looking into some of the other clients to make sure.
Another possibility that passes less of the blame would be that somehow our query is malformed, which would require testing it on other Pixelfed and Mastodon instances.
The text was updated successfully, but these errors were encountered:
If you navigate to the Direct tab, regardless of whether or not you have conversations, they will not be rendered. If you log the fetched Conversation array, it turns out to be
[]
One more obvious culprit might be that Pixelfed hasn't implemented it yet, though I haven't tested this on any other instances so I can't be sure. Pixelfed does allow for direct messaging on the web interface, however, in the docs, it says here that endpoints that "are not applicable" return empty arrays. DMs should be applicable now that they've been implemented but it's possible the exposed API isn't up-to-date. There isn't an issue on the Pixelfed repository regarding this so if that turns out to be the case, we'll have to open one.
It doesn't appear that PixelDroid implements direct messages and the feature hasn't been requested, so that could be a bit more evidence, though it'd be worth looking into some of the other clients to make sure.
Another possibility that passes less of the blame would be that somehow our query is malformed, which would require testing it on other Pixelfed and Mastodon instances.
The text was updated successfully, but these errors were encountered: