Jump to content

[::X-System::]

Members
  • Posts

    286
  • Joined

  • Last visited

About [::X-System::]

  • Birthday 06/16/1984

Contact Methods

  • Website URL
    http://splitfire.weebly.com/

Profile Information

  • Gender
    Male
  • Location
    Neverlands
  • Interests
    ¬ mIRC/IRCX scripting<br />¬ Web/Graphical designs<br />¬ Web building<br />¬ Digital Audio equipments<br />¬ Mythology<br />¬ Parasychology<br />¬ Spirituals<br />¬ Metaphysics<br />¬ Operating systems<br />¬ Mind to mind influences<br />¬ Reading
  • Country
    United States

[::X-System::]'s Achievements

  1. I think i will eventually pretty the dialog up a bit, and i guess i'll use MDX coz I'm still racist to it. It's true DCX has got way more functions, but i'm not really a fan of using a 1+ mb dll, leaving aside the stability and mIRC crashing issues.
  2. check my edit and i am not trying to match stuff.com since they are not a real url pattern, i was trying to match tricky patterns like wwwww.blah.com and www.blah.c0m etc, thats what spammers use on the nets I'm on anyways.
  3. u win :< Here is your regex being tested against some false positive patterns, and returned true on all of them: do you still think it's good? If not, feel free to use mine: ; usage $isurl( ) alias isurl { var %p = /(?:^|[][()<>{}'"\s])((?:(?:irc|s?ftp|https?:)\/\/|www\d*\.)[^\s./]+\.(?:\[\S*?]|\(\S*?\)|\{\S*?}|[^][()<>{}'"\s]|['"](?!\s|$|[()\[\]<>]))++)/giS if ($regex($1,%p)) { var %i 1, %rgml while ($regml(%i)) { %rgml = %rgml $ifmatch inc %i } return %rgml } else { return $false } } * Edit: just for the hell of it.. /(?:ftp:\/\/|https?:\/\/|www2?\.)[^<>\.\s]+(?:\.[^<>\.\s]+)+(?:\/[^<>\.\s]+)*|irc:\/\/[^<>\.\s]+(?:\.[^/<>\.\s]+)+(?:\/[^/<>\.\s]*)?\/?(?![^\s\x2c\.])|aim:goim\?screenname=[^\s&]+(?:&message=[^\s&=]+)?/ --~
  4. @The Gate Keeper The * in D*ck isn't a literal, its just coz i can't type D!ck on the forum, it'll be modified to something else, so yes regex is totally error proof specially with /\b ... \b/ around the pattern. I sure know that what I've done has been done before in some form or another, I stated that clearly actually, and i also stated that most if not all of these previous attempts would be below average if compared to nowadays scripting skills and evolution, and that for sure is a fact. Hybrid, for example, didn't have a real spam/swear kicking system, it only had a .mrc file with loads of on text events, one for each word/token, which is totally pathetic and a total waste of space & system resources, leaving aside the script's performance itself. Loops, hash tables, regex and all types of functions that could made the job easier did exist back then, yet the author chose to do it the noobish buggy speed-killing way. That's why i'd call these scripts "Below Average" About banning via regular expressions, ofcourse you don't use the "server" to ban regex patterns, not on IRCx or IRCd servers. You use regex to match patterns and hunt them down, so it's not about server limitations coz its not a server side issue in the first place. Regex existed since creation of mirc but no scripter actually bothered to learn it except for eXonyte if i remember correctly. It's just an example off the top of my head, but check how swear/spam kickers were on kenobi and hybrid, and now imagine them properly coded with loops and regex matching and a cache file with patterns like /fag?(?:g?[eio]t)?/ or /ass?(?:h[o0]le)?/ and do the math yet again, authors always chose the easy way of using basic bitwise operators like isin and iswm, or even worse: writing a full event for each single word. So yeah, i do think all the examples you stated are below average, coz - again - the methods i just stated in my examples are no magic, loops and regex and everything else existed back then, but were not used for some reason. Separate commands is another thing i always hated about these scripts: doing command | command 2 | command 3 instead of using $crlf when/if possible was a common pitfall everyone had in their scripts, and worse: seeing scripts doing sockwrite -tn ... | sockwrite -tn ... | sockwrite -tn ... in kenobi, instead of using $lf to achieve faster performance. I could keep counting pitfalls and weak points that could have been put in a way better/faster and more stable ways all night, but i'm just pointing out examples on the fly. About booting 900 flood bots, that my friend can't be called a botnet attack. MSN never had a sendQ/rcvQ, not like IRCd nets have got anyways. MSN was way less strict regarding the buffer you send to the server, and the buffer the server sends you. For whoever don't know what Sendq/RcvQ are, and what makes them a pain in the neck and makes MSN prots a piece of cake compared to IRCd, here's a short intro: MSN had none of the above, and i could safely assume that most scripts could boot 900 bots and even more in an eye blink, coz none of the above issues were to be taken in consideration, leaving aside that botnet attacks - ones that i see all the time - are usually 3000+ drones, and it takes alot more than luck to block such attacks Least but not last, the "much of your understanding of what you're doing now, came from their work" is entirely false. I learned what i learned by myself and mIRC's help file. The only help i admit asking for is regex help, and i don't recall asking anyone for help except for eXonyte and a couple of Undernet scripters. I totally respect Ozzy and the time he dedicated to mIRC scripting, but by the time Kenobi was being made, i was writing proxy leechers and mIRC based tunnels.
  5. it's using a HORRIBLY long regex to match all types of urls, even the evading type ending with stuff like .c0m etc.
  6. ty err0r, fixed This was never done in either kenobi or hybrid or guarddog, protections in those 3 were normal and - compared to nowadays scripting/scripters - below average, perhaps they were sufficient for IRCx chat networks where not much abuse could take place, but i barely consider stuff like on *:text:http://*:#:{ access # add deny $address($nick,1) | kick # nick } scripting, especially if it was meant for IRCd use. I tried my best to make Absolute flood proof during huge botnets attacks and it has proven it so far, everything is entirely queued and ofcrs all mode-related stuff take $modespl in consideration while queueing. Queueing theory also exists in kicking, almost all kicks are set on ms timers to check for the user's existence before sending the kick command to the server to avoid racing conditions and to keep the sendQ/rcvQ at accepted rates. Another ultimate protection i might add is enhanced drones/bots hunter, it goes like: - a pattern limiter, to allow a certain amount of nicks with the same pattern to join a channel at once. I'm using a $pattern.regex for it eg. $pattern.regex(err0r) = [a-z]+\d[a-z] - *.dnsbl.dronebl.org check - *.dnsbl.proxybl.org check - TOR exit nodes check plus the basic regex checkers that check for nicks validity. eg. vowels/ASCI/digits/weird combinations Regex also became handy with the swear protection, so far i don't think anyone ever came up with a regex-based swear protection. kenobi, hybrid, guarddog and all the rest just used the basic good old isin or iswm or both, which horribly fails and all it does best is triggering on false positives. You don't want to look n00b if your swear prot kicked someone for saying a string like Charles D*ckens, for the existence of `D*ck`, but with regex'd protection matching strings like $regex($1-,/\b(D*ck)\b/i) you'd never have false positives, the same thing applies for the Host masks filter, you wouldn't need to ban a whole subnet or add stuff like ??????!~@* to the ban list anymore, since you can simple ban a certain pattern. /^(.{3})!~\1@/ and /^(.{4,9}).*!~\1@/ are 2 patterns i have on my version of the script, i made the longer one - iirc - to detect bear drones on dalnet (you might want to read about these) * Yet to come: a separate dialog to set/edit various kick messages for the various protections' kicks. Anyways that was just an example of differences between my prots, and the ones in kenobi & hybrid & guarddog. It's all about enhancing
  7. last tab is done, changed the name of the last 2 tabs to Misc. & Misc. 2 ideas & suggestions would be greatly appreciated
  8. pretty much true, he got nothing on me "officialwise", but yeah I think he expects me not to release it since it was built on his request and also that it wouldn't be fair releasing something to ppl for free if someone had it paid for *shrugs* * update: the last tab is almost done, will be posting a ss of it and some ss of the script in action during some huge botnets flood soon
  9. speaking of it, i was chatting with that dude few mins ago and he actually offered me $50 in return of the add on, which i find too much for mSL.
  10. I'm not certain if it's wrong either, will have to ask the one who requested it and i will sure release it if that's ok for him.
  11. Something i've been working on the past few days, originally requested by a DALnet pal. Not sure if It'll be right to release it, will look into that late. (Still working on Tab 6: "Drones and random patterns")
  12. //timertopvoices 0 21600 /msg #channel <whatever u want>
  13. $server will not be irc.koach.com, Koach's servers are irc[1-4].koach.com, however, best and most reliable way for an autojoiner is $network, and you don't really need 2 lines of /join since mIRC allows you to /join #chan,#chan2,#chan3
  14. on *:CONNECT: { if ($network == koach.com) { .raw -q join -n #tg007,#test } elseif ($network == buzzen) { .raw -q join %#!!~\bSoulFly\b~!! } }
×
×
  • Create New...