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.

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.

This is also how it works in Connecticut. While it may not be perfect, I don’t think it’s entirely unfair. It has the effect of a being a progressive social policy this way in that it is available for those who don’t already have it. Someday it like it to be carte blanche to everyone, but states doing this way is a solid start.

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.

I use Kagi too, it’s surprisingly snappy! Like seriously impressive for a small org. They talk about speed optimisation being critical for them as well. I find the result to be excellent as well. A true Google replacement/feels like Google in its prime.

I believe they have their own index and bot as well?

This is good news! And we/they should keep pushing for more, everywhere. Good for IBEW for continuing the pressure.

They do have their own crawler and I believe supplement from bing only when necessary. Something like 96% of results are from their own index. They actually have a breakdown for every search.

I understand your idea, but I think it would defeat the purpose of the fediverse. It would create single points of failure that are un-correctable.

I also think many people forget that Reddit never functioned any differently. Everyone seems to have forgotten (and I’m not saying you have!) that there are and were always multiple subreddits for any given topic. With slightly differing names. The only reason people are forgetting this is because eventually one or a handful became pre-eminent and the others died or became transformed into something more niche.

I think it’s a problem that will ultimately correct itself, but I think a tags based system, like hashtags in Mastodon, would be a better solution for tying communities/magazines together through metadata.

I think it’s a fair point. They won’t be able to remain federated to many instances if their point of contention is open-enrollment.

I understand needing the Lemmy moderation tools to improve and that it’s temporary, but the damage to their own communities and users may not be temporary.

Their users will turn inward and end up preferring their own communities—which is fine. However it also means that non-beehaw users will shy away from those communities in favour of others, lest their home site get de-federated at some point for the same reasons. These effects combined means slow-to-grow, low-visibility communities in the fediverse, and increases the chance that their communities may dwindle if others of the same subject become pre-eminent outside of Beehaw.

In short, while I understand their reasons, I think that it risks making Beehaw.org permanently insular and ultimately much more similar to a non-fediverse website.

Currently using Orion on iOS. It’s made by the same people behind the Kagi search engine (which I also use now).

It’s still in alpha, so I occasionally encounter a bug, but the fact that it has built-in advert and tracking protection, as well as cool tab-suspend features sold me.

It tends to be on a newer version of WebKit then then Safari as well.

Oh, and did I mention it can use both Chrome and Firefox extensions?

I think Google peaked about 6-8 years ago now and then started slipping at an ever accelerating rate.

It’s almost useless for me when searching anything remotely technical or otherwise niche.

I almost consistently need to go to the second page of results now, something I don’t remember doing since like 2009.

I find Bing acceptable. Brave search works well. But I’m actually using Kagi now since I’m hoping their paid model will actually mean I’m not the product.

This must be a Lemmy thing right? I haven’t experienced this at all on kbin.

I’ve only used it on iOS so far, but I’m a backer so I think that might mean I have a newer version than the public beta. I might try it again if that was a while ago, I had a few bugs previously that have been sorted in the more recent versions.

Also using Orion! It’s the only one that’s convinced me it’s better than Safari, primarily because it’s actually more aggressive with power savings than Safari. The implementation to kill idle tab processes almost immediately is very effective imo.