I can confirm the code is working, But really, I can't see the point of a script, Could of just pointed people to the website concerned. Screenshot of Result: http://puu.sh/Cpn7
Actually the MuteBan's I know of are these:
UnrealIRCd: +b ~q:nick!ident@host
InspIRCd: +b m:nick!ident@host
Hyperion: +q nick!ident@host
and I have already written a script which works Cross-Network here: http://www.hawkee.com/snippet/7421/
Crikey, You make scripting look easy Jethro_
I edited the script slightly as well, to get a list of users on channel entry/leave/server quit and nickname changes, also this is stored in a %serv1user and %serv2user variables, which also adds a new !ul command which will then show serv1 users a list of users from serv2 and vice-versa.
ChiefDean is welcome to use my updated script if he wishes: http://pastebin.com/LPSjZb54
After further examination this script fails to pickup quit+name changes, as there is no channel information passed along with those modes, I have got them both working via the following code:
on *:nick: {
if ($network = %serv1) { relay %serv2 .msg %chan2 : $+ $network $+ : $nick -> $newnick }
elseif ($network = %serv2) { relay %serv1 .msg %chan1 : $+ $network $+ : $nick -> $newnick }
}
on *:quit: {
if ($network = %serv1) { relay %serv2 .msg %chan2 : $+ $network $+ : $nick Quit with Reason: $1- }
elseif ($network = %serv2) { relay %serv1 .msg %chan1 : $+ $network $+ : $nick Quit with Reason: $1- }
}
Great Script ChiefDean, I've found it very useful :)
No dude, I meant is there a way of it converting the .addauth nick:pass into the bXl0d2l0dGVybmFtZTpteXBhc3M= then passing it onto the Script.
So you'd do .addauth nick:pass then the script iself, would encrypt the nick:pass part and them store it?
Example:
/msg Bot .addauth nick:pass
nick:pass >> bXl0d2l0dGVybmFtZTpteXBhc3M=
bXl0d2l0dGVybmFtZTpteXBhc3M= is sent to twitter, and also stored in the TwitterAuth and in the hashfile.
Please clarify my first point dude? the weird number thing, considering most users wont have "commandline" access to the Bot in order to generate the weird number, it's impossible for another user to add themselves once you've allowed them via the Bot itself.
like if you did: .addauth nick:pass then you'd do the encoding: $encode($2-,m) and then send it onto the script, thus the user would only need to perform 1 step instead of all the ones you've stated: eg.
1) Bot owner authorizes user (via the Menu System you added)
2) User Types: /msg Bot .addauth mytwittername:mypass
3) The bot then converts that string into that weird thing (in this example: bXl0d2l0dGVybmFtZTpteXBhc3M=) and then sends onto the script..
I think this would be much easier from the users point-of-view.
Sorry if I sound critical, But a couple of points:
3rd: Encode your username:password combination.
Type //echo -a $encode(username:password,m)
Wouldnt it be easier to add that into the script, so the user can just do this instead>> ".addauth tweetnick tweetpass"
incidentally, I've added this code to my bot, which helps in the above:
on *:TEXT:!enc*:?: {
.msg $nick Encoded: $encode($2-,m)
}
Also are these user+pass's saved in any sence, like if I restart my Bot, would I have to redo everything.
And this...
21:38:27 !tweet Will it be a sunny day tomorrow....
21:38:28 Updating Status.. Please Wait...
21:38:31 Status Updated.
I reckon that would be better /notice'd to the user
what this script is missing, is an ability to have other users use it, once they register with the script..
for example:
/msg Bot !twreg twittername twitterpass You are now registered under your Nickname "Me" to perform twitter updates type !tweet [whatever] on a channel. !tweet last night I met fred.. blah -Bot- Posted your Update to Twitter under Twittername "twittername"Ah ok, It was only a suggestion anyways, the hashtag thing would be good, dont you think, so people could just click the link and travel there.
Currently the #hashtags in IRC serve as a channel name, so clicking it would take you to the channel name it states.
I've just figured this out, I've done it like follows:
var %lasttweet $replace(%lasttweet,$chr(35),http://www.twitter.com/search?q= $+ $chr(35) $+ )
It does work well, I've added it into that section you posted %lasttweet :)
FordLawnmower, Any chance of converting the Hashtag links into a clickable link?
for example: #hashtag
http://twitter.com/search?q=%23hashtag
also please can you confirm/deny my previous message, Thanks dude :)
This simply will not work on some networks, as you will get messages similar to this:
A better way would be to do it via ChanServ, with the following aliases:
alias owner { /msg ChanServ OWNER $chan }
alias deowner ( /msg ChanServ DEOWNER $chan }
alias protect { /msg ChanServ PROTECT $chan $1 }
alias deprotect { /msg ChanServ DEPROTECT $chan $1 }
alias op { /msg ChanServ OP $chan $1 }
alias deop { /msg ChanServ DEOP $chan $1 }
alias halfop { /msg ChanServ HALFOP $chan $1 }
alias dehalfop { /msg ChanServ DEHALFOP $chan $1 }
NOTE: Owner mode usually doesnt allow opping others, but Protect downwards will do, to op someone else, its a case of putting thier name after the command, example: /protect nick, /op nick etc. This will only work if you have rights under ChanServ to give other people op rights though.
Dunno if this would be of benefit, but the "via txt" or "via web" could be useful additions to this script, possibly along with the "real name" (eg. @bobbyllew is Robert Llewellyn for example)
eg. tweet here [via tweetdeck]
or tweet here [Robert Llewellyn via tweetdeck)
Only ideas though, this script ROCKS!
I'm using the "Message (msg #channel) method, I've tried several things, But for some reason it's not working :(
The actual line doesnt appear to be called by the script, so maybe it's in the wrong place.
Sorry to be a pain, I've tried using an ON INPUT but that apparently only allows for actual keyboard input into the bot (doesnt detect the tweets incoming)