Because the documentation on how to set up and run a kbin instance is incomplete. Entire sections just say todo. We need something we can run now, not something we might be able to run in October, if we are lucky.
this post was submitted on 21 Jun 2023
6 points (62.5% liked)
Blind Main
473 readers
1 users here now
The main community at rblind.com, for discussion of all things blindness.
You can find the rules for this community, and all other communities we run, here: https://ourblind.com/comunity-guidelines/ Lemmy specifics: By participating on the rblind.com Lemmy server, you are able to participate on other communities not run, controlled, or hosted by us. When doing so, you are expected to abide by all of the rules of those communities, in edition to also following the rules linked above. Should the rules of another community conflict with our rules, so long as you are participating from the rblind.com website, our rules take priority. Should we receive complaints from other instances or communities that you are repeatedly, knowingly, and maliciously breaking there rules, we may take moderator action against you, even if your posts comply with all of the rblind.com rules linked above.
founded 1 year ago
MODERATORS
I suppose that makes sense, given the deadlines. I just hope it works out and that the accusations about the arbitrary issue closing and dismissal of problems turns out to be false.
It's never happened to any of the issues I opened. Keep in mind that a lot of issues people have when hosting Lemmy are going to be because they misconfigured the database, or the server OS, or the web server, or one of a thousand other parts that the Lemmy developers can't fix. Our Stability issues were because nginx and docker had some misconfigurations for our traffic levels. Not a Lemmy problem, and the issue about the same problem someone else opened was closed, as it should have been. But at least the install and configuration process was well enough documented that the issue eventually got found and fixed (though not by me).
Because they got used to Reddit, where everyone who isn't radcial center (Markets and Capitalism are the only way) gets banned.
I dont agree with his views either, but he does great work, doesnt own the protocol, but gifted it to the public and isn't pushing his believes on others.
IMHO we should get used again to discussing with people who have have a diffrent opinion, instead of only talking to people who already have our opinion.
Yes and no. We do block Lemmygrad for hosting truly vile Russian propaganda.
Kbin is way less mature at this point, no regrets about which way I went. The great thing about federation is you could switch if you wanted to and still interact with the same content.
Kbin doesn't have an app. Lemmy does. That's the extent of it for me at the moment. I loathe browsing feeds in browser on mobile.
What are you talking about, I am using Kbin
Those are the main reason I'm currently replying to you from kbin
Ernest, the kbin developper is great, humble, reactive and I have big hope for him.
On the other hand kbin seems a little less mature at development level, but it has all the time to catch up
It has until July 1 to catch up. That’s when the apps get cut off. We had to have something running now, not whenever kbin catches up.
It runs just fine in browser and as a PWA, I'm literally replying to you from kbin
Yes, from kbin.social. Good luck running your own version of the kbin.social website on kbin though, the way that rblind.com is running Lemmy. Until the documentation for this process is free of sections that are just marked "todo", and the entire thing has a replicable and well explained deploy script, it's not even worth further discussion.
@fastfinge From what I see it's only the firewall and mercurejs which have to-do section. Not really obscure parts
If you already have previous knowledge of hosting anything serious publicly, it's not a problem.
But it's part of my "less mature" in my top level comment
What bother me more is the API not working
Yes, that and the main kbin.social instance turning off federation for a while. Between that and the way keeping kbin.social up and running seems prioritized above making running instances easier, I dunno. I just don't get the right vibes. Similarly, when people join kbin, they're just encouraged to go to kbin.social. Unlike Mastodon or Lemmy, I haven't really scene the developers recommending or even listing other instances. And as someone who doesn't use PHP for much of anything anymore (and doesn't want to), no, none of this is straightforward. Compare it to Lemmy, where deploying your own instance is just editing a couple files and running a single script away. Of course then you get to spend five days realizing the default nginx configuration isn't useful for anything more than a single-user instance, and the postgresql config really needs tweaking, and so-on and so-on. But at least one-click Lemmy installs, helping to keep the fedevirse distributed, are within reach. It doesn't feel that way at all for kbin. And I don't want Kbin (or anyone else) to have control of the fediverse on one or two large instances. Also, RabbitMQ also has a todo section. I've been hosting things online for something like 15 years, but I have no idea what RabbitMQ even is, never mind how to set it up, or what the implications of running it might be, or how I might monitor it, or what could happen when it crashes. Rust, nginx, and postgresql all feel like well-understood, popular, and well-supported technology. If something goes wrong with them, I have pretty much endless support via Google, or if worst comes to worst, it would be easy to find a contractor to hire. The technology kbin is using feels, at least to me, much less known and understood. OK, Lemmy does use pict-rs, and I'm not aware of anything else that does, but pict-rs feels simple enough that it probably doesn't matter, and it probably won't fall over in ways that I would need help fixing.
The power of the fediverse at work!
view more: next ›