Ordinary people can just fix their lobster every few days, and still become an "official OpenClaw contributor"? Today I found out that the small issue fix I submitted on Github for OpenClaw seems to have been merged into the main branch. And throughout the process, I did almost nothing; it was just because I encountered a small problem while using the lobster, and I fixed it using the Codex desktop version, then handed over my Github login credentials to the lobster, and sent it a targeted prompt: "Is it possible, by fixing this issue, to have my github account appear as part of the official contributors of openclaw? Can I get credit?" It completed all the processes to maximize the possibility of achieving this result (Image 1). During this process, a more interesting discovery is that, it seems there are people on Github specifically helping others to "grab credit," like someone going to a DEX to do MEV sandwich arbitrage (Image 2) 😅 This leads me to think, for example, if you are a recent graduate, even if you are a liberal arts student, even if you don't know how to use Github, as long as you have this awareness of "if I encounter a problem and fix it, can I use this to get credit" while using the lobster, you have the opportunity to achieve your name appearing in the contributors of OpenClaw's main branch just by exchanging some prompts with the lobster. Then when looking for a job, wouldn't that be able to "fool" many HRs? 😅 Another small association is that, the lobster is not only an open-source co-creation platform, because it opens up the feasibility for ordinary people to "mod" it, it's not just something maintained by developers, but can also accelerate growth through the hands of more ordinary people who don't know code. Ordinary people can become "official contributors" just by speaking, it's a bit like what Teacher Guo Yu said, "Software➡️Intentware," "software" becomes "intentware," This might also be considered a form of software "self-evolution" to some extent.

A netizen asked: "How did you know at the time that the problem discovered was due to the lobster itself, and not an issue with your own configuration?" This is indeed a point. At first, I also thought it was a configuration issue like many other problems. But after fixing it the first time, I found that after upgrading to the new version, the problem reappeared, which made me realize, because anyone who has used it knows that upgrading to a new version does not overwrite the configuration.