unek / node-tip-bot Goto Github PK

i killed the daemon and right before i killed the bot, a user went n did a massive rain which triggered another small rain bot and now the balances are all way off, some are in the high negatives, and some have 10 times the amount of coins than are in the actual wallet. is there a way i can revert this? since each account is tied to a key pair?

Hey there,
so i tried to contact you many times over irc, but it seems that we have different time zones.
So i realy need that this bot also works with quakenet.
Please be so nice to contact me: [email protected]
Thnank you!

Hello, I'm just wondering how to get help and terms working. I've tried enabling it in channel and pm and it's not exporting any data.

the bot suddenly started ignoring my !rain and !tip commands, but still shows me my balance when i !balance

no other users are affected; everyone else is able to rain and tip.

I disabled .rain on our tipbob because it was in a channel where it was being 'over used' and seemed to be annoying some folks. The channel seemed to appreciate it for the most part, but some users over usage, with foul intent, could have been considered to be intentionally provoking the stark fist of removal.. But, as the tipbob's master, I would still like to be able to use .rain.

Maybe I'm exceeding the scope of a simple tipbot =p
But it would be nice to have some user-flags implemented.
Doing so would also solve my /ignore user request.

I tried to connect with theses settings:
connection:
host: irc.rizon.net
port: 9999
secure: true
debug: true

And I got these errors:
info: Connecting to coind...
info: Running webadmin on port 3901
info: Connecting to the server...
info: Connected to JSON RPC API. Current total balance is 0Đ
23 Jun 14:24:59 - Connection got "close" event
23 Jun 14:24:59 - Disconnected: reconnecting
23 Jun 14:24:59 - Waiting 2000ms before retrying
23 Jun 14:24:59 - Unhandled message: { prefix: 'irc.rizon.io',
server: 'irc.rizon.io',
command: '439',
rawCommand: '439',
commandType: 'normal',
args: [ '*', 'Please wait while we process your connection.' ] }
23 Jun 14:24:59 - Connection got "end" event

!rain 1752178.087936
[21:03] <+dogedShibeBot> uphoria rained 97343.22710756 DOGED upon BrownPanick, Dj4x, dogedRADIO, cryptoloot, dogeb0t, Maseyo, buZz, gnomethrower, DBR, dogedDEV, jwinterm, mogreen, OnlyOne, Erlin, Rawnie, dogedart, Erock23, [Curious]Koala.
[21:03] !balance
[21:03] <+dogedShibeBot> uphoria has -0.000008 DOGED (unconfirmed: 0 DOGED)

It would be GREAT if the tipbot would keep track of the users who've spoken in the last xx minutes, and ONLY .rain upon them..

It would also be GREAT if the tipbot would NEVER rain upon itself.

I have disabled .rain pub/priv commands because it's a waste of good time, coin and Slack - that I have to always go in and move coins around. Expect a small BTC donation. Thank you for your efforts.

There's going to be a bunch of tip bots in a channel and it's going to drive me crazy. Obviously rewriting the tipbot to alter everything to allow for %cmd% would be something that would take time, and taking into account that I don't know how this package operates yet, could you tell me what I need to change to get !tip to be .tip for the time being.

-thanks

It would be very cool and usefull if someone could add !tip [nick] all

What might you do to prevent abuse? Seems repeated .rain commanding will certainly cause tipbot to flood off a server. And some users are just asshats.

Maybe tipbot could /ignore users.. somehow.

Unregistered commands termsand help function correctly but address, balance etc are ignored. status_command variable has been set correctly.

var regexp = new RegExp('^(\S+) ' + settings.connection.status_command + ' (\d)');
assumes ordering of ACC/STATUS as 2nd param

Below is debug log from unrealircd server:

28 Mar 19:40:57 - SEND: PRIVMSG NickServ :STATUS SashaCoe
28 Mar 19:40:57 - GOT MESSAGE from SashaCoe: !address
28 Mar 19:40:58 - GOT NOTICE from "NickServ": "STATUS SashaCoe 3"
28 Mar 19:44:25 - SEND: PRIVMSG NickServ :STATUS SashaCoe
28 Mar 19:44:25 - GOT MESSAGE from SashaCoe: !balance
28 Mar 19:44:25 - GOT NOTICE from "NickServ": "STATUS SashaCoe 3"

Freenode server:

28 Mar 19:32:52 - SEND: PRIVMSG NickServ :ACC SashaCoe
28 Mar 19:32:52 - GOT MESSAGE from SashaCoe: !balance
28 Mar 19:32:52 - GOT NOTICE from "NickServ": "SashaCoe ACC 3"
28 Mar 19:32:52 - SEND: PRIVMSG SashaCoe :sashacoe has 0Đ (unconfirmed: 0Đ)
28 Mar 19:33:24 - SEND: PRIVMSG NickServ :ACC SashaCoe
28 Mar 19:33:24 - GOT MESSAGE from SashaCoe: !address
28 Mar 19:33:24 - GOT NOTICE from "NickServ": "SashaCoe ACC 3"
28 Mar 19:33:24 - SEND: PRIVMSG SashaCoe :Your deposit address

I would like to see a new command for unregistered users, to display in the help menu.

info
- 'This is a bunch of stuff about the coin'
- 'Coin Stats: 21M 10Min Blocks'
- ' '
- 'HOMEPAGE: http://blahblahblah.com'
- '[ANN]: http://blahblahblah.com'
- 'Wallet URL: http://blahblahblah.com'

Something like that. I'm trying things. No love yet.
If I get it worked out, I'll post it.

If you just ping the bot for balance via PM it includes you in active soaks!
Especially as you wouldn't be able to 'see' it leeching!
You don't even have to know how to code a bot to use this!

(MrPrime from freenode asked me to open this issue!)

I don't understand npm well enough yet to have a clue where to begin, but need to bind the bot to a second adapter / IP. How might I accomplish this.

when trying the rain command, nothing happens at all?

:(

sucks big time ...

Seems the check for 'enough balance' doesnt happen early enough or well enough.
Users can tip 'all their coins' to another user a couple times before it comes back with 'but you only have -128976319827'
Then they do it back and forth and back until they have -all- the coins from the wallet.

VERY UNSECURE, DONT RUN THIS BOT LIVE!!!! VERY UNSECURE, DONT RUN THIS BOT LIVE!!!! VERY UNSECURE, DONT RUN THIS BOT LIVE!!!! VERY UNSECURE, DONT RUN THIS BOT LIVE!!!! VERY UNSECURE, DONT RUN THIS BOT LIVE!!!! VERY UNSECURE, DONT RUN THIS BOT LIVE!!!! VERY UNSECURE, DONT RUN THIS BOT LIVE!!!! VERY UNSECURE, DONT RUN THIS BOT LIVE!!!! VERY UNSECURE, DONT RUN THIS BOT LIVE!!!!