@cacheson@kbin.social avatar

cacheson

@cacheson@kbin.social

This profile is from a federated server and may be incomplete. Browse more on the original instance.

cacheson,
@cacheson@kbin.social avatar

Back in the day facebook only had a like button and people demanded a dislike button. I don't know what facebook thought internally.

😆

cacheson,
@cacheson@kbin.social avatar

Might be interesting to have per-instance weighted voting. So local votes would count as 1x, votes from other instances could count as 0.5x, and votes from that one instance that has a lot of vote brigading would count as 0x. Would be useful for smaller, specialized instances that tend to get harassed by outsiders.

cacheson,
@cacheson@kbin.social avatar

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.

Actually, that would be really cool and worth doing regardless. Have a voting statistics view for each post where upvotes and downvotes are broken down per instance, and maybe by other criteria too. @ernest

cacheson,
@cacheson@kbin.social avatar

You can use the boost feature. Your boosts are public, but that's usually a good thing. Things you want to save are often things you want to promote, and vice versa.

cacheson,
@cacheson@kbin.social avatar

It looks like they're still working out what they want their process to be:

https://github.com/MbinOrg/mbin/pull/34

Seems like your concern is addressed there:

Pull Requests require at least one (1) other maintainer approval before the PR gets merged (built-in peer review process).

The mbin fork happened when kbin development was looking a lot less active. In any case, it's not necessarily bad to have a diversity of approaches. Due to their differing organizational structures, mbin will likely tend to have more features and more rapid development, but also potentially more bugs, while kbin remains more stable.

cacheson,
@cacheson@kbin.social avatar

Hmm, that seems like not such a good look from Ernest. According to google translate:

I know, honestly it was on purpose. I noticed that forks sync changes immediately with /kbin. I wanted to check how they deal with this much-announced community-based qualitative code review. Answer: they can't cope. Quite an obvious bug was accepted in PR and domerged into the main branch :P It now works properly on the rifle ;)

Hopefully everyone can play nice and work together productively.

cacheson,
@cacheson@kbin.social avatar

From the PR comments:

Maintainers MAY merge incorrect patches from other Contributors with the goals of (a) ending fruitless discussions, (b) capturing toxic patches in the historical record, (c) engaging with the Contributor on improving their patch quality.

I asked around and asked in the C4 specification matrix room.
And the reason is actually simple. If you merge bad code, have a record of proof in git (pull requests aren't forever it's only a github/gitlab thing).

So the idea is if you merge bad code you have proof in the git record that there is a bad actor. You can always revert the commit again or fix it. And the record can act as a proof in case the community want to get rid of bad actors.

Request: Remove ability to 'boost' your own comments and threads (kbin.social)

The ability to 'boost' your own comments/threads has been used by a very small number of users in a way that seriously degrades conversation on the platform. These users constantly move their own contributions to the top of the conversation without regard to their value. If allowed to continue it will likely become standard for...

cacheson,
@cacheson@kbin.social avatar

That's because of a bug in the hot sorting. It was working fine for a while, and then broke. Upvoting your own post also fixes it. We should probably have our posts self-upvoted by default anyway, like on reddit and lemmy.

cacheson,
@cacheson@kbin.social avatar

Ah, fair point. Either way, it doesn't make sense for it to be optional.

cacheson,
@cacheson@kbin.social avatar

If you've blocked any domains, try unblocking them. Domain blocking is buggy and will hide random stuff from you.

I've got the photo post bug too, but it only seems to affect me on @anime_irl, while @animemes seems to still work fine.

Also, you posted this multiple times, may want to delete the other ones. Whenever you make a post, check the "newest" sort order to make sure it went through, and then upvote your own post to make sure it's visible for everyone on the default "hot" sort order.

cacheson,
@cacheson@kbin.social avatar

Sure thing. Blocking individual communities does still work.

cacheson,
@cacheson@kbin.social avatar

Domain blocking isn't instance blocking. It's for if you don't want to see posts that link to, for example, imgur.com. It's also broken and will just hide random posts from you.

We need more / faster moderation (kbin.social)

Ive spent the last week in shock at the lack of moderation because magazines and federated stuff is only moderated by @ernest who I know is busy with development. But the magazines that are on kbin.social and were setup as "Template" magazines are getting trashed either with spam/porn or toxic comments that were reported long...

cacheson,
@cacheson@kbin.social avatar

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?

cacheson,
@cacheson@kbin.social avatar

It's an annoying combination of bugs. Basically just look at "newest" after posting, and upvote your post to make it visible.

cacheson,
@cacheson@kbin.social avatar

I just use the "boost" feature to save things.

cacheson,
@cacheson@kbin.social avatar

Notifications from blocked users is a bug. There isn't really anything that can be done about the "last word" thing, though. On reddit-style platforms, the expectation is that blocking a user just hides their posts and comments. If the blocking user's activity was hidden from the blocked user, then it would be possible to preemptively block someone before defaming them in order to stop them from reporting it.

cacheson,
@cacheson@kbin.social avatar

I may be mistaken on the exact details of how it works on reddit, but allowing non-moderator users to prevent others from replying doesn't sound like a good idea. For comments, preventing a blocked user from replying directly in a child comment means they'll just reply in a sibling comment instead. They still get the last word, so the only thing accomplished is to mess up the threading a little bit.

For posts, preventing blocked users from replying gives the poster pseudo-moderator powers over replies. They can block anyone criticizing or disagreeing with them, giving them significant narrative control. Not exactly desirable.

