This post has no comments visible for me (though it should have 9 as of now). I do not see it in the kbinMeta at all. I also sometimes get 500 errors in kbinMeta, particularly when sorting by new. I only found this post by clicking on Ernest's name to see activity. Any ideas (though I'm not sure if I will see any responses, heh). Not seeing anything but 200s in the network tab of inspector.
From what I've heard another big issue is that moderation actions don't get federated to lemmy anyway. Beehaw was considering (or did it already) blocking Kbin domains because for example, posts deleted by moderators here don't get deleted on the lemmy instance. So even if you do moderate it's not applied to federated instances 🙁
Ps. these are Let's Encrypt certificates. Something isn't correctly configured on the server. Failing to renew this media.kbin.social domain. I do not have the correct credentials to help out here, but I do know certbot program should NORMALLY auto-renew these TLS certificates. To avoid this issue in the first place from happening.
If not, I recommend bringing it up there. If you only bring it up here, you rely on ernest or another contributor writing it down and remembering it, which probably isn't too reliable. Better to put it on the issue tracker.
I posted in https://kbin.social/m/kbinMeta/t/509976 as well but just to make sure you see it, ernest was pinged so hopefully this will be fixed when he sees it
The good news is this was fixed in latest https://codeberg.org/Kbin/kbin-core/issues/1019 the bad news is it hasn't made it to kbin.social yet so hopefully whenever this instance is updated it will be fixed
This is actually due to the way these platforms work. When a user comments on a comment or post on their instance it will be shown on their instance. It's then sent on to the owning instance of that comment or post. That owning instance then forwards it on to all interested parties (magazine instance, commenters instance).
Any instance in that chain can refuse to forward or broadcast that message due to a block, but the users own instance will likely always show that post. Ideally they would not do that and would be made aware of a block but that is a bit of a grey area in ActivityPub implementations.
Thanks for explaining, but wow, that's really unfortunate and seems like something that needs addressing, especially since they're the biggest instance.
I thought the whole point was to have the freedom to associate and disassociate with the content of our choosing?
Is there a way to know if/when this is fixed? Because I honestly don't feel comfortable posting the content I do to my target audience if I can't properly keep the trash out.
This is a software bug. Why would other normal instances not want to know about and enforce community ban lists? That just results in a poor experience for their own users.
@adam thank you for explaining this. Am I correct to understand, then, that this is something about which we ought to approach the #activityPub devs, rather than ernest?
Ernest's comment that ActivityPub tries to federate moderation (but isn't ?why) was very interesting.
It seems to me, on the face of it at least, that moderation is a key part of any social medium.
kbinMeta
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.