IRC: Difference between revisions
Sir Finkus (talk | contribs) |
Sir Finkus (talk | contribs) |
||
| Line 124: | Line 124: | ||
| #debug || no || bot error spew || [[User:chromas|chromas]] | | #debug || no || bot error spew || [[User:chromas|chromas]] | ||
|- | |- | ||
| #comments || | | #comments || yes || soylentnews.org comments feed || [[User:crutchy|crutchy]] | ||
|- | |- | ||
| #github || no || ~github-list repos push feed - checked every 5 mins || [[User:crutchy|crutchy]] | | #github || no || ~github-list repos push feed - checked every 5 mins || [[User:crutchy|crutchy]] | ||
Revision as of 10:32, 15 September 2016
Contact chat@soylentnews.org if you are interested in working on one of these projects. Also, the IRC Page has information about getting started with IRC, and the IRC vision is worth checking out.
Who we are
| IRC Team Main Page | ||
|---|---|---|
|
nick |
position |
timezone |
| juggs (AKA Deucalion) | Co-team leader | UTC+1 (BST) |
| paulej72 | Member | UTC-4 (EDT) |
Retired Members
Former members of the IRC team that have lost their roles due to inactivity or retirement
| Former members | ||
|---|---|---|
|
nick |
position |
timezone |
| xlefay | Co-team leader | UTC+2 (CEST) |
| FunPika | Member | UTC-4 (EDT) |
| Landon | Member | ? |
Current Projects
Chat bot (Python)
- ELIZA module that uses Futurama personalities (to match the bot's current nick)
- Modify bot logging to match existing formats (mIRC preferably)
Services (C)
- Single sign on against the website (coordinate with NCommander)
- Get the web IRC to use the website's sessions to sign in
Documentation
- Quick-Start/How-to guide for staff members (.op .topic nickserv commands etc.)
Misc bots
- Anyone wanting to join existing bot development projects should contact the developer(s) noted below.
IRC Games
- NerdRPG
Dependencies
- servers
- bots
Channels
Official channels
- Unless otherwise noted, channels are NOT considered "safe for work"
| Channel | Description | Maintained by |
|---|---|---|
| #soylent | General chat/lobby | All SoylentNews Staff |
| #staff | Public Staff channel - Everyone's welcome to join, but messages from non-voiced are only send to the ops in the channel | All SoylentNews Staff. |
| #editorial | The home of the SoylentNews editors, here you can volunteer for duty, report typo's & ask for submission tips and the like. | Editors & IRC Staff. |
| #dev | The home of and for developers that help develop our fork of SlashCode. | Development team & IRC staff. |
| #help | This is the IRC help channel, where IRC operators and others provide help and answer any questions related to IRC you may have. | IRC Staff. |
| #sysops | This is the Sysops homefront, where most of the magic happens. We maintain the servers and services. | Sysops & IRC Staff. |
| #wiki | This is the Wiki's channel, nothing much happens here except for a bot reporting our every edit on the wiki! | IRC Staff. |
| #irpg | This is our "nerdRPG"'s (our fork of idleRPG) channel, feel free to idle along! | IRC Staff. |
| #test | Main testing chambers, feel free to test anything in here (just be friendly & be considerative) | IRC Staff. |
Private establishments (unofficial)
| Channel | NSFW | Description | Maintained by |
|---|---|---|---|
| ## | yes | mostly about bacon and stuff | crutchy |
| # | yes | the batcave; bot testing/borking, random chaos, exec's home | Alberto |
| #derp | aqu4bot's origin and the portal to Universe 2. Bring own peanut butter. | Subsentient | |
| #sublight | Sublight's bot home ground | xlefay | |
| #rss-bot | no | various rss/atom feeds | juggs |
| #debug | no | bot error spew | chromas |
| #comments | yes | soylentnews.org comments feed | crutchy |
| #github | no | ~github-list repos push feed - checked every 5 mins | crutchy |
- NSFW = not safe for work / kids /family (contains adult themes and profanity)
Bots
There are a few bots lurking in the Soylent IRC channels besides the services mentioned above.
Anyone wishing to develop bots should use #test or # for testing.
Please avoid flooding in private establishments and official channels (except #test and #). The #debug channel is used by bots for public error reporting (if dumping errors to #debug, bots should ideally be set to not respond to commands in that channel to prevent race/infinite loop conditions).
| nick | channels | triggers | devs/ops/hosts | source | tasks | usage/notes |
|---|---|---|---|---|---|---|
| aqu4 |
|
|
|
http://github.com/Subsentient/aqu4bot |
|
|
| Bender |
|
|
|
|
| |
| ciri |
|
|
| |||
| exec |
|
|
http://sylnt.us/execsrc |
| ||
| Loggie |
|
|
| |||
| Hedonismbot |
|
|
|
|
||
| NerdRPG |
|
|
||||
| MrPlow |
|
|
|
|
| |
| perlbot |
|
|||||
| PlowKing |
|
|||||
| Regurgitator |
|
|
|
Eggdrop v1.8.0+fixbotnetloop http://www.egghelp.org/files.htm |
|
|
| SedBot |
|
https://github.com/FoobarBazbot/sedbot |
|
| ||
| SoylentMUD | ||||||
| sublight |
|
|||||
| tama |
|
|
||||
| WikiRC |
|
|
||||
| x |
|
|
http://sylnt.us/execsrc |
|
Bot projects / task ideas
- IRCiv is currently under development for the exec bot and is intended to be a civilization-like building game played on IRC.
- a Soylent PBC board meeting assistant script is currently under development for the exec bot, intended for minute taking and publishing on the wiki. See IRC:exec#Meeting_assistant for more details.
- an IRC voting system. refer to IRC:exec#Proposed_IRC_voting_system for details.
- returning data from the SoylentNews using the SlashCode API
- IRC:exec suggestions
Information for Sysops / IRC admins
Server Related Info
IRC services are now served up by beryllium. The core IRC services as well as several bots live on this server. They are mostly run from the sylnt user account out of /home/sylnt/
Start and stop scripts are in the ~/bin directory. start.all and stop.all will start and stop each of the services below with the appropriate script in a proper order. start.all is also set in sylnt's crontab to start at reboot. Individual services can be stopped or started with the appropriate script stop.service or start.service where .service is replaced with the suffix listed in the table below.
The services each have a cron.service script, also in ~/bin, that monitors that the service is running and restarts it if it does not find it. This is done by monitoring the pid, set at startup, and seeing if the job is still running. cron.all is run at 10 minute intervals from sylnt's crontab as well.
| IRC Services | |||||
|---|---|---|---|---|---|
|
Service |
Description |
Path |
DNS |
Ports |
start/stop/cron suffix |
| Charybids 3.5.2 | ircd services | ~/charybdis | irc.soylentnews.org | 6667, 6697(ssl) | .charybdis |
| Atheme Services 7.2.6 | a modular IRC Services package | ~/atheme-services | internal only | .atheme | |
| Atheme Iris | web frontend for IRC | ~/atheme-iris | chat.soylentnews.org | 3989 (forwarded from 80) | .iris |
| Bender | jsonbot bot | ~/.jsb | internal only | .bender | |
| Loggie | logging bot | ~/logbot | logs.sylnt.us | 80 | .loggie |
| NerdRPG | local Idle RPG | ~/nerdrpg | internal only | .nerdrpg | |
| Regurgitator | local RSS aggregator based on Eggdrop | ~/irc-bots/Regurgitator | internal only | .regurgitator | |
| WikIRC | wiki log bot | ~/wikirc | internal only | .wikirc | |
| ZNC | IRC Bouncer service (n.b. repo install, config in sylnt home) | ~/.znc | internal only | .znc | |
All of /home/sylnt/ started out as a copy from the original server xlefay setup on his systems. No new files were added to this, only certain services need to be recompiled. Source files for most of the services are found in ~/source, and copies of the original services that ran on original server are in ~/OLD. Test compiles of some of the services were moved to ~/test before bring up the current versions.
Charybdis was compiled with ./configure --prefix=/home/sylnt/charybdis/ --enable-epoll --enable-openssl --enable-ipv6 --disable-assert. Atheme was compiled with $ ./configure --prefix=/home/sylnt/atheme-services. Iris was configure by running ./compile from the ~/atheme-iris directory. The bots did not require a recompile from what was transferred from original server.
Config files were adjusted to set the proper ip addresses for the new server (both IPv4 and IPv6) and to adjust the staff who had admin access.