You're freaking kidding me

@RedwolfPrograms When you get the chance, give it another go, I think I fixed it

No old Sandbox posts

Also, I've updated main.py to use UTC time

@ChartZBelatedly Looks like it's working, nothing errored

@RedwolfPrograms Perfect :D

So the problem was something with the bot itself?

In which case, I think we should switch DEBUG to False and just let it run for the next couple of days

@RedwolfPrograms I'd changed the password for the gmail login, but stack exchange hadn't updated the change

I was logging in via gmail when I tested it, the bot was logging in through SE

So all I should need to do is have it run on startup?

(I have it reboot once a week)

@RedwolfPrograms Yeah, I think so

So long as main.py is running, it'll handle the "once per day" activity stuff

@ChartZBelatedly Does the script use the CPU when it's waiting? uptime shows the CPU is constantly working while it's running.

@RedwolfPrograms Yeah, it sticks itself in a while loop, but it shouldn't take up a significant amount of processing power (or at least it doesn't on my computer)

If you've got a way to just auto run a script at a specific time so that it doesn't use the CPU during "downtime", I'm happy to change main.py so that it just sends a message when run

Sounds good, thanks!

@RedwolfPrograms Updated the private repo, should now just send the message when main.py is run

You might want to wait a few minutes, my testing's hit into the rate limiting again :/

It should run at 00:00 UTC, right?

1:00 UTC. I changed it cause apparently the network scripts run at 00:00 UTC so can cause lag

Okay, it should be set up now.

Is it fine if I test it?

Yeah go ahead

There aren't any posts from a week ago tho, so it won't send any messages

No errors, looks like it works

Nice, let's hope it keeps going :P