16
submitted 1 year ago* (last edited 1 year ago) by TellumSiege@kbin.social to c/kbinMeta@kbin.social

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

you are viewing a single comment's thread
view the rest of the comments
[-] floppy@rabbitea.rs 1 points 1 year ago

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)

[-] TellumSiege@kbin.social 2 points 1 year ago* (last edited 1 year ago)

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.

[-] e569668@fedia.io 3 points 1 year ago

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

[-] TellumSiege@kbin.social 2 points 1 year ago

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.

[-] GeekFTW@kbin.social 2 points 1 year ago* (last edited 1 year ago)

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.

load more comments (8 replies)
load more comments (13 replies)
load more comments (14 replies)
this post was submitted on 20 Aug 2023
16 points (100.0% liked)

/kbin meta

5 readers
6 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