There's a couple things that could be happening, but I'm gonna go with my gut and ask do you have any domains blocked? There's been repeated issues with domain blocking affecting your ability to post (in fact, I had to clear all my domain blocking to properly post to kbin). This is the first thing I'd check.
The next thing would be to see if those instances or communities banned you. This seems unlikely, as it's affecting you on both lemmy.world and lemmy.blahaj.zone. The last thing could be that these communities have defederated or blocked kbin users due to past spam issues (@Technology is still blocked on lemmy.world due to this), but I haven't seen it implemented in this way before.
But I'd start with the domain blocking - 90% of the time when people have problems posting on kbin, that's the cause.
Bummer - looks like your post did show on lemmy.blahaj.zone, and I see that you got one up on @gothindustrial. Leads me to think it might be a community ban on @spookymemes for why your toy post didn't show up there. blahaj.zone was probably just slow.
Same here. When I started trying to post a few weeks ago it was intermittent. Sometimes it went through, other times I needed to "massage" the post by interacting with it (upvoting, commenting, etc.), sometimes it appeared on the local version of the magazine, sometimes just on my profile. But the past week or so it's been really bad. I gave up trying to fight with it and just made an account on a Lemmy instance to post from.
I think this might be a two way issue. I usually post on Kbin magazines from an account on Midwest.social since Lemmy has a more mature app ecosystem at this point, and none of the comments I made from that account in the last couple of days seem to have made their way over.
I have received my first comment on this post, and yes, I am unable to view it. Just the notification.
To answer the part of your question that I could read, yes I have five instances blocked. Does that prevent me from viewing comments on my own posts in other instances?
Also, this appears to be very kbin.social specific at the moment at least. I went around and checked kbin.cafe, kbin.melroy.org, fedia.io; disabled federation on each but all of them had their own domains shown for local posts. It seems only kbin.social is currently stripping domains from new posts made to kbin.social, causing the inability for any kbin.social users to view those posts if they block any domain (to clarify, this affects kbin.social posts FOR kbin.social users. You won't be able to see this issue from a remote instance, as the posts do show as the domain kbin.social over on say, fedia.io. It's only on kbin.social that posts to kbin.social are losing the domain)
Basically, this was fixed in the source code a month ago, but kbin.social itself (the only instance experiencing this issue) doesn't have the fix loaded in yet.
I don't know of every instance of course, but from the general purpose ones the order of up-to-date from most to least at the time of posting would be something like: kbin.run, fedia.io, kbin.cafe, artemis.camp (specific API branch), kbin.social.
But there's also other considerations. fedia has a double post/comment issue and a low amount of 500s. Artemis has been giving me a lot of 500s, can't upvote anymore (just reloads the page), commenting doesn't always federate. Many instance admins seem to have disappeared since 3 months ago. I'm not sure what life is like on instances I'm not actively using so there might be issues unknown to me.
Edit: the keys that I look for are localization / ui changes. "more" dropdown now has "more from domain" on updated instances. The UI for the sidebar is different, and most recently the footer is differently styled. There's also the federation list of instances page in the footer now.
I used to run an instance, and one of the reasons that I stopped was there is no good way to update it. If I pulled the source code again and recompiled the Docker it just wouldn’t start. Wiped the database and it still wouldn’t start.
This is why I still tell people Kbin is not production ready.
I was going to get involved in the development but after 4 months they still haven't merged the PR which makes it easier to onboard new developers (and also makes it easier to spin up new or update existing environments) so I've reconsidered where to spend my time. Which is a shame because when I saw kbin was built on Symfony in PHP I had very high hopes for it. I think the onslaught of new users completely overwhelmed the developer to where maintaining the instance took priority over developing it, which in the end makes it more likely to die off instead. /rant
I’m excited about the upcoming update that will roll out the API for kbin.social. Is there any updated information that can be shared about the timing of the roll-out?
It seems there's been some unexpected irl issues that have prevented ernest from properly working on the update.
However, I'm almost ready to continue on this journey, so you can expect that in the near future, there will be a banner with information and the update date of the instance and release. After that, we will work on avoiding such longer development downtimes in case of my absence.
i update kbin.run to stay in sync with the most recent commit to the dev branch on a regular basis, although the update frequency is much lower now compared to 4 months ago... it's a "bare metal" install (no docker), so i made a very simple shell script to update it. half the time no one notices until they refresh the page or get inadvertently logged out due to a backend cache getting cleared. you're welcome to try it out if you'd like.
All of your posts went through, there's just a bug with sorting. You should delete the duplicates. Unless perhaps the duplication is a commentary on the lack of moderation?
Coming from another instance, I really can’t wait for kbin to fix this issue. Every time I see spam, it’s from kbin because of the lack of moderation. I don’t understand why only the instance admin is able to moderate.
I like so many things about kbin, but definitely don't need another unmoderated spammy site to visit. I check back every few weeks, and nothing seems to improve.
There's reason to be hopeful now. Ernest has posted an update about instance moderators who will be able to moderate mags that are either admin owned (and so otherwise wouldn't have other moderators to moderate them) or for those mags which are abandoned.
kbinMeta
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.