Cavalarrr

@Cavalarrr@kbin.social
2 Post – 10 Comments
Joined 1 years ago

I may have missed the mark on my point in the main post to be fair; It's not about fearing defederation from beehaw.org, it's more about ensuring we don't get overran by people with ill-intentions before the dust has settled, and whilst the site doesn't have the manpower in place to keep things like that under control.
Currently there's nothing stopping someone from the communities beehaw has defederated with from signing up here and going on a fullblown hate campaign because they disagree with the ideals of the beehaw admins. Everywhere they go, those local instances are then looking at "ih8beehaw@kbin.social", and if nothing is done to prevent that, then it colours the rest of kbin.social users in a bad light. The more bad users you get, the more likely you are to experience widespread defederation, and lose out on a lot of what should make the concept of the fediverse great.

9 more...

To be fair, I think there's an issue with the obfuscation / blurring on a lot of the NSFW posts, i.e. people are tagging their post as adult only, but the thumbnail still shows "in all it's glory", I'll add an example below (don't worry, I'll still obfuscate):

Obfuscation not working properly (SFW)

I also feel like the blur isn't aggressive enough for some posts I've seen; I'd prefer something less... subtle... Sync for Reddit would just straight up show you a red box as the preview unless you went into the post.

Thanks for clarifying! Was the choice to defederate mainly down to a flood of content from other instances drowning out the fedia.io community, or the nature of content coming in, for example?

My thinking re: closing registrations for a time, is that if currently the only person that can action warranted sitewide bans (e.g. users actively using hate-speech in multiple posts in multiple magazines) is ernest, then there may be a point where there's simply too much to keep on top of, given everything else he has going on.
These concerns may well be completely unwarranted, and I'm well aware that even if kbin.social were to be defederated from a number of instances, that once "the situation" was under control, they could be re-federeated if agreed with the other instances. It would just be a shame to hamper our own community by being relatively powerless against a potential influx of bad faith users whilst ernest is busy being awesome and actively improving kbin as a whole.

Interesting, I thought it was just an abbreviation of the original Polish site, karab.in (which would also explain why 'subreddits' are called magazines, karabin = rifle). Either way, that's pretty seamless inspiration.

To be fair, and whilst I am poking fun at the article with the description, unfortunately there are bound to be at least a couple of crackpots that would try and incite violence, regardless of the fact that the vast majority of Reddit staff likely don't agree with what's been going on either.

lemmy users want to stay on lemmy. they don't want to come to kbin (even to troll). and I think the few that might end up here will just be drowned out by good faith kbinauts.

Given the much higher number of Lemmy instances, you may well be 100% correct on that, that is, even trolls may just decide to 'stick with what they know' and continue to use a Lemmy based instance.

if someone has an issue with kbin being open to everyone, then they will naturally block us no matter what we do.

Also correct, however, I understand that if a post is local to kbin.social, and had comments from lemmy.world users, in addition to kbin.social users, and a beehaw.org use came to the post, they wouldn't see any of the comments from the defederated users. That is to say, so long as one instance doesn't federate with another, they will never see posts from that instance, regardless of where they are.

I'm not saying that won't still prevent people defederating with kbin.social purely because we're open / federate with another community they specifically defederated from, but there's less reason to if kbin.social maintains a quality userbase.

I think that spirit and culture is far more important than whether or not a few bad apples start getting other instances wanting to defederate.

If a large amount of "beehaw haters" start flooding kbin and changing the culture to be one of toxicity and vitriol, then I do think we'd start having a problem.

Another agreement from me here, however, the point of this post is to start a discussion around whether or not we can prevent being overwhelmed with bad apples too early on in the platforms lifespan (although I appreciate we've already addressed this above).

As has been said, at this point, it's entirely up to @ernest, but I think it's worth looking at potentially taking a couple more people on to assist with the moderation side of things.

6 more...

Hopefully someone can create something like this for kbin instances. I would say all federated 'groups' but I'm currently not sure how that would work with things like Mastodon.
I imagine in the future, we'll etiher have better built-in discoverability or a site that includes the whole of whatever ends up being the biggest aggregator platforms.

Thanks for the link!

Slightly off topic, but why are we saying 'kee'binetters? Where is the 'kee' in kbin?

3 more...

Hear hear!
I never really contributed much to reddit, as usually you had the people that perpetually watched twitter / news sources / new reddit posts getting in first, to the point where there wasn't a whole lot of point getting involved outside of voting, because someone else has already said whatever you were about to.
Here though, I'm itching to contribute and get the ball rolling on magazines. Just a shame the performance issues are hampering that, haha!

2 more...