109
I’m making this post because I’m shutting down my Kbin instance, kbin.lol, and
redirecting it here for an undetermined amount of time. ## But why? Kbin isn’t
ready. Not even close. I know the developer, Ernest, has been working his ass
off trying to get everything fixed and pushed, and I really value his efforts.
However, it’s still beta software, and as I’ve been unable to make a good user
experience, it’s being shut down until there’s a better release, or a stable
one. ## What issues? Kbin.social works fine! - There is no option to delete a
user, except from the command line. Users can’t delete their own data. I have to
manually process all user removal requests, with the backend. - Federation
appears to be broken due to the messenger backend repeatedly crashing, with no
information on how to fix it. All I did was restart the Docker stack, which
shouldn’t break anything. - Compiling and running the site is extremely
difficult. With Lemmy, I just pull a docker-compose, set some variables, and
start it. With Kbin, I have to clone the git, change many variables across many
config files, and then compile the entire stack from source(even though stable
releases of some containers exist). I did eventually manage get the site
running, except this leads into the next point… - There’s no way to do a stable
update. I’ve tried pulling Git updates into the existing folder - that
overwrites all my variables and the site doesn’t start. I pulled it into another
folder, and not only does it not start, but all the users and database get
wiped. I’m sure I could figure it out…but I don’t want to be providing a site to
my users that’s so duct taped together. Ernest, bless his heart, is patching
stuff up on the source daily - but how do I update? - It doesn’t appear to be
scalable. The main instance, Kbin.social, runs slow and unresponsive because of
the sheer volume of users on it(which baffles me, because it’s beta software
that wasn’t ready for prime time). It’d be better if we had more instances, but
it’s hard to deploy, so we don’t have many instances…it’s a never ending circle.
## Okay, so it’s got some issues. What now? For now, you’re more than welcome to
join my Lemmy instance, which is right here. It’s nice and stable and I feel
confident providing it as a service. I’m still subscribed to Kbin development,
and if it has a proper Docker stable release, or something that just makes it
easier to host, I’ll look into it again. It’d be a damn shame to let the
kbin.lol domain name go to waste, lol, so I’m definitely invested in getting it
running. If you happen to be a smart web developer with spare time, and would
like to volunteer your skills to get it running, feel free to reach out to me,
but again, it’s a hairball I don’t feel comfortable with. With the right help,
though, maybe it could work. ## I don’t like Lemmy, it’s got tankie devs!
Personally, to be perfectly frank, I couldn’t give a shit less. I’ve got a long
history in the FOSS community and if I banned everybody I disagreed with it’d
just be me, a scratch kernel, and nano. Outright political instances and
instances that allow blatant racism are defederated here on my instance. Lemmy
devs are willing to create a product that makes the entire internet better, and
share it with everyone, for free, regardless of your beliefs. That’s good enough
for me. I’d rather see the internet become a better place, than to turn our nose
up at a FOSS project, because of disagreements between humans. That’s ruined
enough of the world already. ## What’s a tankie? Google it. I’m not here to be
political. ## Never mind all that, I just want Kbin! Well, you’re free to use
any instance of anything, of course! Kbin.social [https://kbin.social] is open
for signups - although I can’t guarantee that it’ll keep up with the flow of new
users from Reddit. We have hundreds of Lemmy instances including this one that
seem to be doing fine, if you would like. ### If Kbin can pull together a
release that is actually worth running, I will deploy it and relaunch the site.
- P.S. All user accounts and data from the kbin instance have been deleted.
Don’t worry - your data is gone, not being kept or spied upon.
Looks like the admin for kbin.lol has some pretty valid gripes with the current status of Kbin. I have to agree, you can tell the platform is not up to speed at all.
Kbin looks visually great but the backend just isn’t there. Check out his statement, it’s worth the read.
I found the same, tbh.
I’ve been on the thrediverse using lotide until now, which is different then lemmy or kbin. There were some federation issues so lotide wasn’t federating just as the place was blowing up with more users, so I decided it was time to install one of the new pieces of software.
I spent 3 days trying to get kbin working and federating, and just wasn’t having luck with it. Even now, kbin.social is pretty dodgy about federating, and doesn’t federate with a lot of other stuff at all.
My instances require good federation. That’s non-negotiable because otherwise it’s just me sitting here talking to myself.
Ultimately I went with lemmy, which I managed to get up and running quite a bit quicker.
To be fair to kbin, it’s a super new project. lemmy and lotide have been going for years, I hadn’t even really heard about kbin 2 months ago. I think it’ll get a lot better, but it’s going to take time and effort.
I sucked it up with respect to the lemmy devs politics stuff… Instead of bitching that they’re not exactly like me, I’m going to just be thankful to them for creating a platform we can share.
Yes, definitely problems federating, kbin.social is under quite some load and I made a new kbin instance (I’d previously only been testing). It’s been up over 2 days and not received a single thread or comment from kbin.social. In the meantime it’s filling with content from lemmy instances, like this thread for example.
But, I’m sticking with kbin for a few reasons. First as you say it’s a younger project and things will only get better, and as a software developer maybe I can help with that some. But, also because I like how it looks and prefer it over others.
I think there’s a lot of functionality missing, but it’s going to come over time. For people not prepared for this kind of bleeding edge operation I’d certainly not blame them for wanting to use a more established project.
I’m surprised you’re having trouble federating with kbin.social- that’s always been working for me from my personal instance. I have trouble federating with a few lemmy instances though. Lemmy.ml is still blocking the kbin useragent. And the communities of infosec.pub, sh.itjust.works, sopuli.xyz, among others- cannot be discovered from kbin.
As long as you’re happy with it, it’s best if there’s a diversity of projects each trying to do a different thing. That’s one reason why I stuck with lotide as long as I did (and I didn’t stop hosting it)
Actually- scratch that. updates from kbin.social are definitely slowed to a crawl right now.
Just a note,
It was shown a lot of the recent threadiverse federation issues were/are being caused by Lemmy. Major Lemmy instances were/are intentionally or unintentionally (due to a bug in their platform), blocking inbound federation traffic from Kbin and Lotide. While allowing their own outbound to go through.
The jury is still out on if it was an oversight/issue with their latest release, or something more nefarious on the part of the devs with regards to competition.
Yes, this seems reasonably accurate. I think it was the 17.3 release where federation with lotide went silent