this post was submitted on 16 Feb 2024
93 points (97.0% liked)
Fediverse
28406 readers
947 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I’m not one to knock a developer on their software. Making things like kbin are complex and they certainly take effort to maintain and improve. That being said, these are my complaints about the management of kbin:
Why is there hardly ever any feedback from Ernest about why kbin is down? It just comes back up and that’s the end of it, until the next outage. A link to an explanation, or detailed banner message, or a schedule would be nice, assuming that these outages are scheduled.
Why has Ernest insisted on being the only developer to work on this? This creates a potential “single point of failure” situation.
None of the git issues on Codeberg seem to get triaged or responded to.
Ernest rarely responds to DMs on kbin.
At this point, I think I’m just going to create an alternate Lemmy account to avoid these blackouts.
MBin is a fork by a group who tried to push into KBin but couldn't. There seems to be at least 4 active committers and stuff gets merged.
You will see a number of the KBin instances moved over https://fedidb.org/software/mbin
I created an acount on kbin.run (which is mbin) earlier today. I tried on the most populous mbin instance, but the request page throws 429s and the contact page 500s. This morning, I was ready just to go back to reddit for a bit (I didn't care for Lemmy, but I guess I would give it another shot before that).
Just tried to create an account on fedia.io, which is the biggest of the mbin instances (at just about a bit above 4K users, so not THAT much), and it just could NOT take the registration, all i get is "429 Too Many Requests", after multiple tries. I suspect that says the instance is woefully underpowered for the traffic it's handling
Yeah, something's misconfigured, underpowered, or something.
Hi there, mbin dev here. We have a configuration problem with rate limits. "429 Too Many Requests" is the server saying "you requested to much, I will not send you any responses anymore". Feedback is noted and we'll try to get that sorted out asap
@jherazob@kbin.social @tiredofsametab@kbin.run
Yeah, my very first request was a 429 so the back-off seemed really weird, heh. Thanks!