Skip Navigation
/kbin meta @kbin.social V17 @kbin.social

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.

4
4 comments
  • 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.