Please Help: I’m a mod/CC for a fairly active mag on Kbin. Right now, my threads aren’t appearing for many of our users.
TellumSiege@kbin.social to /kbin meta@kbin.social – 1 points – Since Monday, I’ve had issues posting threads. I’ll get an error message saying:
We are working on resolving the issues
Over the next few days, there will be a change in server infrastructure. Temporary problems with the website's functionality may occur during this time.
...Despite the message, my threads will still post to the magazine--but few users can see them.
I’m sorry if this has been addressed before; I did a quick look at this mag and couldn’t find the exact issue I’m dealing with. I’m just wondering if this is normal ‘fediverse growing pains’ or something I need to fix on my end?
Thanks for any help. We have a massive event coming up in a week—probably going to drive a tonne of traffic to our magazine—and I’m really hoping we can find a fix before then.
EDIT: The specific magazine I'm referring to is this one: kbin.social/m/Squaredcircle
This could be this issue https://codeberg.org/Kbin/kbin-core/issues/1019 which I'm trying to gain visibility on. This thread, as well as some of the others you have posted in SC [1] [2] [3] [4], all do not show a domain. If what I've written in the issue is accurate, that means kbin.social users with any domain blocked at all will not be able to see the posts or comments. Removing all blocked domains will fix it. Right now my findings are basically posts are somehow being made with no domain, and if a user blocks any domain at all, doesn't matter what it is, that will count as true and filter it out. LMK if this helps, trying to gather as much data as I can
Here to confirm that I was having this issue too - at @e569668 's advice I unblocked a domain that I had blocked and now I am able to see a LOT more threads that I was previously unable to view in magazines. I wasn't even able to view my own threads in magazine.
It appears having ANY domain blocked erroneously filters out threads not at all associated with those domains.
Also confirming. Just unblocked what domains I had blocked, every thread giving me problems works perfect.
Edit: Should clarify, the 500 error happens still, but the threads that weren't showing up, now are.
Thanks so much for the help. I'll try to gather some evidence/anecdotes from others and get back to you soon.
And I have no idea if this helps but on Friday afternoon things seemed fine for me. I was able to post the "Edge's last match" and "Pro Wrestler Charged with Assault" threads with no issue whatsoever. Again, don't know if that helps, just want to give you as much info as I can. Thanks again.
Checking in again. Just tested what e569668 suggested and unblocked all the domains I had blocked and instantly everything works again. Can see the SQ posts you and I made, can see this one normally instead of profile stalking, can see comments, etc etc.
Given I originally thought domain blocking worked as _instance _ blocking and over the last 2 months I learned it's not, I'll live with having a few foreign-language-communities show up in All if it means everything works for now lol.
Edit: To clarify - Still getting the 500 error when trying to post, just tested on !Random again, but the thread does post, and does appear on new as I expect it to, I can see it like normal. So with domains unblocked the 500 error changes from 'fuck my life' to 'mild annoyance'.
Edit 2: And with the most wonderful timing, as I'm uploading some clips from last nights Multiverse show and typing the above edit on this comment, my streamable account gets flagged and they just killed all the videos I've uploaded over the last couple weeks. Guess I won't be posting clips after all! 🙃 This is why we can't have nice things. (and funnily enough the videos I uploaded this morning like the BC entrance, gone within seconds). Another copy of the same video posted over on Reddit by someone else, up 10h now with zero issues on a website with much more traffic than kbin, the hell lol).
Edit 3: Ok made a thread just now (6am est), no 500 error, all looking good so far.