Systems Engineer and Configuration
Management Analyst.
Postgrad degree is in computer science/cybersecurity, but my undergraduate is in archaeology. Someday, maybe, I’ll merge the two fields professionally!
I love true science fiction, as well as all things aviation, outer space, and NASA-related.
Lastly, Calvin and Hobbes is the best comic strip of all time!
Glad to be here trying out kbin and the fediverse.
Hmm I just checked, they’re all live and their status page for each link has no outages. I would check any content blockers etc. that you have, I suspect it’s a problem on your end. They do use different domains for their blog, feedback, and help KB etc.
Kagi does exactly what you’re describing. It’s what I’ve been using.
I don’t thinks that’s accurate, Kbin has only co-existed for a few Lemmy versions. I’ve been on Kbin before the initial wave of new users, when the site had about 200 users, federation was fine. You may be thinking of when federation was deliberately broken by Ernest with the entire fediverse for about a week when he had to enable Cloudflare DDOS protection during the first surge of signups.
The specific issue here was highlighted by a Kbin user several days ago. They monitored the traffic back and forth and saw that inbound Kbin-bot requests were denied by Lemmy.ml after the latest upgrade. At the time of that post, Lemmy.world did not have the issues and it had not upgraded yet. I’m not sure if that issue has since been fixed in the code or not.
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.
Important to note that’s not necessarily Kbin. Some of the major instances of Lemmy had an issue where they were blocking inbound Kbin traffic but allowing their traffic out.
It was unclear if it was somehow intentional or the result of a bug in their most recent upgrade.
If you’d still like to delete you can dm Ernest and he’ll sort it out. There’s a known processing backlog.
+1!
Newer uses of the fediverse also don’t realise yet that Lemmy is older then Kbin, years older. Kbin has only really publically existed for a couple months.
I was here before any surge when there were about 200 users and Ernest followed everyone MySpace Tom style. It’s damn impressive how the site held up even when he had to introduce cloudflare protection temporarily. It was slow, but never crashed completely.
Some Lemmy instances did go down for a bit, even the bigger ones that didn’t had more synchronising issues then Kbin. I’m not trying to knock Lemmy by any means, but I think this goes to show that Kbin is alright if at a few months old, it can keep up with software that’s been around for several years at this point.
Kbin has only existed publicly for a little over two months.
Lemmy has been around for four years.
It’s rather significant imo that Kbin is on par functionally with Lemmy, and Kbin.social has higher active user counts then all but a few Lemmy instances. Kbin seems to solve issues faster as well in the several weeks I’ve been here anyway.
Weird, they do, but they redirect for me and the final URL is different than what you pasted.
https://help.kagi.com/kagi/getting-started/
https://help.kagi.com/kagi/why-kagi/why-pay-for-search.html
My best guess is that a DNS record is messed up on their end, and since I’ve been to those pages before relatively recently, the cname or A-record is still cached for me.