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.
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 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.
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.
not sure if it answers your question but https://fba.ryona.agency/ let's you search for who is blocking who. It currently says 22 instances are blocking or otherwise limiting interaction with kbin.social, and that kbin.social isn't blocking anyone.
Sadly I haven't yet, the same think happens to me, random news videos autoplaying, even when not on screen yet. I'm fairly confident there's no setting to turn off video autoplay on kbin. Sadly even if you tell Firefox to not autoplay videos the videos continue to play, the Firefox mobile settings seem to be limited in that respect though.
I wonder if turning it of on the desktop browser site settings and then syncing will fix it.
Hrmm I think I have automedia preview set to on. I've turned it off and will see if this fixes it. I say think as the UI for the kbin page settings isn't super clear what's on and what's off ..
Ernest has previously said that this will be an upgrade to address several issues, such as those related to federation, spam and lack of moderation tools.
API stuff is listed in the 'merged pull requests' section (quite a few times), so unless I'm mis-interpreting what that means, I think the API should be going live as long as this downtime is for the updating of the instance!
This will help a LOT with people seeing /kbin as an option ... the mobile webpage is pretty fantastic, but I'm really looking forward to switching to the Artemis App as my daily driver.
I don't recall Ernest explicitly saying so, but the API is live on the artemis.camp instance, so hopefully it's in a state where it can be implemented as part of the core kbin code base. Perhaps the kbin codeberg can shed further light on this question.
API is part of the kbin code base (on latest develop branch). For example https://kbin.melroy.org also have API enabled. But kbin.social is still not upgraded until this day.
Not sure if anyone is getting this problem or whether it is a KBin issue or a browser issue.
I get an issue when browsing on mobile (Firefox) and loading magazine headers under all. If I scroll down and load a few additional magazine headers, click on a magazine title to view it and then hit back to return to the list of magazines, the list does not return me to the place I was at in the list.
Instead it truncates the list back to first loaded magazine headers and leaves me viewing the random details normally positioned at the bottom of the all list. To get it to load more magazine headers I have to scroll back to actual bottom of the listed of initially loaded magazine headers. It then starts reloading headers as normal but I then need to scroll and reload all subsequent magazine headers to get back to my position in the list.
If someone continues to harass you after you've blocked them, it's because they're lonely and want your attention. I've found that offering comforting and condescending words while reverse spamming them with Eleanor Rigby seems to end the harassment quickly... especially when they realize that they can't block you properly either.
I think there's something to be said for it being public. If someone's downvoting all of your content for no reason without engaging with it, that's obviously not someone worth your time and it may be a decent idea to just block them. I could also imagine some communities making it explicitly against the rules to downvote constructive comments for no reason, for instance.
At any rate, my understanding is that the actions must be at least publicly accessible in order for federation to work, so the only thing that Kbin could do is simply not openly display that data. Perhaps making it less accessible would reduce the temptation to look, but it'll always be available to anyone who truly wants to see.
Yes, on par I lean towards it being a good thing as publicly available information rather than shadowy mud-slinging. I had one post downvoted by someone who apparently has done nothing else before or since, which takes a bit of the sting out of it. There will probably be debates about it at some point, and probably the occasional tit-for-tat attacks around the place, but overall I think it does link a bit more identity to the person who does the up- or down-voting which creates more of a community feel instead of hiding behind total anonymity.
kbinMeta
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.