Longer comments have a band at the bottom of the text with a double arrow which, when click on it, is meant expand and show the rest of the text. On mobile, it doesn't uncover all the text. Is there an option to disable this feature so that comments are not collapsed?
Have you blocked anyone? There's a bug that causes certain threads, including your own, to not be visible to you outside your profile. It's caused by you blocking anyone at all iirc. Or maybe it's about blocking domains, I forgot the specifics, but try removing any and all blocks and see if that solved it.
It's fixed in the latest code iirc, but there's not been a stable release yet that incorporates the change.
Additionally, and I have no idea if this is related, I cannot send direct messages to anyone outside of kbin.social
This is correct, direct messages only work on the same instance currently. If I remember the previous discussions about it correctly, this is intentional for some undisclosed (or lost to time?) reason currently. Like, the developer has specifically added code to cause this behavior, I assume because there were worse issues with it.
Thank you, that was it! I have blocked lemmy.ml around the same time, after unblocking it the issue seems to be fixed!
The fact that the blocking wasn't 100% and lemmy.ml still sometimes showed in the feed is also a bit of an issue, but that one didn't break the site in any way, so whatever and hopefully it will work properly in the future.
I think the issue there is probably that the block applies to what's in the (some.domain) next to threads. For non-link threads, it's hidden, but it's the instance the thread was created on. But for threads that link to an article, image, video, or anything else, it's the domain the link points to. So a thread linking to a youtube video will have youtube.com as its domain. And only blocking youtube.com will hide it, not blocking the instance the thread is from.
It think ideally both, the target of the link and the owning instance of the thread, should be accounted for by the block functionality. But I don't think that's currently the case.
Even if lemmy.ml is blocked or even defederated, its communities should remain, just not threads and comments made by lemmy.ml users. But you might still see @lemmy.ml communities show up in your feed if someone from lemmy.world or kbin.social made a thread there.
2 Things there. I was mainly talking about the kbin.social template magazines like tech or opensource but also
The other problem is that reports from kbin are not getting to other instances AFAIK so we must self moderate other instances that appear on here
I do the same for my mastodon instance. I see a user doing something against the rules via another instance their federated profile is limited or suspended from my own instance
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.
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.
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?
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 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.
kbinMeta
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.