Maybe this works because it is not even a YaCy problem, more a Solr problem. However, all the simple questions (how to install YaCy, how can I do this and that) can also be answered by this GPT.
Now, I don’t know if anyone of you have a OpenAI account or want to have one. For me this is a very good proof of concept and a motivation to implement the same functionality inside YaCy as well. Using the latest proof-of-concept of adding RAG in YaCy (see Added a RAG Proxy for AI Chat with YaCy · yacy/yacy_search_server@13fbff0 · GitHub) we could work on a YaCy Expert using YaCy.
The YaCy GPT is public, so please try it out and tell me if this is useful for you!
Well, unfortunately yes. I did not know this! I hope that OpenAI will change their policy.
However, I can’t imagine a future where we will not be able to provide such a function ourself!
And, Oh The Oracle’s Master, could you ask the Great Oraculum for solving this issue? My prayers go only in this direction. May the consciousness be with you!
Well, I tried. The GPT responded with a very very long answer. One would have to go into detail and find how much hallucination is in the answer, but partly it looks good:
I just got an email from OpenAI: GPTs are now available for all users, not only ChatGPT Plus:
Hi there,
We’re reaching out because you’ve built a GPT and shared it in the GPT store.
We recently announced that all ChatGPT Free users would soon be able to use GPTs in the GPT Store, in line with our mission to make AI technology accessible to all. Today, GPTs in the Store are now available to all ChatGPT users, allowing more than 100 million weekly active users to experience your GPT and the others in the store.
GPTs now use our newest flagship model, GPT-4o. Given the possibility of increased usage and behavioral changes with a new model, we recommend reviewing and testing your GPT to ensure it continues to perform as intended.
Thank you for building GPTs and introducing new ways to learn, have fun, and be more productive with ChatGPT.
Hi, did the change of that document cache really change performance for anyone?
I found since solr 9.0 the load got quite high and the performance was super low.
In the meantime I found this was becuse the autowarm count for the filter cache got set to 128, which results in autowarming after each commit into the index, which is almost all the time…
Setting it beack to ‘0’ made the the performance being ok again.
And the patch for setting the docCache looks really ugly to me, while there is a clean config in solrconfig.xml. @Orbiter I hesitate to revert your commit, but it really should
I admit the change was ugly but looked like the only thing that would force an effect. I do not know if the solrconfig is actually read by the code because we have an embedded solr. It’s also scary that my changes are actually reviewed in that intensity, however thats a good thing. So what should we do?
Definitely not a halucination, seems reasonate. However, based on what I previously wrote in the forum and github issues.
Do you think it’s possible to implement?
