The only thing I really dislike about Honda styling right now is the “underbite” look they have on the front. The previous gen had the opposite, almost a pig nosed look. Why can’t they just do normal front designs?

I love the rear this generation and how they toned the entire look down, but they can’t figure out front grills to save their life it seems.

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.

These are all weak takes imo.

The designer of much of Hyundai’s current lineup is Luc Donckerwolke, who is famous for his Lamborghini (Diablo, Gallardo and Murcielago) and Audi designs. You may not like them but they’re not “design by committee” derivatives.

Almost no manufactures are heavily developing their ICE engines anymore, nor do all even produce their own engines (Hyundai/Kia do).

Much of the “airflow” “issues” you’re talking about are simply price point. The two most impactful areas for sound insulation on cars are undercarriage and wheel wells and door/window frames and seals. For the former, nothing about it is high-tech. Even luxury makes user sound-absorbing materials including plastic deflectors, fabrics, and lightweight low-density filler materials behind panels such as polystyrene. How much sound proofing you get is a reflection of Hyundai’s entry level lineup. You’re not going to get Mercedes-level sound insulation at half the price just because the design looks high-end. It’s not until you’re near the top of luxury car lineups or Rolls/Bentley territory that this area becomes innovative.

P.S. Hyundai/Kia also hold patents for 2-stroke supercharged engine designs as well as variable compression designs.

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.

Genuine question here, how can Lemmy have more content if it’s all federated? Wouldn’t Kbin, despite being much younger, have all the same content?

Yes….on a technical level. But the picture is bigger than that. Personally, I have a hunch that the choice of Rust is making Lemmy’s development slower. This seemed to be evidenced by the fact that Kbin has more functionality than Lemmy while having only been around for 2 months. Vs Lemmy’s 4 years. The Kbin dev has also been much more able to fix things on the fly during the surge in users. Whereas Lemmy will supposedly move off websocket use any day now.

Adoptability isn’t something to be discounted. The fact that there any more people out there familiar with PHP may give Kbin an edge over time. And let’s be honest, in real-world test PHP can very often be faster then - less-than-mature-Rust codebase.

Kind of like how Lemmy made up communities? Lol you don’t call microblogs “toots” either. Seems every fediverse software has their own terminology.

Also it’s dev, singular. Kbin has been put together by only one dev. I personally find that damn impressive considering it’s functionally on par with Lemmy being only 2 months old to Lemmy’s 4 years.

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

I think they actually have the largest independent index outside of Google/Bing right now.

Others that exclusively use their own index are:

Mojeek (results aren’t great)
Kagi (result are pretty good imo)

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.

Via the ActivityPub protocol that fediverse software uses :)

Pretty cool stuff!

Kbin can also directly interact with Mastodon users and toots because of this. Kbin magazines can natively contain both “threads” from Kbin and Lemmy, and microblog “posts” from Kbin and Mastodon. (And other software depending how they map these features.)

You bet! The fediverse is definitely a confusing concept to wrap your head around the first time. And it doesn’t help that different software server instances don’t need to use a site name that specifies which software they are (like Beehaw, for example).

I think the “dynamic updates” behaviour is tied to Lemmy’s use of websockets instead of http. Kbin uses http. The Lemmy devs have stated they’re going to move off of websockets in the future as they present scaling issues with the way the software is written.

The websocket protocol allows bi-directional push communication regardless of the previous request which means that new posts are constantly triggering server side updates which then appear like a page “refresh” on clients.

Arguably, while websockets have very cool realtime features compared to http, for a Reddit-like content aggregate their use can quickly overwhelm usability without significant retooling.

It depends on what you mean by other servers…Lemmy instances? I haven’t seen any differences between kbin instances.

Kbin is entirely different software from Lemmy; it’s a completely different backend.

So that would be why it’s “better” in that regard than Lemmy instances. My understanding is that it’s a bug in Lemmy that will be fixed soon.

The “popping” of the feed in Lemmy is tied to their use of websockets instead of http. I believe the devs stated they’ll be moving off of websockets in the future.

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.

That’s makes sense but from an engineering standpoint, anything below operating temp and pressure fundamentally causes more wear.

It may be minimised with configurations such as you describe, but it’s still more wear than if the engine hadn’t stopped in the first place.

How much, I don’t know, but over the course of hundreds of thousands of miles and thousands of stop-start cycles, it adds up.

Well I think I can answer that. It is more efficient for fuel consumption. They all have the systems because it allows them to hit better EPA fuel economy numbers. But better fuel consumption doesn’t mean there’s no effect on the engine.

I’m not saying I’m 100% correct btw, I’m waiting for a mechanical engineer to explain why I’m wrong. But my limited understanding hasn’t found an answer for my concerns yet.

That might be true, I’m not a mechanical engineer but despite that, my understanding is that within the engine block itself, cylinders are primarily lubricated via the system holding pressure. This pressure starts to drop the second the engine ceases.

You can notice the effect on cars that have realtime oil temp monitors. Mine does, and it’s digital. My stable oil temp is around 216 degrees Fahrenheit. After a start-stop cycle, even for only 5-10 seconds or so, the temp drops about 5-8 degrees. After a minute, the temp is down 25 degrees. That’s significant. Essentially the engine is no longer “at temp” for the first 30 seconds or so after it resumes. That’s 30 seconds of additional semi-cold, under pressure wear each cycle.