/kbin meta

4 readers

1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago

Has posting been super weird for anyone else lately? (kbin.social)

submitted 1 year ago by Xperr7@kbin.social to c/kbinMeta@kbin.social

7 comments fedilink hide all child comments

Oftentimes, I cannot see my own threads or comments unless I link them to myself directly from an unsigned out window. And then to boot, I can't see comments in my own threads. It's super frustrating rn.

you are viewing a single comment's thread
view the rest of the comments

[–] e569668@fedia.io 2 points 1 year ago (1 children)

Recently I noticed with another user that they had blocked a domain and it, for some reason, was hiding all comments in the thread despite the blocked domain being completely unrelated to the post (the post wasn't on that domain, wasn't by someone on that domain, and no commenters were from that domain).

If posts are disappearing when you're logged in but not when logged out, it should be something like that: either a language filter, federation turned off, or a blocked community you might not expect filtering it out. You can double check by unblocking domains/magazines to see if any of them return comments, though that might be troublesome with many blocked.

[–] Xperr7@kbin.social 2 points 1 year ago (1 children)

Well, shit, That did it, I can see comments properly now, thanks. Annoyed that I gotta have hexbear and lemmygrad unblocked for now though -_-

[–] e569668@fedia.io 1 points 1 year ago

If anything makes sense to you, let me know, I didn't want to get too into what was being blocked or wasn't loading, but I imagine it must be some false positive; that is to say, I assume whatever you posted did not include those domains and maybe no users from those instances posted in it. I couldn't figure out why the instance domain filter would trigger in such a case, but I didn't dig too deep into it; I guess I should make an issue but I've been holding off on making issues until 1.0 versioning happens so there's a way to say x bug happens in y version, otherwise it has been difficult so far to discuss issues between people that may be on different git shas