huh. connection refused, that's a new one, and not something I can help with. You'll have to contact the one running the forum you're connecting to and find out from them why your bot is being refused connection.

Sorry, but that error really isn't something i can sort out on my end. it's on the server side.

@TheWorms
Assuming you're absolutely 100% certain the login credentials are correct in the configuration file, the only two things that come to mind are:

• Check the username. It is case sensitive for logging in via the bot. I keep meaning to fix that but........ yeah havent gotten around to it yet.
• Check the forum key. are you sure you've set it correctly. If you havent set it it will default to https://what.thedailywtf.com which is almost certainly not what you want.

@sic2 said in get all posts:

Hi!

I have a similar question to @louisemcmahon

I can get the most recent posts from the API /api/recent/posts (API route code

I can see that there is no way of getting all posts (at least I do not see it). Do you know if there is a workaround or there is a plan to add this feature?

Thanks!

it sounds like you want the contents of a topic client side to process.

if you have a browser that is ES6 compliant (chrome confirmed, firefox is probably good, not sure about safari, IE is out) then this GIST will work fr downloading a single topic as CSV.

view the gist

to select the topic to download you edit the final line of that script to include the topic ID you wish to save, replacing the example topic id (in this case 20937) with the one you desire.

downloadTopic(20937).then(result=>console.log(result))

then execute the script in your browser console while being on the target forum.

if it complains about window.socket not existing on line 84 of the script, simply refresh the forum with the console open and try again. I've not figured out why, but sometimes chrome can't find the websocket object used by the forums if the console is opened after the page loads.

@Domas-Vileikis okay..... that's strange as heck.....

that's not where i expected that failure to occur.

however i do know what the cause is. and i can help you fix it.

the error occurs trying to load the configuration settings for the forum in order to get the CSRF token to log in. this is done by loading /api/config on your forum.

so, for example, if you were running a bot for this forum the value you would have put in core.forum would be https://community.nodebb.org and so the configuration would be at https://community.nodebb.org/api/config

can you check to make sure that when you visit the URL in your configuration for core.forum you arrive at your forum's home page and that when loading /api/config relative to that URL in the manner i described above your browser loads a JSON document.

if one or both of these manual checks fail then the value you put in the configuration for core.forum is incorrect and needs to be updated. if both checks pass when tried in a browser then it is most likely your forum has some sort of security in place that is preventing sockbot's user agent access to the REST API of the forum. you will need to update the firewall rules in this case to allow sockbot access, or if you are not the administrator of the webserver your forum runs on you will need to ask your server admin to update the firewall rules for you.

hoping this gets you off and running with sockbot,
-Accalia

@jiangcaiyang said in [sockbot] I wanted a robot, So I made one:

I want to know if people use it for malicious perpose?

yes, that's possible.

@jiangcaiyang said in [sockbot] I wanted a robot, So I made one:

For instance, some could run a script that frequently post ADs to our forum, thus cause our forum unable to run normally?

yes, but sockbot is incapable of that, it needs a manually registered account so would be far too quickly banned. there are other bots that run the spam.

@jiangcaiyang said in [sockbot] I wanted a robot, So I made one:

Is it possible to use it without administrative permission?

yes, but i hereby formally declare that anyone doing so with sockbot is a total poopy pants. ;-)

sockbot is meant for fun, not malice.

@Domas-Vileikis hmm... well other than nodebb being very confused with the formatting that looks okay.

can you run the bot as follows and post the results to me via chat? This command will be very verbose with debugging information and may contain sensitive information so please do not post the results publically.

DEBUG=* sockbot config.yml

that command should provide me with additional information to figure out what's happening so we can sort you out. ;-)

@julian true, but as this is a startup error it's highly likely to be caused by a misconfiguration in the config file (usually the wrong URL for the forum)

@Domas-Vileikis interesting error...

could you post the configuration file you are using for the bot (with password redacted for security) so i can take a look at it? most errors like this are simple typos in configuration and should be easy to solve.