bazbt3 / thmigpen Goto Github PK

At the moment if the script runs unattended it will post the vote totals every time, with a misleading message that there's a new vote been made.

It would be preferable to retain the most recent post number from the previous query and only post if newer votes exist. (Easily managed, the script will not post if there's no text to post.

Highlighted by @teebeuteltier.

thmigask cron job temporarily disabled to not collect more #tmask1804 suggestions.

Is now a good time to implement:

• stop/start commands,
• remote management of poll suggestions' name hashtag, subtitle, Patter room number for the display of suggestions,
• increased delay between bot responses

The script can list individual votes but there's no totalling yet.

Unsure whether to implement.

Possible strategies:

• Allow multiple votes (current behaviour),
• Disallow entries after the first (next-easiest to implement),
• Replace earlier entries with the most recent.

Mention all whether successful or not.

It's possible reliance on an RSS feed will be subject to a limit on the items available within it. Storing the data removes this limitation, subject to an appropriate time between polling the feed.

May not be an issue; polls are unlikely to have heavy use with short intervals between votes.

Once the hashtag appears in the public timeline thmigpoll will report it; not desirable to see it in the votes even if invalid.

I have no idea if I need to do this or if it will be valid.

Test for an entry without a hash, place test before the main hashtag test, add suitable text to invalidate the entry, advise the user to redo.

Every module is based on thmigpen, and is of the form v0.1.n, but the 0.1 is now effectively meaningless. Also it's stopping releases being meaningful (they're not being used.)

Retaining failures is a bit anti-social!