If you search some people already have. https://kagifeedback.org/d/6842-non-ai-unlimited-plan/39

And… it’s not a priority for them, maybe they’ll charge you $5 to disable AI features though 🙃

It will take a prompt, then run multiple web searches to get relevant info, recursively if needed, and then give a meaningful response with citations.

Do you have an example of this you can provide verbatim?

I’m just curious; I think the one application LLMs might actually be viable for is exactly this kind of connection finding in a large corpus, and since I’m doing lots of research, I might actually find personal utility.

The AI assistant is backed by several different models which IIRC just call out to those providers (Op*nAI API, etc) and rack up tokens in the billing system: You might be right that the AI cost is included when below the plan price — to that I have to say, give me a fucking cheaper plan that doesn’t implicitly include the cost of AI.

As far as I can tell, you have to completely disable all keyboard shortcuts or else when you press A anywhere that isn’t the search box you get dumped immediately into their AI assistant prompted with whatever you already had in the search bar.

It didn’t track me more than a few pennies, but on principle the several times that happened made me angry.

Apparently some of the news views in search are also easy to dump you into AI land. There’s community CSS add on that hides all that stuff now, but I wish the company would let me just disable the AI traps.

I use Kagi because the truth is all other corporate alternatives at this point are unusable swill.

That said, I do not like the company and disagree with their choices in many aspects.

For one, while they don’t force you to use AI features, there isn’t a way to explicitly turn them off for your account, there always the opportunity to rack up token costs if you accidently hit one of the AI buttons.

They still don’t run their own index, instead complacent to just pay the other search providers. Additionally, if you’re trying to escape Google… Kagi runs on Google Cloud Services.

There’s more complaints, and I’m sure others will chime in, but that’s my take.

It’s funny because I’ve had this one particular issue with two Asus routers that I manage for family…

They use this plunger power button design, you push the button in and it toggle locks in to place, the problem is that after a few years whatever mechanism retains the plunger fails and it always springs back and keep the device from staying on. So far the solution has been to cram a paper clip down the housing to hold it in. I just find comedy in having to apply that fix twice.

Sooner is better than later on this, the expertise and supply chain for AP1000 isn’t going to hang around unused.

There are literally people running servers at home.

Which is why I’ve said three times now it should be an EPYC 4005 product.

Two V-Cache CCDs just don’t make sense for consumer use-cases is the point here.

Because of the latency topology you’d only see a benefit if both CCDs were running independent programs that are more strictly sensitive to latency than compute throughput. That’s a very niche subset of uses, and like I said, ideal for a GSP deployment. This should be a product, but in the EPYC 4005 family.

Otherwise, you’re better off with some sort of heterogeneous topology, one can imagine an 8 core V-Cache CCD paired with a 16 c-core CCD design (this is very roughly what Intel is pursuing with upcoming products) which offers compelling utility even in the consumer space.

Honestly these don’t make much sense as a consumer product. If your game is doing latency sensitive work across the CCDs then you’re wasting the V-Cache, the only real way to see a benefit would be running two separate games…

Which is the kind of thing you would do on game server — so this seems ideal as an EPYC 4005 product instead.

What gets me is they’re still planning on using the advertising monetization model.

The sad thing is those GPUs are in specialized boards with specialized servers and cooling, and not really good at the kind of work consumers would want it for, assuming you could even get drivers. So most all of those GPUs will realistically get scrapped if the bubble pops.

Maybe we’ll see the EPYC CPUs get sold secondhand at least, those are socketed.

Honestly even normal monitors are starting to fail at 2-4 years because they underspec the backlight LEDs, have faulty T-con boards, bad flatflex edge bonding, etc.

If they can get the price of OLEDs within 25% of a good IPS monitor like for like, I’d just get the OLED knowing the monitor has a lifespan either way.

Kagi uses Bing as its primary search index AFAIK, so no Google search API there.

That said, it does run entirely on Google Cloud Services, which I personally find ironic.

I think we’ve tapped most of the mileage we can get from the current science, the AI bros conveniently forget there have been multiple AI winters, I suspect we’ll see at least one more before “AGI” (if we ever get there).

If you feel you are not properly sedated, call 348-844 immediately. Failure to do so may result in prosecution for criminal drug evasion.

— THX 1138

I agree with this viscerally.

A lot of people are expressing sympathy for the people in the Kirk crowd, but honestly I think it might be a good thing for them — to see first hand what Kirk and the Republican rhetoric is actually advocating for. Maybe it’ll snap them out of the fantasies they have of culling “undesirables”.

…Which is basically how the OP’s or function also works, it takes several Option<T>s and returns the first valid one (and only that one), it doesn’t operate on boolean logic types — it’s a valid lexical use of or.

It’s an understandable interpretation for the lexical use of or which can imply exclusive disjunction.

In Rust the result type has the method .or() which returns either Ok(A) or Ok(B) (but not both), and I don’t see clambering to change it to xor, because the exclusive nature is implicit both linguistically and in the type state.

It’s fine, modern CPUs boost until they either hit amperage, voltage, or thermal constraints, assuming the motherboard isn’t behaving badly then the upper limits for all of those are safe to be at perpetually.