If your co-workers are getting promotions and raises and you are not, its a you problem. If someone else is getting credit for your work, its a you problem. Given your claims of impeccable work, we are only left to assume its a personality issue.
Its not to say its fair or right, but life is a popularity contest, whether we like it or not. More likeable people get more things, sometimes undeservingly so.
It’s not true that if someone else is getting credit for your work, that’s a you problem.
At my workplace now, there’s a senior staff engineer taking credit for work that was done by someone 3 levels below him. And the senior staff engineer still thinks he is not getting enough credit for his work. The senior staff engineer’s manager has been crediting him for the work the less senior engineer had done, since the less senior engineer is no longer at that team, in forums where the less senior engineer has no access to.
The less senior engineer is plenty likeable. As is the senior staff engineer. But the less senior engineer had left that team, and the senior staff engineer and his manager are unscrupulous, and do what they’d like to their advantage.
If you read the PR, the bad issues are in a few extensions, not the bot itself. The unencrypted oAuth token isn't really a big deal. It should be fixed but its a "if this box is compromised" type thing. Given the nature of clawdbot, you are probably throwing it on a random computer/vps you don't really care about (I hope) without access to anything critical.
You're talking about if a box is compromised, but to clarify, this is hard coded into the source in the repo, not an end-user's credentials (and it's a `client_id` and `client_secret`, not a token): https://github.com/clawdbot/clawdbot/blob/7187c3d06765c9d3a7...
You know, as the rest of us do, that someone has already thrown it loose in the same place where they store their banking information. Oh well, lessons will be learned about containers.
Every time I've tried to actually use gpt-oss 20b it's just gotten stuck in weird feedback loops reminiscent of the time when HAL got shut down back in the year 2001. And these are very simple tests e.g. I try and get it to check today's date from the time tool to get more recent search results from the arxiv tool.
Not really an apples to apples comparison. You are comparing it to core technologies that millions of things sit on. There will always be money for that.
Its almost never correct to rip on a project from a distance. Only two things can happen, one, you are wrong, and the project succeeds. This is a personal catastrophe for your career at that company. Two, you are correct and the project fails. Its rare this will get you enough credibility to make the risk worth it. There are always others that will show up and dogpile as if they "knew" the entire time themselves. You need to be consistently correct about failure to get truly noticed, but then it asks a lot of questions. Why are you still working there? Why don't you have enough influence to prevent it in the first place? "I told you so" rarely accomplishes anything good.
Cool project, but I never found the cloudflare DX desirable compared to self hosted alternatives. A plain old node server in a docker container was much easier to manage, use and is scalable. Cloudflare's system was just a hoop that you needed to jump through to get to the other nice to haves in their cloud.
reply