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

4 points

It sounds like you might be having some overlapping issues. Since the “error on post” thing started happening, I’ve noticed that new posts won’t show up in the default “hot” ordering. I assume that this is a sorting bug and they show up at the bottom of it. This was also happening when I first joined kbin, although the error page on post thing wasn’t happening then.

The workaround seems to be to go back to the magazine’s main page after posting, and sort by “new”. Your post should then show up at the top. Upvote your own post, and then when you go back to the default “hot” ordering it should show up at or near the top, as normal.

Hopefully this fixes at least one of those issues. Good luck with everything.

permalink
report
reply
1 point

Are they not appearing on other instances? In which case it may be this bug: https://codeberg.org/Kbin/kbin-core/issues/875

If they aren’t appearing for users on your instance that’s probably a different problem entirely.

Also if you’re posting from kbin.social and the magazine is hosted there, that isn’t the same issue either (it’s only if somebody from a different instance posts to a magazine where that bug occurs)

permalink
report
reply
2 points
*

Going by who boosted and upvoted my threads, here’s what I’m seeing:

Last night, our ‘Collision’ thread seemed only visible to people on Kbin…but not everyone. One of our other top CC’s couldn’t see the thread and they’re on kbin.social, the same instance our mag and my account were created on. From what they’ve said, they’re struggling to see anything I create – that includes threads and comments. Here’s what they said about their own issues when they tried posting a thread:

Ironically, I actually did get the error lol.

Got the post all pre-typed out and such, titled, tags, etc. Hit post, error. Panicked, thought I lost it all, but didn’t. Tried 4 times, same error every time, said fuck it and I’ll give up. Then noticed 4 threads on my profile (I deleted the other 3 myself) and this thread still doesn’t show up for me on the magazine. Tried to click your comments and can’t even see em normally on the topic that does open, hell I’m responding to you via your profile page right now. (same with your post to kbinmeta just now, I see it, but i cant see the comments on it). First time it’s happened to me during thread creation however (instead of the typical occurrence from when I block someone).

On Friday night, our ‘Rampage’ thread was visible to people on other instances. The thread was boosted and upvoted by users on lemmy.world, feddit, kbin, and sh.itjustworks. But I don’t think that user–or some of our others–could see it either.

Let me know if I can gather any more info for you. And thanks for the help. In cases like these, I really wish I was more tech savvy.

EDIT: I created a new thread on m/SC about an hour ago. It has 7 upvotes yet not one from Kbin (excluding myself and GeekFTW, who found the thread via my profile). It seems like one thread I create will be viewable by people on Kbin, the next not so much. It doesn’t make much sense to me.

permalink
report
parent
reply
3 points

One of our other top CC’s couldn’t see the thread and they’re on kbin.social

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

permalink
report
parent
reply
2 points

Hey, a few updates on the issue:

One of our mods tried a “test” thread to see if they received the error. They did at first, but was able to fix it using @Cacheson ’s advice. Here it is in their words:

Yeah, I got the error message, too. Sorry for taking so long.

Quick edit: I tried the fix mentioned by @cacheson in the thread you linked and my Test thread shot straight to the top of the second page of “hot” on my main feed.

Once they were able to create the thread, I messaged one of the users who was experiencing the issue and they were able to view the post. Following your advice seemed to be what helped them. Again, here it is in their words:

Indeed I can! Apparently my blocking of explodingheads was the issue! Don’t know why but I can see everything! Even the dirty secrets!

Their issues seem to be solved. Unfortunately, I’m still seeing the error when I post. FWIW, I have nothing blocked at all. And I’ve tried posting on two different devices with two different browsers (no clue if that helps in any way; just wanted to mention it in case it does).

Let me know if there’s anything else I can do on my end. Thanks as always.

permalink
report
parent
reply
3 points

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.

permalink
report
parent
reply
2 points

Also, there’s a PPV starting in 15 minutes so I’m going to be a bit distracted tonight. Tomorrow I’ll give that codeberg thread a good long read and report back anything I can. Just wanted to give you a heads up.

permalink
report
parent
reply
2 points

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.

permalink
report
parent
reply
4 points
*

(Still replying via stalking your profile lmao)

Hey everyone, the other person Tellum is referring to here.

I do not see said Rampage thread. For further info for yourself, the last thing I see posted on the mag under newest is my own thread (the thekla/bayne/shirakawa/may one). No activity appears after that.

permalink
report
parent
reply
2 points
*

Yeah, that’s weird.

FWIW, @GeekFTW and I are responsible for 70-80% of the posted content on our magazine. If both of us are having this issue then it’s going to be a big problem for our growing community.

I know these things are tricky and take time to solve. I know this won’t be fixed overnight. But next Sunday is one of the biggest pro-wrestling shows in history and the last thing I want is for some of our users to not be able to experience that with us. A few of us have gotten to know each other pretty well because of this place. It’d be heartbreaking if we can’t all come together during that epic show.

permalink
report
parent
reply
1 point

Incidentally my comment probably won’t be visible from instances other than mine and kbin.social until somebody interacts with it (I’m not sure if this reply itself is sufficient, usually it needs somebody on kbin.social to interact to make it visible elsewhere)

permalink
report
parent
reply
4 points

For what it’s worth your post has been federated to my lemmy instance

permalink
report
reply
4 points

Appreciate hearing that. Weirdly enough, the posters who’ve brought it up are actually Kbin users…

permalink
report
parent
reply
3 points

I’ve been seeing them

permalink
report
parent
reply
3 points

The error occurred again as I posted this. So there’s a good chance many won’t see this either :/

permalink
report
reply
2 points

I’m seeing this and on kbin

permalink
report
parent
reply
2 points

Thanks. It’s weird. I post discussion threads throughout the week (for pro wrestling shows) and all week I’ve had people bring it up. Even make other ‘discussion threads’ because they couldn’t see mine.

permalink
report
parent
reply

/kbin meta

!kbinMeta@kbin.social

Create post

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

Community stats

  • 1

    Monthly active users

  • 1.3K

    Posts

  • 13K

    Comments

Community moderators