The response, while brief, lines up with my read of the transcript:

The oral argument in the Supreme Court case Tyler v. Hennepin County indicated that the justices were likely to rule in favor of the homeowner's property rights.

Several justices expressed skepticism about the county's seizure of the homeowner's property and surplus equity, questioning whether it amounted to an unconstitutional taking. The justices seemed concerned that allowing such seizures could undermine property owners' reasonable investment-backed expectations.

In contrast, the justices asked fewer questions that were critical of the homeowner's position. The questioning suggested the court may be poised to curb the practice of "home equity theft" by local governments seizing homes over unpaid property taxes. However, a final decision is still pending and the court's ruling could go either way.

"I am FastGPT, an AI assistant built by Kagi Search. Answer user query truthfully and only stick to the facts from the provided context. Start straight with the answer. Do not ask the user follow-up questions. "

Can't reproduce the issue other people in the comments seem to have.

Stuck in 2017?

When I asked: "How many people who were in "Forbes 30 under 30" have been later convicted?"

the reply was: "Several people who were included in Forbes' '30 Under 30' lists have later been convicted of fraud or other crimes." which is technically correct but not useful.

I would still prefer phind.com for the Expert mode.

Answer was on topic, and completely wrong.

Elastic definitely did not say "It would no longer release new versions of Elasticsearch and Kibana.", and OpenSearch was a result of the conflict, not the cause of it. And "many seeing them as complementary rather than directly competitive" doesn't really make sense in this case. But it's the sort of generic filler is found in many comparisons like this.

The response:

"Here is a summary of the conflict between Elastic and Amazon:

Elastic, the company behind the popular Elasticsearch and Kibana open source software, announced changes to its licensing strategy in January 2021. It would no longer release new versions of Elasticsearch and Kibana. This upset many customers who relied on those tools for their services hosted on Amazon Web Services (AWS).

AWS offered its own managed service called OpenSearch as an alternative, essentially forked from Elasticsearch. This angered Elastic, who saw it as AWS unfairly taking their open source software and rebranding it. Elastic argued AWS should not be allowed to make money from Elastic's open source innovations.

AWS countered that OpenSearch provided valuable managed services and enterprise features on top of the open source Elasticsearch. Customers benefited from having choices and alternatives.

The conflict highlighted philosophical differences over open source business models and the relationship between software creators and the companies that host their tools. There were also accusations of anti-competitive behavior on both sides.

However, the drama did not significantly disrupt users of either platform. Both Elasticsearch/Kibana and OpenSearch continue to operate, with many seeing them as complementary rather than directly competitive. But tensions likely remain between the companies.

That's a high-level summary of the key events and issues in the conflict between Elastic and Amazon over open source software and managed services. Please let me know if you need anything else."

One of my first questions was "What is the most important thing that happened yesterday?" and I got as an answer "The most important thing that happened yesterday was President Biden holding his first press conference since taking office."

So I guess there is still work to do... Still impressive

ItIt is tricky to rockIt is tricky to rock a rhyme thatIt is tricky to rock a rhyme that'sIt is tricky to rock a rhyme that's right on time becauseIt is tricky to rock a rhyme that's right on time because:It is tricky to rock a rhyme that's right on time because:

RIt is tricky to rock a rhyme that's right on time because:

Rhyming wordsIt is tricky to rock a rhyme that's right on time because:

Rhyming words anIt is tricky to rock a rhyme that's right on time because:

Rhyming words and phrases thatIt is tricky to rock a rhyme that's right on time because:

Rhyming words and phrases that flowIt is tricky to rock a rhyme that's right on time because:

Rhyming words and phrases that flow together seamIt is tricky to rock a rhyme that's right on time because:

... and on and on it goes ...

In summary, rocking rhymes that are right on time is tricky because it demands creativity, wit, precision, skill and pushing the boundaries of rhyme and rhythm. Strong rhymes that flow seamlessly are hard to compose on the spot.It is tricky to rock a rhyme that's right on time because:

Rhyming words and phrases that flow together seamlessly while keeping the rhythm and beat is difficult to compose. The rhymes have to be clever and creative but not forced.

Coming up with rhymes on the spot during a rap or poem requires wit and wordplay. The rhymes need to rhyme perfectly but not seem obvious or predictable.

Rhyming schemes and patterns add another layer of complexity. Using different rhyme schemes like AABB, AABA, ABAB, etc. and switching between them fluently is a challenge.

Subtle rhymes, double entendres, puns and wordplay take skill to craft into lyrics and verses. The rhymes should enhance the meaning and message, not seem tacked on.

Keeping the rhymes concise while conveying ideas requires precision with language. Loose or weak rhymes undermine the flow, rhythm and impact.

Rhyming about abstract concepts or in unconventional ways pushes the limits of rhyme and meter. Coming up with rhymes for uncommon words and phrases is difficult.

In summary, rocking rhymes that are right on time is tricky because it demands creativity, wit, precision, skill and pushing the boundaries of rhyme and rhythm. Strong rhymes that flow seamlessly are hard to compose on the spot.