this post was submitted on 10 Mar 2024
20 points (100.0% liked)

Lemmy.world Support

3217 readers
69 users here now

Lemmy.world Support

Welcome to the official Lemmy.world Support community! Post your issues or questions about Lemmy.world here.

This community is for issues related to the Lemmy World instance only. For Lemmy software requests or bug reports, please go to the Lemmy github page.

This community is subject to the rules defined here for lemmy.world.

To open a support ticket Static Badge

You can also DM https://lemmy.world/u/lwreport or email report@lemmy.world (PGP Supported) if you need to reach our directly to the admin team.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world

founded 1 year ago
MODERATORS
ruud@lemmy.world
MrKaplan@lemmy.world
jelloeater85@lemmy.world
lwadmin@lemmy.world
Serinus@lemmy.world
20
The Previous Update Broke Our Bot And I Don't Know Why (lemmy.world)
submitted 8 months ago* (last edited 8 months ago) by MMARefugee@lemmy.world to c/support@lemmy.world
6 comments fedilink hide all child comments
 

Hi all, I'm not sure where I should post.

The mod team at mma@kbin.social uses this account to run a bot found here: https://github.com/daniel-lxs/BotIt

What this bot does, it is uses karma criteria on reddit, to grab the links of the best breaking news in the MMA world and automatically post it on here.

It allows our users to catch all the breaking news without having to use Reddit.

We are now getting an incorrect_login error. The previous bot maker is MIA and has left the project.

We lost almost all of our users the last time lemmy prevented this account from posting in some kind of bot purge or something. We got posting privileges back awhile back, but now we are afraid we are going to lose the rest of our users.

Having the bot being able to post breaking news is absolutely crucial for us. Can anyone help?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] BakedCatboy@lemmy.ml 5 points 8 months ago* (last edited 8 months ago) (3 children)

Hmm maybe it's not that simple then. It doesn't look like the JWT is stored so it's probably trying to get a new one when started. The other possible culprit would be if you need to use lemmy-js-library with a major version matching the Lemmy server version.

Assuming the server updated to 0.19.0, the version used by the bot is 0.18.0. You would just need to edit package.json so that the lemmy-js-client line reads:

"lemmy-js-client": "^0.19.0",

Then running npm install or yarn install (or whatever command you used to install dependencies previously)

[โ€“] MMARefugee@lemmy.world 3 points 8 months ago* (last edited 8 months ago) (2 children)

After suggested change:

PS C:\Users***********\Botlt> npm install

npm ERR! code EJSONPARSE

npm ERR! path C:\Users********\Botlt/package.json

npm ERR! JSON.parse Unexpected token "โ€œ" (0x201C) in JSON at position 976 while parsing near "... "lemmy-js-client": โ€œ^0.19.0โ€,\r\n "lin..."

npm ERR! JSON.parse Failed to parse JSON data.

npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.

I went back in and changed it to:

"lemmy-js-client": "^0.19.0-rc.1",

It will now run again, but same incorrect_login error.

[โ€“] BakedCatboy@lemmy.ml 4 points 8 months ago (1 children)

I think that's part of the solution, I skimmed some of the forks and found one that updated the lemmy-js-client to 0.19.2-alpha.3 but they made some code changes too to the authentication code. So maybe trying that fork is worth a shot: https://github.com/thepaperpilot/BotIt

Last changes were last month on that fork

[โ€“] MMARefugee@lemmy.world 4 points 8 months ago* (last edited 8 months ago)

Thanks so much for your help.

I am not programmer, and I didn't even realize there was a fork. Let me root around in there and see what I can find out tomorrow.

Thanks again.