A few days ago I downvoted someone's comment, and the next day I happened to notice every single comment I've ever made had at least one downvote. All from the person I dared to downvote the ONE time. I straight up asked why they did it, and they seem to think I'm an "obvious" troll account that "apparently just exist to...
While that's definitely a notable downside, I think the upsides outweigh it.
For one, being able to see upvotes & downvotes seems to have made a lot of people a bit more thoughtful with handing them out. This obviously isn't the case for everyone — there's still a good bit of downvoting people for disagreeing with the hivemind — but I and others have observed that downvote quality is a lot better here on kbin.social, and I think that vote visibility is a big part of that.
It's also just transparency on kbin.social's part. If votes federate, anyone can set up an instance to view your votes or just go to one that shows them. Someone could literally make a website listing downvotes throughout the fediverse, and there's nothing stopping them. Kbin.social is being transparent about the fact that votes on the fediverse can be accessed by the public, and I have no issue with that.
@ernest Happened again while viewing this post. Couldn't vote or boost the post, the crosspost, or any comments. Alongside the things from before, changing the comment sort seemed to fix the problem.
I'm not sure what the issue is, but it doesn't seem to be specific to any thread or page. Just that sometimes, all voting & boosting on a page just doesn't work.
I've been thinking a bit about this post regarding #Mastodon's responsibility to be compatible with the #threadiverse (#ActivityPub thread aggregators like #Lemmy & #Kbin). Right now, a thread from Lemmy or Kbin usually federates to Mastodon with truncated text and a link to the actual thread. However, many want Mastodon to be more compatible with threads so that the people over on Mastodon interact with the threadiverse more.
I was initially in agreement as a Kbin user. But having given it some thought, I think this is an unwise approach that'll only serve to overcomplicate platforms on the #fediverse. Yes, people on Mastodon should promote other parts of the fediverse (and vice versa), but complete interoperability shouldn't be expected of every platform.
As much as many would like it, you can't have long-form video from PeerTube, images from Pixelfed, threads from Kbin, blogs from Writefreely, etc. all neatly fit in a microblog feed. These are different formats made for different platforms, and the people making them are expecting them to be interacted with in completely different ways. When someone makes a thread in a Lemmy community, they're probably expecting that the people who are going to see and interact with the thread are people that want to see threads and are thus on a Lemmy instance (or another thread aggregator). If someone from Mastodon were to interact with it as if it were a microblog post, there'd be a big mismatch. People interact with microblogs differently than they do with threads — that's why they're separate to begin with. You don't see everyone on Twitter also wanting to use to Reddit because people who want microblogs don't necessarily want Reddit-style threads, and vice versa.
The other option, then, is to separate these different formats into different feeds or otherwise make them clearly distinct from one another. Kbin does this by separating threads and microblog posts into two tabs. While you can view both in the "All Content" tab if you'd like, they're styled differently enough that it's very clear when you're looking at a thread and when you're looking at a microblog post. This distinction lets users treat threads like threads and microblog posts like microblog posts, which is really helpful since the two formats serve different purposes and have different audiences. This option — clear distinction — is a great way to solve the conundrum I've been talking about… if your platform is meant for viewing all these different kinds of content to begin with.
And that's what it really comes down to imo. Mastodon is a platform for microblogging. Most people go to Mastodon because they want a Twitter alternative, not a Twitter alternative that's also an Instagram alternative and a Reddit alternative and a YouTube alternative. Even if you put these different content types in separate tabs, it would inevitably make things seem more confusing and thus raise the barrier of entry. Add a Videos tab to Mastodon to view stuff on PeerTube, and people are inevitably going to go, "Wait, what's this? Is this like YouTube? I thought this was just a Twitter alternative! This all seems too complicated," even if you tell them to ignore it.
It's probably best to leave Mastodon as it is: a microblogging platform that has some limited federation with other formats. The way Kbin threads currently display on Mastodon is fine. In fact, when I post a Kbin thread, I'm expecting it to be viewed via a thread aggregator. If people on Mastodon were part of the target audience, I would've made a microblog post.
Now, if you want to make something that lets you view everything on the fediverse via different tabs, feel free. As aforementioned, Kbin supports both threads and microblogs, though it comes with some challenges (e.g., trying to fit magazine-less microblog posts into Kbin's magazine system). However, this doesn't mean every platform on the fediverse needs to seamlessly incorporate everything else. I'd love people on Mastodon to promote and even try out Lemmy & Kbin more, but that doesn't mean Mastodon needs to also become a thread aggregator.
The point I'm trying to make is that you don't have to be able to read non-microblog stuff (Kbin threads, PeerTube, Writefreely, etc.) on a microblogging platform and that it's probably best for Mastodon to not have that functionality. Many people on Mastodon are going there for microblog posts, not threads. They want a Twitter alternative, not something that's also a Reddit alternative. Conversely, people on Lemmy & Kbin aren't making threads for people on Mastodon to view and interact with, as they're platforms for different types of content.
If you want to be able to cleanly view both threads & microblog posts, there are platforms that allow that, but I don't think Mastodon needs to or even should be one of them. If you make Mastodon support all these kinds of content from all these different platforms, people who go to Mastodon for a Twitter alternative will wonder, "Wait, why is there stuff from the Reddit alternative? Wait, I can see things from the Instagram alternative too? Why's that? And I can see full blog posts?" Mastodon, being an introduction to the fediverse and sought after as a Twitter alternative, shouldn't do all of that.
@carturo222 I didn't mention it due to a lack of familiarity, but if Friendica serves that purpose, that's great! People who want to interact with all of the fediverse with a single account should use that or a similar platform. The thing is that people are starting to advocate for everything to do what Friendica does — e.g., for Mastodon to be able to seamlessly interact with non-microblog stuff in the fediverse — and that's just not what Mastodon is trying to do.
I disagree. Yes, Mastodon is the first ActivityPub-based platform for most people, but that doesn't mean it's obligated to be an app for all social media on the fediverse. Most people go there for microblogging, not to see threads from Kbin or images from Pixelfed or videos from PeerTube. They just want a Twitter alternative, and Mastodon should provide that imo. If people already view the mere act of selecting an instance as enough of a barrier to prevent them from trying it out, you're going to lose more people if you complicate things by shoving YouTube-style or Reddit-style content into the platform.
This also makes me think that it wouldn't be very effective way of supporting other platforms. You're not going to get much engagement from Mastodonians on other types of content because those types are just not what they're there for. At best, you'll get people commenting on Lemmy threads thinking that they're microblog posts and thus not actually understanding the format of the thing they're replying to.
I get that Mastodon has most of the people on the fediverse, but that doesn't mean it's on Mastodon to feed activity to other platforms. Even if it wanted to, I don't think it could.
Even if we ignore the issues, I just don't think other ActivityPub platforms would benefit much from this. People are going to Mastodon for microblogs, not all the other stuff. Even if you give people the option to view PeerTube videos from Mastodon, if that's not what they're here for, then most of them won't bother. We see this on other platforms. Even on Kbin, which has great support for the microblog format with a unique tab and all, a ton of the people who came here for a Reddit alternative just don't bother with the Twitter stuff.
And again, that's ignoring all the downsides of implementing this stuff. Add all of this non-microblog stuff, and more people who are searching for a Twitter alternative will disregard Mastodon as too cluttered and confusing. People already do that because of needing to pick an instance, and yet more do because they can't immediately grasp federation. Additionally, those who do interact with, say, a Lemmy comment through Mastodon won't be aware of the context behind it being in a Lemmy thread that's part of a community and which has different functionality (e.g., downvotes & a title). You could have a badge to indicate that it's from Lemmy, but then you worsen the problem of people getting to Mastodon and going, "Wait, wtf is this? Why is this platform so confusing?"
And let's say Lemmy/Kbin threads did get some great surge in activity from this. You'd end up with a significant portion of activity on these platform being people using a Twitter alternative, which I don't think people looking for a Reddit alternative (or even people already on these platforms) would find desirable.
Since you brought it up, I think Lemmy's handling of microblogs is a good example of what I mean, as I don't think Lemmy should be handling microblogs at all. Lemmy has to assign a title to something that doesn't have one and downvotes to something that doesn't accept them. The result is that several Kbin magazines, when viewed from Lemmy, are dotted with posts that obviously aren't meant to be there and which would clutter the thread to death if microblog usage on Kbin increased. And for what? When I make a microblog post, I don't intend for it to reach people on Lemmy, as that format is not what most people on Lemmy are interested in. Likewise, most people on Lemmy aren't trying to reach people on the Twitter alternative and might prefer not to. Lemmy supporting microblogs doesn't really do much, and the same would go for Mastodon even given its large user count. People just won't be interested.
This isn't a hurdle because people typically aren't going to the fediverse with the idea of "I want a single app for all my social media." That's not how social media works outside the fediverse, so it's not really going to be a surprise that the Twitter replacement is a Twitter replacement and not one for 5 other platforms. If someone really wants to view Reddit-style threads, they're straight up better of making an account on a different platform (just like they would make a different account for Reddit) because Mastodon is a microblogging site.
Even the best attempt to incorporate all these different types of content into Mastodon is going to further complicate the platform and make more people dismiss Mastodon as too complicated of a Twitter alternative. This isn't a situation where there's no harm at best. And the potential benefit? Lemmy comments having the occasional Mastodon user?
Mastodon itself is a good enough introduction to ActivityPub without needing to make it support other things. It shows how people on different servers can share & interact with a pool of media through the same protocol. When people learn about other platforms on the fediverse, they can go check those out. Just promoting the platforms will do the job fine without complicating people's entry into the fediverse.
I've been using Kbin for a few months now and I didn’t really feel the need to set my #feed to anything besides "Subscribed". I can guess from their names what the "All" and "Moderated" feed are but I have no idea what the #favorites feed does. I've seen that the recently added #collections also use the word "favorite" when...
@Gordon_Freeman There isn't a crosspost button, but if two threads are similar, they'll show as crossposts of each other. I'm not sure exactly what the criteria are, but from what I can gather, two link threads will show as crossposts on Kbin if they have the same link. Otherwise, they need the same title (and maybe the same photo?).
@Gordon_Freeman Agreed, though it would be cool to have a button that you can click to make a crosspost. Maybe it'd send you to the thread creation page with certain things filled out to make it a crosspost.
In the past week or two, I've been making a lot of updates to my Kbin userstyle, idkbin, to account for all the new features Kbin has been getting. This weekend, I had a bunch more motivation to work on it, so I decided to make a bunch of additions to the userstyle and make the next version 1.3.0 (as opposed to 1.2.7, which...
@Damaskox I get them every now and then trying to upvote, downvote, or boost something, but it's extremely random. Usually, I find that going to the activity tab and upvoting from there helps
I've thought the Magazines page has been messy for a while now, though with collections now also being on the same page (at least for the time being), it's starting to get very out of hand....
Another update to my #kbin userstyle idkbin (now at 1.2.6.1)! The "new comment" marker recently added by Ernest is now stylized by idkbin (mainly to work with rounded edges), and a bug with borders has been fixed. #kbinmeta#kbinstyles
I've noticed that a lot of people on the #fediverse aren't particularly welcoming to those who don't initially get it or have trouble with it. You'd think that if multiple people say they have trouble picking an instance, it might be a genuine barrier to entry that we need to consider when introducing them to the fediverse. But no, instead of suggesting an instance to get rid of that barrier everyone gives unhelpful advice like "just pick one" or "it's not that hard." We'd have a much easier time getting people on the fediverse if there weren't so many people with this attitude of "the fediverse is simple, and the people who don't get it are lazy and should try harder."
@wizardbeard I'd argue that telling people to join largest (or at least a larger) instance isn't a bad thing. If I was telling someone to join Kbin, I'd tell them to just pick kbin.social. Later on, once they get accustomed to fediverse and understand the idea better, they can go to a smaller instance if they want
(e.g., if it's focused on a topic you like, it has features or moderation policies you prefer, or you just want to take some load off the larger instance). Having people initially go to larger, more established instances — where the experience tends to be more approachable due to more active hosts, more old content being federated, a larger community within the instance, etc. — greatly reduces the barrier to entry.
And the danger of a lot of people on a single instance is really exaggerated. If things go badly on, say, a Lemmy instance that most people are on, they can just move to another one with the same features, same UI, and similar access to content. It's not like Reddit or Twitter where moving means you're missing out on a ton.
You're right that it's usually better to be the change you want to see as opposed to simply criticizing others, but I think it's still important to discuss how we introduce people to the fediverse.
That's definitely a good point in the case of a mass exodus like what happened with Reddit. But even in those situations, I don't think this means we need to direct people to tiny instances. Lemmy now has a bunch of solid instances (lemmy.world, lemmy.ml, sopuli.xyz, sh.itjust.works, lemm.ee, lemmy.ca, etc.), so if some mass immigration to Lemmy were to happen again, you could say something like the following:
"Pick lemm.ee, sh.itjust.works, or lemmy.world; doesn't matter too much since they're all decently large instances with good moderators."
Saying something like this:
Narrows the options down to a small few that don't really differ for the new user
Leads them to an established instance with a lot of people, making them more likely to stay
Splits people between instances so we don't get instance slowdowns, shutdowns, etc.
I think it'd be more effective to just tell them an instance to choose. If someone asked me how to pick a Lemmy instance, I'd say direct them to a large, general instance: "Just sign up on lemmy.world [or some other instance]; it's a large instance with good moderation, and you can figure out if you want to switch to a different one once you've gotten more acquainted with the fediverse." My idea here would be to just get them to try it out without lingering on the question of which instance to choose, as it doesn't really matter for newcomers when we're talking about large, general-purpose instances.
@Mpwg Yeah, unfortunately a lot of people are quick to dismiss the fediverse if they don't get how to pick an instance. That's why I think it's important to get them on an instance quickly and get into the nitty gritty later. Mastodon has a lot of decently large instances
tmk, so I'd just suggest mastodon.social or another such instance. Trying the fediverse at all is much more important than picking the right instance from the get-go.
Right now, downvotes (reduces) don't federate to (and from?) Kbin instances. This lack of federation makes the downvote counter really inaccurate—a comment that looks like it's +10 might be -15 when you look at it from lemmy.world....
This is a good time to start a discussion on how it should work on kbin.social
A while back, I made a thread on /m/AskKbin about this. While it's not solely kbin.social users, there's still a lot of good input, and you could use KES to sort through those who are and aren't on the instance if you want. My two cents are that it's important for downvotes to exist, be federated, and be shown separately so that (A) people can easily express that they feel something doesn't helpfully contribute to the discussion and (B) similar expressions from other instances aren't drowned out.
Downvote federation only applies to remote threads from other instances, without affecting local threads
To be clear, what exactly do you mean by this? Does this mean that downvote federation is one-way (i.e., that downvotes federate from Kbin instances but not to Kbin instances)?
At the moment I personally am a fan of the limited downvote federation because I do think it acts as a hivemind barrier;
I think it's a lot less straightforward than this. While it definitely drowns out the "hivemind" of the wider fediverse, it also creates a bubble within your own instance. If a lot of people outside of your instance think you made a bad comment but few inside your instance do, limited downvote federation creates an inaccurate representation of what people think.
Additionally, having downvotes but limiting their federation makes them extremely unintuitive and only serves to further confuse new users. It's actively misleading—you'd think that if you see 0 downvotes that nobody clicked the downvote button, but that might actually be 5 people or 10 people or 30 people. At least if you don't have a downvote counter at all, it's clear that downvote functionality just isn't recognized on the instance. I'd much prefer that over a straight up incorrect counter.
Overall though, I think the problem is how the downvote was used (on Reddit, at least) was not conducive to discussion.
I agree that there's a big problem with how downvotes are used. I personally use downvotes if something is:
spam
straight up hateful
completely off-topic
a nonsensical take that the poster doesn't support
In other words, if something isn't a reasonable contribution to the discussion, I'll likely downvote it.
However, lots of people seem to use the downvote button as a disagree button. I see this less on kbin.social than I do on other instances, and that could be a potential reason to not federate downvotes. If downvotes are used differently on kbin.social than on other instances, then I can see it making sense to not lump them all together. However, that only makes sense if people on kbin.social aren't using the downvote button as a disagree button (which they are, just less so than on other instances). And even still, there's the problem of an unfederated downvote counter still being misleading.
Rambling aside, I see three ways of handling this:
Remove the downvote button entirely.
Remove the downvote button, but replace it with reactions that people can use ("This is spam," "This is hateful", "This doesn't contribute to the discussion," etc.). If other instances adopt this set of reactions, reactions from those instances could federate.
Keep the downvote button and federate downvotes.
I don't like #1 very much because then you don't have a great way of indicating spam, hateful posts, unhelpful comments, etc. outside of reports that only moderators can see. #2 seems really nice, though both it and #1 come with the downside of filtering out negative feedback from instances with downvotes. #3 is also good, though it comes with the problems of downvote misuse.
I see where you're coming from, but this to me seems more like a property of the fediverse than an issue with Kbin in particular. Right now, anyone can make an instance and choose to show downvotes. Someone could make their own instance, gather downvotes federated from other instances, and make a list of who's downvoted who. Being on an instance that doesn't show downvotes doesn't hide your downvotes from everyone — just you and others on instances that don't show them.
On this end, I feel that Kbin instances are just being transparent about the publicity of your votes. If anyone can see your downvotes just by looking at an instance that shows them, I think it's important that people are aware of that. Showing public votes is sort of telling you, "Hey, people can see how you voted on the fediverse," and that's preferable to pretending that nobody can see them.
Obviously, if my instance was sending my IP address off to other instances, I would get off that instance. However, downvotes are different situation. To my knowledge, for votes to work and be somewhat reliable, instances need to have a user attached to each vote. It would be very problematic if an instance was sending userless votes and other instances were just accepting them without issue. Nothing about the fediverse requires sending my IP off to other instances, whereas votes need to have corresponding users to be trustworthy.
Kinda? Your example wasn't really an exaggeration of the situation with downvotes but a different situation entirely, so it didn't really address my point. Again, as long as there are downvotes on the fediverse, the people behind them will be visible to anyone who wants to know just by looking at an instance that shows them. Thus, being on an instance that doesn't show who you downvoted doesn't make your downvotes more private than if you were on an instance that did.
I 100% get being worried about people seeing who you downvoted, but in that case, I'd suggest being on an instance that just doesn't have downvotes. Those exist, and I've seen plenty of people who prefer things that way.
Understandable. I don't view showing downvotes as weakening filters—I see how it could deter downvoting to some extent, but in my experience, it leads to people handing out downvotes less freely and when it's more justified as opposed to not downvoting at all. Nevertheless, I see where you're coming from, and I want to stress that I think it's completely fair to not want people to see if you've downvoted them.
Note: I don't think defederating from an instance prevents them from seeing your content (according to this thread), so I'm not sure if defederation would make your votes private.
Like you mentioned, that could be interesting for specialized instances used by a small group of people, but that wouldn't work for any general instance due to the vote counters being really unintuitive. If an instance were to do that, I imagine they'd also want to have something you can click that shows how many votes were local, how many were from other instances, how many were blocked, etc.
If you want to get the mods to take something down, that's what the report button is for. Downvotes shouldn't also play that role, especially if they stay as downvotes. That down arrow is inevitably going to be used by a lot of people to express mere disagreement.
That's not really a culture I want to be fostered here on kbin.social. Kbin instances are part of the wider fediverse, and there's nothing about someone on kbin.social that makes their vote more important than someone else's vote. If Kbin had a reaction system (like I mentioned in another comment) instead of downvotes, then not federating downvotes would make more sense, as specific "this is spam" or "this doesn't contribute to the discussion" reactions are more useful than just a down arrow. But the system we have right now is extremely unintuitive to new users and promotes a culture of "Eh, downvotes from people on other instances don't really matter. What's important is what people who are arbitrarily on my instance think."
If you really want to know which votes are local and which ones aren't, it'd be much better to either
have an indicator next to each user in the activity tab showing whether they're local or not, like what KES does with threads & comments, or
have something you can click that lists the numbers of local votes and remote votes separately.
I responded in another comment of yours, but I'll also respond here for the sake of visibility.
We on kbin have not developed a knee-jerk "downvote everything I disagree with" behaviour that reddit had and lemmy.world is starting to have.
I completely agree with this. From what I can tell, public voting has made people on kbin.social much more reserved with their downvotes — tending to only use them for spam, hate, off-topic, or noncontributory posts and less for just disagreement — without having the risks that come with a complete lack of downvotes (i.e., not having a quick way to give negative feedback on posts that are off-topic, noncontributory, etc.).
Not federating downvotes from much bigger instances allows us to develop our own culture here on kbin without it being buried in an avalanche from elsewhere.
This is a good point, but there are a lot of issues with not federating downvotes. Yes, not federating downvotes DOES help to emphasize the downvoting culture on kbin.social, but it also means that the downvote counter is misleading and unintuitive. New users would reasonably think that, like the upvote counter, the downvote counter represents anyone who's downvoted your post (outside of people on defederated instances). Having downvotes act like they do right now makes kbin.social less approachable and more confusing to new users.
Also, as long as we're using the same system as other instances, I don't want to push the idea that negative feedback from other instances doesn't matter. A downvote is ultimately a downvote, whether it's from kbin.social, another Kbin instance, or a Lemmy instance. The last thing I want is for the main Kbin instance — the one to which many will default — to have an exclusionary culture.
If we don't federate downvotes, I think we'd be better off just ditching downvotes entirely and instead having something more conducive to how we want instant negative feedback to be used. As I've mentioned in other comments in this thread, it'd be great to have a set of reactions people can use. "This is spam," "This is hateful," "This is off-topic", "This doesn't meaningfully contribute to the discussion," etc. would be a much better system for promoting the voting culture we want here on kbin.social. And if other instances adopt such a system, we could federate those reactions with them as well.
It definitely is to some extent, and voting culture isn't a huge part of why people go to kbin.social. Kbin.social is the main Kbin instance. If someone prefers the Kbin's UI to Lemmy's or wants to have microblog support, many will just default to kbin.social. I came here because I thought Lemmy looked ugly and Kbin looked really nice.
When you're introducing the fediverse to people, a lot of people are just going to go to the default instance, and it's honestly good advice to tell people to just do that to start out (lest they turn away from the fediverse entirely due to not being able to make a choice). Voting culture has nothing to do with that. Just because someone's on lemmy.world doesn't mean their downvotes are worth less than ours, and just because someone's on kbin.social doesn't mean they don't just hand out downvotes in order to disagree.
Out of curiosity, how would the current system be preferable to specific reactions? The whole idea of "we should only count downvotes on our instance" only makes sense if everyone on our instance is using downvotes in a more reserved manner, which isn't the case for everyone. Different people on kbin.social use the downvote button in different ways, and that'll be even more so as the instance grows. If we really want to preserve this voting culture we have, wouldn't it be better in every way to replace downvotes with reactions specific to how we'd want downvotes to be used?
Definitely agree that Ernest has a ton to do and implementing a whole new system shouldn't rlly be the top of his priority list. If it's too impractical, I'd prefer that downvotes just federate instead of the unintuitive system we currently have, but I've already discussed that at length.
Whenever I try to view the threads page of newcommunities@lemmy.world (i.e., https://kbin.social/m/newcommunities@lemmy.world), I get an error. It's only kbin.social where this happens, and it's only the threads page of this specific community. I can view the microblogs, the people, and even individual threads, but the threads...
I know there's block, but "block" currently blacklists the entire magazine. If I click on it, it wipes all the threads on /all/, prevents me from looking at threads on the magazine landing page and all comments in the threads should I venture in. A "filter" would be a soft block that just clears it from my feed on the main page....
I think it'd be simpler to just change the block button so it does that. Adding a new "filter" button would lead to newcomers being confused on what the difference is. Besides, I don't think there's much benefit to being completely unable to view a magazine.
Made a small update to my userstyle idkbin following the recent #kbin update. Colors the user follow & block buttons + some other fixes. #kbinmeta#kbinstyles#kbinMeta
I've noticed that when I'm browsing microblogs on Kbin, I see very few favorites (upvotes) on posts even when there are tons when you look at them from Mastodon. For example, this post doesn't seem to have any favorites, but look at it from Mastodon, and you see over 120. In general, federation with Mastodon is really...
As someone on kbin.social, I'm not seeing it. I saw a comment in a similar thread saying that moderation done on Kbin doesn't federate to Lemmy instances, and I think that's the culprit here. @ernest (the Kbin dev) is working towards a full release, and I hope that it might fix this issue—or at the very least, that it's dealt with shortly after.
EDIT: Yeah, I looked at @science from lemmy.ml, and my God is it awful. This really needs to get fixed ASAP.
I moderate @mcsuggestions, and today, I noticed that my comments on the two most recent threads didn't show up when I was logged in. After some experimentation, I figured out that whenever I had any domain blocked, all comments on those threads disappeared. From what I can tell in this magazine, others are experiencing the same...
I'm starting to see some serious downsides to being able to see who downvotes you. (kbin.social)
A few days ago I downvoted someone's comment, and the next day I happened to notice every single comment I've ever made had at least one downvote. All from the person I dared to downvote the ONE time. I straight up asked why they did it, and they seem to think I'm an "obvious" troll account that "apparently just exist to...
What does the "Favorites" feed do? (kbin.social)
I've been using Kbin for a few months now and I didn’t really feel the need to set my #feed to anything besides "Subscribed". I can guess from their names what the "All" and "Moderated" feed are but I have no idea what the #favorites feed does. I've seen that the recently added #collections also use the word "favorite" when...
Released idkbin 1.3.0! — A few small visual improvements for Kbin (userstyles.world)
In the past week or two, I've been making a lot of updates to my Kbin userstyle, idkbin, to account for all the new features Kbin has been getting. This weekend, I had a bunch more motivation to work on it, so I decided to make a bunch of additions to the userstyle and make the next version 1.3.0 (as opposed to 1.2.7, which...
The Magazines page is a bit of mess (kbin.social)
I've thought the Magazines page has been messy for a while now, though with collections now also being on the same page (at least for the time being), it's starting to get very out of hand....
What's the plan for downvote federation? (kbin.social)
Right now, downvotes (reduces) don't federate to (and from?) Kbin instances. This lack of federation makes the downvote counter really inaccurate—a comment that looks like it's +10 might be -15 when you look at it from lemmy.world....
Text with image markdown seems to disappear. (kbin.social)
Whenever you use this format...
Can't view the threads page of newcommunities@lemmy.world (kbin.social)
Whenever I try to view the threads page of newcommunities@lemmy.world (i.e., https://kbin.social/m/newcommunities@lemmy.world), I get an error. It's only kbin.social where this happens, and it's only the threads page of this specific community. I can view the microblogs, the people, and even individual threads, but the threads...
Could there be a "Filter" button for magazines? (kbin.social)
I know there's block, but "block" currently blacklists the entire magazine. If I click on it, it wipes all the threads on /all/, prevents me from looking at threads on the magazine landing page and all comments in the threads should I venture in. A "filter" would be a soft block that just clears it from my feed on the main page....
Why don't favorites & boosts federate from Mastodon on microblogs? (kbin.social)
I've noticed that when I'm browsing microblogs on Kbin, I see very few favorites (upvotes) on posts even when there are tons when you look at them from Mastodon. For example, this post doesn't seem to have any favorites, but look at it from Mastodon, and you see over 120. In general, federation with Mastodon is really...
Spam from unmoderated communities/magazines
Both !infosec and !science are being spammed constantly with opioid ads and other non-sense....
Blocking any domain seems to make certain stuff disappear (kbin.social)
I moderate @mcsuggestions, and today, I noticed that my comments on the two most recent threads didn't show up when I was logged in. After some experimentation, I figured out that whenever I had any domain blocked, all comments on those threads disappeared. From what I can tell in this magazine, others are experiencing the same...