Is it just Kbin, or does every fediverse service have the issue of being totally swarmed with bots advertising illegal pharmaceuticals? Is this just the result of limited moderation?
Kbin seems more affected than others from what I can see in reports but it exists on other instances too.
It is a moderation issue in the sense that it is too easy for these bots to sign up. Individual instances could improve this by requiring an application for example.
With Lemmy, we have seen huge numbers of bots at times but most large Lemmy instances have registration applications turned on. As in you apply to join an instance instead of just being able to make an account.
By default this means waiting for manual approval of your account, but many instances set up automated approval behind the scenes.
This function means many spam bots are averted before the public sees them, and also spammers avoid instances with registration applications.
I mention this because Kbin, or at least Kbin.social, doesn’t appear to have registration applications which makes it a prime target for spam.
Also Lemmy has coordination between dozens of instance admins sharing details of spammers. I.e. a lot of hard work behind the scenes. I’d guess the lack of moderation at the admin level also accounts for part of the issue on kbin.
(A lot of Lemmy spam also comes via federation from Kbin.social, so much that many instances block high spam communities on Kbin and some block Kbin completely).
No, he's not. Kbin was recently down for a week. Then voting and comment counts broke. Before all that I had to get into the habit of reloading the page I was on every time I wanted to vote on something. It's a terrible user experience.
That's not to say I don't like him or he's not a good dev or whatever. Just that people have limits and it sure seems like he's bumping against his.
I didn't say anything about burning out. A job can be too big or difficult for a person without them burning out.
Ultimately, it's just a question of results. If kbin.social is working poorly but other alternatives are doing good, I move on. That works well in the Fediverse especially, as evidenced that I am commenting from fedia.io.
Likewise I also moved on from Kbin. Obviously we have no power over that project, that belongs solely to the person who created it, but we do control our own actions. e.g. I used to sing the praises of the Fediverse and go out of my way to not equate it with Lemmy - always saying like Lemmy/Kbin. Now I still do the former but I actively tell people that Kbin might not be a good match for them. Ernest has kept it as alpha version software - which is fine, there is a need for such things, and it will become great, someday… hopefully. But today is not that day, and that is super good for people to know, e.g. that they don’t have to leave the Fediverse entirely to get a more functional experience, just Kbin.social.
One day is annoying, but bearable. much longer and I won't have a choice but switch. I like kbin, but the mbin team says some things that I find concerning about kbin - I wish the two could patch up their differences.
I'm not saying anything negative about kbin, and I still have and use a kbin account. I'm just saying that it's hard to post anything from an error page.
I appreciate the info though, I am experimenting with different instances so that's good to know.
@FfaerieOxide me too. I like it, I love the platform, I don't have an issue with the outages, and I like the way Ernest understands the fediverse.
If there's an outage fine, I just go to another fediverse account til kbin.social comes back. We all have other things in our life, sometimes projects have to take a back seat.
Also I have a lot of sympathy for Ernest wanting to retain control. It's his vision, let's let him do it his way.
Edit: the spam seems to be on mags that have Ernest as sole mod, so that might be an easy fix.
The project definitely accepts contributions, the mbin devs have contributed to kbin before and a few weeks ago a minor code change was committed and merged by someone other than ernest.
As I understand it, the issue is that people with merge permissions other than ernest are only allowed to merge their own pull requests, not those of third parties, which require a review from ernest.
(At least that's what I've seen explained before, though I haven't seen any proof of it so I don't fully know if it's real.)
This means a majority of contributors can't get their pull requests merged when ernest is gone. Which is why they went and made mbin when he was gone for months last time.
I think a lot of us have had the same thoughts looking around kbin.
We all appreciate the work Ernest has done, but we really need someone to dedicate some time to picking out a team to help him, but it seems like that's not happening for whatever reason. I know there's a few other people in the codeberg, but I believe there was a falling out there. What we really need in addition to that though is just generic admins.
I understand the desire to keep kbin a solo project in order to maintain control over it, but if this is going to see any success in the long term, then there needs to be a team. I like kbin over lemmy for the interface and mocroblog integration, but the spam and lack of updates are taking its toll. At the very least, there needs to be another admin or two to look after things whenever Ernest isn't around.
By this argument nothing should ever interoperate with anything else because clearly that's the first step toward destruction.
I'm writing this on Firefox, which interoperates with Chrome and Edge. Oh no! We need to get these browsers operating on incompatible protocols stat, before they all extend and extinguish each other.
In reality, "embrace extend extinguish" is not a law of nature. XMPP is not ActivityPub. They are separate things with separate circumstances. Did you know that XMPP is actually still functional and open and you can download clients and servers that use it to this day? The stories about how Google "destroyed" it have become wildly distorted folklore at this point.
The great thing about the Fediverse is that you can choose that even if Threads federates. You pick what you engage with, which communities and instances you subscribe to and which you block.
@ernest
I've noticed this week that I'm currently seeing no visual indication that the boost button is active. No underline, color, or anything.
It seems that a now-broken userstyle I'm using expects there to be an "active" class applied to the element, but it isn't anymore. Is that intentional?
Figured I should point this out to you in case you don't know already.
The main issues with the improper functioning of the instance have been resolved, but it led to additional complications. Currently, using the instance should be quite comfortable, but I will continue to work intensively on a comprehensive solution for the next few days. Therefore, occasional interruptions or errors may still...
Cloning black-footed ferrets raises optimism for preserving a threatened species (www.infoterkiniviral.com)
Explore the groundbreaking cloning efforts reshaping endangered species conservation, as two more black-footed ferrets join the ranks of genetically i
KES 4.1.0: Improving the signal to noise ratio by blocking unsolicited ads (kbin.social)
The blurb below is excerpted verbatim from the release notes. For the full release notes, see here....
Do the "Ernest needs to add more maintainers to KBin!" comments remind anyone else of the xz social engineering malarkey? (kbin.social)
Comments such as:...
I Still Like Kbin.social (kbin.social)
I still like posting here....
So… what's going on? (kbin.social)
Since the beginning of the year, there's been a bit of a pattern over on @kbinDevlog:...
Scientists Identify The Optimal Number of Daily Steps For Longevity, And It's Not 10,000 (www.sciencealert.com)
Conventional wisdom would have us believe the journey to a long and healthy life begins with 10,000 steps.
How Threads will integrate with the Fediverse (plasticbag.org)
[UPDATE] Issues with the functioning of kbin.social (kbin.social)
The main issues with the improper functioning of the instance have been resolved, but it led to additional complications. Currently, using the instance should be quite comfortable, but I will continue to work intensively on a comprehensive solution for the next few days. Therefore, occasional interruptions or errors may still...