Blocking should only be for filtering what the blocking user sees. It cannot be a substitute for proper moderation.

cacheson,
@cacheson@kbin.social avatar

Alright, let's pretend that you've blocked me, and that this comment is telling everyone that you smell bad. It's not a direct/child response to your comment, but everyone can see it and knows I'm talking about you. If you don't respond, then by your logic I've "won", and you must in fact smell bad.

It seems more like you're taking a stand on stubborn principle than advocating for good user interface design.

cacheson,
@cacheson@kbin.social avatar

Yes, but I don't think PMs currently work between kbin and lemmy.

cacheson,
@cacheson@kbin.social avatar

This is a software bug. Why would other normal instances not want to know about and enforce community ban lists? That just results in a poor experience for their own users.

cacheson,
@cacheson@kbin.social avatar

The default "hot" sort order is bugged right now, so new posts without any upvotes end up buried. Upvoting your own post after making it fixes this.

And in general, yes, upvote your own posts. It's weird that they aren't automatically upvoted by default, like they are on both reddit and lemmy.

cacheson,
@cacheson@kbin.social avatar

Generally your posts will be successful despite the error, but they'll also end up buried in the default "hot" view. If you switch to "newest" you should see it. Upvoting your own post should make it show up correctly in hot. No idea about the deletion thing though.

Is there a way to report an individual user? (kbin.cafe)

There is a user who posted an irrelevant ad on a magazine I follow, so I clicked their profile to see if the rest of what they posted was spam too. It was. However, I didn’t find a report user option on their profile. Is there one anywhere? I know I can go through and report their individual posts, but I’d also like to flag...

cacheson,
@cacheson@kbin.social avatar

Ernest would be the one that would have to ban them from the site. A comment he made recently about the spam situation:

This month, the largest update is planned. It's taking a long time because part of the team is returning from vacation, hence the delays. I hope that the update will resolve some of the most pressing issues. I'm also trying to remove spam systematically, but currently, the code is my priority. After implementing the new version, I will seriously address the community.

If there's anything urgent, currently contacting through the form is the quickest option. Cheers!

cacheson,
@cacheson@kbin.social avatar

It's partly specific to the kbin software, and partly specific to kbin.social. The biggest problem is that the software doesn't currently support having more than one administrator account per instance.

The flagship instance, kbin.social, is administered by ernest, who is also the lead developer of the project. Working on the software seems to keep him plenty busy, to the point where he's not able to keep up with administrator tasks.

Since kbin.social was (I assume) not used by very many people before the reddit migration, almost all the older magazines are owned by ernest, and have no other moderators set. There's also a large number of magazines that were created during the migration, but have since been abandoned by their owners. Reassigning these is a task that currently only ernest can do.

And of course as the most populated instance, kbin.social is a more desirable target for spammers, compared to the other kbin instances.

cacheson,
@cacheson@kbin.social avatar

Neither lemmy nor kbin have an account migration feature yet. AFAIK that's just a mastodon thing for now.

cacheson,
@cacheson@kbin.social avatar

Pretty sure we're already defederated from grad. We don't have an instances page yet where we could check, but that's been merged into kbin's code and should be available next time the site gets a version update.

How do I know which instances kbin is/is NOT Federated With? (artemis.camp)

Sorry if this has already been asked, but is there a way to know if kbin is or is not federated with another instance? I know there is a way to block domains by typing in https://your kbin instance/d/domain you want to block and blocking them from there, but is there a way to see a list of instances defederated by default?...

cacheson,
@cacheson@kbin.social avatar

Pretty sure this isn't currently possible. I've created a feature request on kbin's issue tracker for it.

cacheson,
@cacheson@kbin.social avatar

And there's a pull request for it already. That was quick.

cacheson,
@cacheson@kbin.social avatar

Yeah, we haven't had an update in a while. Apparently the next one is going to be pretty big. Ernest said he's aiming for the end of September, but I'm assuming that may slip.

"Antiwoke" magazin on kbin.social posting bullshit like "how to end Wokeness" and "Time to reject the extrem trans lobby harming our society" How to report ? he is the moderator of that magazin. (calckey.social)

@ernest how do I report a Magazin on kbin.social ? There is a usere called "ps" who is posting to his own "antiwoke" Magazin on kbin.social. Please remove this and dont give them a chance to etablish them self on kbin.social. When I report his stuff it will go to him because he is the moderator of the magazin? Seems like a...

cacheson,
@cacheson@kbin.social avatar

The regulations are quite general, and I would like to refine them together with you and do everything properly.

I have been wondering how instance-wide moderation will end up looking on kbin, once you've had a chance to get a team in place for that. While it is (I assume) a "generalist" instance, it's important to keep in mind that you can't please everyone. Trying to have too broad of an audience will just result in retaining those with a high tolerance for toxicity (usually highly toxic themselves), while everyone else leaves in favor of better-managed spaces.

Communities in general, and particularly on the internet, need to understand what their purpose is, and be proactive about filtering out those that are incompatible with that purpose. This doesn't mean judging those people as wrong, or "bad people", it just means recognizing that not everyone is going to get along, and that some level of group cohesion needs to be maintained.

cacheson,
@cacheson@kbin.social avatar

I think there is value in having both generalist and specialized instances, and the big landing spots for new users should probably strive to be more generalist. As you point out though, there are limits to how broad of an audience one can practically cater to.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • meta
  • Macbeth
  • All magazines