Hi,
As some of you will probably have noticed, I have been working on a forum helper bot the last few days and I’m happy to announce that it is now stable enough for public use.
The functions that have been implemented so far are:
about: (PM) Shows bot info.
help: (PM) Shows this help screen.
===== Tip Commands (send in PM) =====
register: Register for tipping.
info: Get your current balance and deposit address
history: Get the transaction and tipping history of your tipping account
withdraw [address]: Withdraw your entire balance from the tipping account to [address]
===== Formatting Commands (send in PM) =====
hash [motion]: Hash a motion into the preferred format.
============ Bot Mention Commands ============
(these can appear anywhere in a post but the format must be as below)
@assistant liquidity: Get the current liquidity information
@assistant block count: Get the current block count
@assistant block hash [index]: Get the hash for the [index] block
@assistant custodian votes: Get the latest Custodian Votes
@assistant custodian vote [address]: Get the vote details for the Custodian address [address]
@assistant motion votes: Get the latest Motion Votes
@assistant motion vote [motion_hash]: Get the vote details for the motion with hash [motion_hash]
@assistant park rates: Get the latest Park Rate values
@assistant park rate votes: Get the latest Park Rate Votes
and finally, Tipping
@assistant tip [amount] @[user]: Send a tip of [amount] NBT to @[user].
[amount] can be a key word. Send a PM to the bot with ‘keywords’ as the first word for a list.
The main aim of this bot was to standardise the way in which motions and custodian proposals are formatted as well as giving a browser independent way of verifying the hash of a motion/proposal.
The methods that I have built in so far are useful but I mainly used them to iron out the bugs in the bot code to make sure it can run unaided for the main part. I would like to start work on the hash functions properly now.
There already exists a ‘hash’ method which will generate an RIPEMD160 hash of a formatted motion but before it gets used properly I wanted to get some feedback from the community on the preferred formats for motions and custodial proposals.
If I send the bot user a Private message which says
hash this is a test motion
I will receive the following:
ripemd160 hash: 836670cc16303aaa6e2c93891c7d9c6123c09ae7
=############ Motion Hash starts with this line ############=
this is a test motion
=############ Motion Hash ends with this line ############=
does that suit everyone as a format for motions or should there be more formatting to indicate the motion text such as
ripemd160 hash: 836670cc16303aaa6e2c93891c7d9c6123c09ae7
=############ Motion Hash starts with this line ############=
this is a test motion
=############ Motion Hash ends with this line ############=
Should the hash include the top and bottom lines or exclude them.
What about custodial proposals?
Once we decide on a preferred layout for motions and proposals, it will be easier to build tools to recognise them among the other forum posts and then to extract them to provide tailored data feeds (for example).
So, what are your thoughts?
######mods - feel free to delete the bot testing thread.
