I cannot see some threads. Is there something wrong with my account or is is a bug?
I cannot see some threads. Is there something wrong with my account or is is a bug?
Some threads that are visible when logged out become invisible when logged in. This seems to apply to all magazines and all instances - I am not completely blocked from an instance or a magazine, they just don't show all the threads. This seemingly started relatively recently, because I now cannot open a thread that I commented on 2 days ago. However there is some possibility that it happened in the past and I just did not notice, I only go here once in a blue moon.
When I open one of the threads using a direct link, the body of the post itself is shown, it shows the correct number of comments, but the field where comments should load says "No comments".
Example threads that I don't see:
Example 1 (the one that I commented on)
Example 2
Example 3
Additionally, and I have no idea if this is related, I cannot send direct messages to anyone outside of kbin.social, the "Send message" link in their profile just sends me to a 403 forbidden page. I have no idea whether this is related or whether it's just an unfinished feature (in that case ignore this) - I only noticed now, after I wanted to message somebody that unfortunately I can no longer reply to their thread.
You're viewing a single thread.
Have you blocked anyone? There's a bug that causes certain threads, including your own, to not be visible to you outside your profile. It's caused by you blocking anyone at all iirc. Or maybe it's about blocking domains, I forgot the specifics, but try removing any and all blocks and see if that solved it.
It's fixed in the latest code iirc, but there's not been a stable release yet that incorporates the change.
Additionally, and I have no idea if this is related, I cannot send direct messages to anyone outside of kbin.social
This is correct, direct messages only work on the same instance currently. If I remember the previous discussions about it correctly, this is intentional for some undisclosed (or lost to time?) reason currently. Like, the developer has specifically added code to cause this behavior, I assume because there were worse issues with it.
Thank you, that was it! I have blocked lemmy.ml around the same time, after unblocking it the issue seems to be fixed!
The fact that the blocking wasn't 100% and lemmy.ml still sometimes showed in the feed is also a bit of an issue, but that one didn't break the site in any way, so whatever and hopefully it will work properly in the future.
lemmy.ml still sometimes showed in the feed
In what way?
Even if lemmy.ml is blocked or even defederated, its communities should remain, just not threads and comments made by lemmy.ml users. But you might still see @lemmy.ml communities show up in your feed if someone from lemmy.world or kbin.social made a thread there.
I am quite new to Lemmy and I don't yet understand specifics like this, so that may well have been it. Thanks.
lemmy.ml still sometimes showed in the feed
I think the issue there is probably that the block applies to what's in the
(some.domain)next to threads. For non-link threads, it's hidden, but it's the instance the thread was created on. But for threads that link to an article, image, video, or anything else, it's the domain the link points to. So a thread linking to a youtube video will have youtube.com as its domain. And only blocking youtube.com will hide it, not blocking the instance the thread is from.It think ideally both, the target of the link and the owning instance of the thread, should be accounted for by the block functionality. But I don't think that's currently the case.