IMO context poisoning is only fatal when you can't see what's going on (eg black box memory systems like ChatGPT memory). The memory system used in the OP is fully white box - you can see every raw LLM request (and see exactly how the memory influenced the final prompt payload).
the core problem is that language/library authors need to provide some way to bridge between different execution contexts, like containing these different contexts (sync / async) under FSMs and then providing some sort of communication channel between both.
This would generally just discourage open software in general. Rebble is a non-profit and should not pretend to "own" any software or content. Eric didn't do things the polite way, but either way there's nothing to discuss here. Claiming that someone can steal something that is open source implies that they own said open source code / content. that's not how any of this works.
Reselling open source content is always going to be bad taste.
If AI would truly love it, then that seems like the best-case ATS-optimized resume to me. The right tool for the job. Imagine using real people to review applicants - what is this, the 1800s?
It's funny how Japanese contributors often go nuclear whenever things don't go their way instead of communicating etc. Bugs happen. this is tech. open communication is always the way to go before escalation. we see the same phenomenon in git, ruby etc etc etc.
Ironically, Japanese work culture encourages over-communication. It seems that open-source is considered a counter-culture that they want to escape japanese work culture from.
>In October 22, the sumobot was introduced to Japanese KB articles. I cannot accept its behavior and no words. [...] It has been working now without our acceptance, without controls, without communications.
How exactly did you manage to place the blame for no communication on Japanese contributors here given the actual complaint in question?
Because given the nature and scope of the complaint, they should have disclosed prior communication. It is clear here that they probably attempted, poorly, to communicate but ultimately chose to nuke the relationship instead, claiming that they have a monopoly over japanese translations.
I live in Japan so I have seen what danieltanfh95 describes many times in person. Japanese people at work seem to have infinite patience with whatever random bullshit their company will ask for, but outside of work they get easily frustrated when things don't go the way they expect.
It is really just BS. These are just basic DSA stuff. We deployed a real world solution by doing of all of that on our side. It's not magic. It's engineering.
This is honestly not better than the LLM-powered double booking system where i just record in plain text, and have the LLM convert it into journal entries. the entire thing is in plain text and backed by git+remote. Recording finances is the hardest part about tracking finances because you tend to forget/get lazy/need to track across multiple family members etc.
This is solved via LLMs that can transcribe, categorise, convert messy records into structured book keeping.
I remain unconvinced that anything more rigid is more useful.
Manus had 1 marketing gimmick with the agents. That is no longer anything novel.
reply