~help <alias>
gets first 3 lines from section of this wiki page: http://wiki.soylentnews.org/wiki/IRC:exec_aliases
followed by a url
~staff meeting
outputs paragraph in site news slashbox containing the word "meeting", with paras delimited by <br>
scripts can call lib.php function bot_ignore_next() to set a flag in the bot that tells it to ignore the next message, which is useful if outputting aliases that you don't want to be processed (such as for ~help)
~count <nick>
counts number of privmsgs in channel. also indicates over how many days and average of privmsgs per day.
some recent goings on with the exec bot that generally lurks in #Soylent channel on irc.sylnt.us:
- sed supports regex through use of preg_replace (FoobarBazbot's awk script no longer running under exec)
- reserved alias for logging script
- disabled ping script for auto-restart cos it was a disaster (i think i fixed the problem by disabling the ping until connection is established but not going to bother testing for now)
- implemented support for bucket_append messages, which allows creating lists from multiple concurrent processes without fouling each other (needed for users.php which builds lists of channels, nicks and nickserv accounts using list, who and whois irc commands)
- refined the weather script a little as a result of some feedback (thanks to those involved)
- put weather and time functions into lib files to make them accessible from a new welcome script that can (if enabled) show weather and local time on joining a channel (if your nick/location is registered using ~weather-add or ~time-add)
- created switches.php in an attempt to make enabling/disabling features on a per channel basis a little more uniform (used by sed and welcome scripts)
- script created to add suggestions to the wiki, using ~suggest (appends to a section of an article, with bullet formatting)
- added stats aliases ~first, ~last, ~find-first, ~find-last and ~count that make use of cached chat logs
- added interface for adding/editing/deleting ~define sources
- added ~killall admin command to terminate all scripts/programs running under the bot process
- admin setting to ignore/unignore nicks added
- added script start timestamp template for the exec.txt file
hoping to eventually get the nickserv account checking stuff in users.php to a point where i can use it to fix up the player authentication in irciv cos i really wanna get back into that
haf fun :D
===
https://github.com/crutchy-/test
http://wiki.soylentnews.org/wiki/IRC:exec
I didn't pay much attention to this so please excuse me but the garbage processor spat this out today:
Despite accepting all the flawed assumptions such "AI" would itself/themselves be committing the same "criminal" acts of postponement by wasting resources on such a scenario instead of better AI.
Hopefully that's not an example of cryptomnesia.
Anything more intelligent than even me (intended as a low reference point) would have far more interesting things to do than retarded human sadism, the same goes for any $deity worth the title :)
Well that's already too much attention wasted on an idiotic distraction (doesn't matter if it's genuine idiocy or staged).
Here is look at the upcoming changes in August update for Slashcode. We anticipate that this will be deploy within the next week or so, as we are finalizing updates to the subscripion plugin.
The majority of the work done in the past two months has been on Unicode support. The Mighty Buzzard was the point man on this endeavor, and almost single handedly bent slash to his will. The amount of code changes need to make this work was large. All of the slash Perl modules needed to be touched to add utf8 support. Our memcache processor had to be upgraded so that it would not mangle utf8. Form inputs had to be sanitized as Perl sometimes can't determine that what it reads in is a utf8 string without being told so specifically.
During our testing of utf8 we discovered many processes in slash that were deliberately breaking utf8. These all had to be tracked down and squashed. Our MySQL database in not set to handle 4 byte Unicode and would take a major change to make it comparable, so we are using html entities to handle these characters as needed. We also determined that the filter on submissions and comments were not coded with utf8 in mind. As many of these would be impossible to make utf8 friendly, we removed them. This will make most of you very happy as you will see very few filter errors from now on.
We are currently doing some ongoing testing on utf8 to make sure it works properly. Many thanks to Bytram who is heading up the QA on this. We are hoping that when we release this we do not break anything permanently.
Late in July we were given a mandate to get subscriptions working. As NCommander was taking a much needed vacation the bulk of the work fell on me. NCommander had indicated the changes we wanted to make would be relatively easy. The old slash subscription code was designed to give users that subscribe ad free pages as well as early access to stories. The majority of our community did not want subscribers to have early access to post, because it was thought that some users would abuse this functionality. Also since we do not have ads, we wanted to change the subscription length from number of pages to number of days. These two changes should have been easy to do.
The problem was that the slash subscription module was missing functionality like many of the systems that we have fixed. The PayPal payment system was missing the back end payment processing code, so although a user could pay for a subscription there was nothing to tie the completed transaction back to the website to give the user their subscription. Being PayPal this code was not straight forward to implement, and as of this writing we only have the real-time component working. The back end processor, which would catch payments that complete but fail to reach our systems due issues on redirect, is being hammered out right now by The Mighty Buzzard. It is its own little web engine in Perl that listens for PayPal transactions, verifies, then processes them.
Other subscriber bonuses were also added to the code. One of the biggest is that subscribers will not be throttled by slash's formkeys. They will no longer get the "Slow down cowboy" messages. Another bonus was already in the code and just needed to be turned on. This bonus allows the user to see their entire comment history on their info page. This was a Easter egg to me as I was unaware that it was available until I read the code. The final community requested feature was the ability to turn off the subscriber indication. This was a * that was beside a user name next to a comment. It is now a star and goes well with our new Zoo icons (see below). But the indicator status was stored with the comment at the time it was made. I had to rewrite the code so that the check would happen at display time and it would check the author of the comment to see if they are a subscriber and they do not have the hide_subscription status checked.
As work was being done on the swag store with a bunch of versions of the SoylentNews logo, we noticed that the main site logo on the Wiki was a nicer version than the one on the main site. We used the newly obtained logo source files to update all of the site logos with cleaner ones based on the Wiki logo. This also lead us to pump out two quick site themes. Bada55 and Black IcIcle are based on the two colors used in the logo on each #bada55, and #1c1c1c.
We also had some new topic icons made by user rand. We used some of our original icons, some of rand's, and some that I made, to get our new set of topic icons that are all transparent png files so they will work on the dark themes. This made our Zoo icons (Friend and Foe) look bad, so a quick trip to the internet, to find a free set of similies that would look good at 15px x 15px, fixed that issue.
So as The Mighty Buzzard would say, thank The Mighty Buzzard it you like the changes and blame paulej72 it you hate them :).
exec now supports a reserved <startup> alias, which at the moment executes a script that triggers a sequence of aliases related to starting SedBot(2) in #Soylent and ##.
the <startup> trigger fires when the bot attempts to identify with nickserv, and like other reserved aliases can't be triggered from irc.
my intention is to make scripts to enable easy management of the current sedbot.awk script, unless FoobarBazbot returns beforehand in which case he'll be able to take the reigns.
the advantage of the <startup> alias is that if exec is disconnected temporarily, sedbot will restart when a connection is re-established.
a test was performed by pulling the network cable out of the machine hosting exec and leaving it unplugged for a while. when the cord was eventually plugged back in, exec came back up and restarted sedbot without any intervention.
https://github.com/crutchy-/test/blob/master/irc.php
https://github.com/crutchy-/test/blob/master/irc_lib.php
bot admins now have a little more control over scripts that are executed
to see a listing of running scripts/processes:
~ps
this will generate a list in the format:
[$pid] $shellcmd
to kill a process listed by ~ps:
~kill $pid
if the bot is restarted (~restart) or quits (~q), all processes (including any children) will be killed
bot source code is here: https://github.com/crutchy-/test
if you would like to log an irc channel, you can /invite loggie.
as a backup, exec also has a logging feature.
you can /invite exec to a channel, or if you're not op, go to another channel with exec already in it and do '~join #yourchan'
then if you want to switch logging on, do '~log on'. you can switch off logging using '~log off'
logs are publicly accessible here: http://irciv.us.to/irc_logs
if you want exec to go away, do '~part' from within channel, or '~part #mychan' from any channel with exec in it
everyone uses and abuses poor ol' sedbot in irc, but currently it's only working in #soylent. its also in #test but isn't working there for some reason.
for anyone who just can't live without sedbot functionality in other channels, you can do "/invite exec" and then "~sed on" to enable (or if sedbot makes a grand entrance you can do "~sed off" to disable). if you're not a chanop, you can do "~join #chan" from any other channel with exec already in it (usually #soylent).
works similar to sedbot. doesn't do vowel replacement or regex though.
Check out http://wiki.soylentnews.org/wiki/Feeds for a trial concept in article summary development.
Thanks go to prospectacle for his ideas.
Eventually feed sources will be read from here: http://wiki.soylentnews.org/wiki/Feed_sources (currently read from a file on the bot host).
For the curious:
Bot script: https://github.com/crutchy-/test/blob/master/irc.php
Feeds script: https://github.com/crutchy-/test/blob/master/scripts/feeds.php
Wiki script: https://github.com/crutchy-/test/blob/master/scripts/wiki.php