Bots: Difference between revisions
From Buzznet
No edit summary |
No edit summary |
||
(72 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
<strong>BUZZNET IRC NETWORK</strong> | |||
<span style="color:#000000; background:#00FF00"> This Wiki is Under Construction And Updated Every Day....</span> | |||
{| class="wikitable" | '''This is a Private Network. We can remove you at any time, for any reason.''' | ||
== This is a table of notable bots on Buzznet. == | |||
* If you host a bot related to service, join it to #services. | |||
* Make sure he have the flag +b for (Is a Bot) when connect | |||
{| class="wikitable sortable mw-collapsible" | |||
! Nick !! URL !! Hosted by | ! Nick !! URL !! Hosted by | ||
!Channel!! Description | !Channel!! Description | ||
|- | |- | ||
| | |Hopm | ||
| | |https://github.com/ircd-hybrid/hopm | ||
|Koisser | |||
|#Services | |||
|Local open proxy monitor | |||
|- | |||
|D4rk3gg | |||
|none | |||
|Parrot | |||
|#Services | |||
|Random bot. | |||
|- | |- | ||
| | |Pylink | ||
| | |https://github.com/PyLink/PyLink.git | ||
|Parrot | |||
|Anywhere | |||
|Service BOT | |||
|- | |- | ||
| | |Buzznet | ||
| | |https://github.com/PyLink/PyLink.git | ||
| | |Parrot | ||
| | |Anywhere | ||
| | |Service BOT | ||
|- | |- | ||
| | |WikiBot | ||
|https:// | |https://www.mediawiki.org/wiki/Manual:IRC_RC_Bot | ||
| | |Parrot | ||
| | |Anywhere | ||
| | |Wiki Website IRC | ||
|- | |- | ||
| | |Supybot | ||
| | |https://limnoria.net/ | ||
| | |Parrot | ||
| | |Anywhere | ||
| | |Limnoria BOT | ||
|- | |- | ||
| | |OperServ | ||
|https://github.com/ | |https://github.com/anope/anope/archive/refs/tags/2.0.18.tar.gz | ||
| | |Parrot | ||
| | |#Services | ||
| | |Services bots | ||
|- | |- | ||
| | |NickServ | ||
|https://github.com/ | |https://github.com/anope/anope/archive/refs/tags/2.0.18.tar.gz | ||
| | |Parrot | ||
| | |#Services | ||
| | |Services bots | ||
|- | |- | ||
| | |ChanServ | ||
|https:// | |https://github.com/anope/anope/archive/refs/tags/2.0.18.tar.gz | ||
|Parrot | |||
|#Services | |||
|Services bots | |||
|- | |- | ||
| | |Gl0bal | ||
| | |https://github.com/anope/anope/archive/refs/tags/2.0.18.tar.gz | ||
| | |Parrot | ||
| | |#Services | ||
| | |Services bots | ||
|- | |- | ||
| | |BotServ | ||
| | |https://github.com/anope/anope/archive/refs/tags/2.0.18.tar.gz | ||
| | |Parrot | ||
|# | |#Services | ||
| | |Services bots | ||
|- | |- | ||
| | |HostServ | ||
|https://github.com/anope/anope/archive/refs/tags/2.0.18.tar.gz | |||
|https:// | |Parrot | ||
| | |#Services | ||
|# | |Services bots | ||
<nowiki>#</nowiki> | |} | ||
== Getting Started with Limnoria/Supybot == | |||
=== Introduction === | |||
* Ok, so you’ve decided to try out Limnoria. That’s great! | |||
* Limnoria, is the best IRC bot in the world :) | |||
=== Initial Setup === | |||
* <span style="color:#FF0000; background:#00FF00">YOU NEED ROOT</span> | |||
* First create a user call supybot | |||
adduser supybot | |||
* You need to add your user to sudoers list | |||
nano /etc/sudoers | |||
* ADD this line to user privilege specification | |||
supybot ALL=(ALL:ALL) ALL | |||
* Switch to the new user with | |||
su supybot | |||
* Is the time to installation | |||
sudo apt install limnoria | |||
* you may create a ‘runbot’ directory inside your home directory. | |||
mkdir runbot | |||
* Now you can cd to your ‘runbot’ directory, | |||
cd runbot | |||
* and from within it run <code>supybot-wizard</code>, which will walk you through a series of questions to generate the bot config file. | |||
supybot-wizard | |||
* Once you generate the config file, which will be named <code>yourbotnick.conf</code> (where “yourbotnick” is the nick you have chosen for your bot in the wizard), it will be placed in your ‘runbot’ directory. ( | |||
* Now to start the bot, run, still from within the ‘runbot’ directory: | |||
supybot -d yourbotnick.conf | |||
* The operation succeeded xD | |||
== Limnoria Plugins == | |||
* make sure you clone your plugins in this directory ~/runbot/plugins | |||
* is always a good choice to load PluginDownloader do this command in the channel | |||
!load PluginDownloader | |||
=== RelayNext === | |||
git clone <nowiki>https://github.com/jlu5/Limnoria-RelayNext</nowiki> RelayNext | |||
* Load the plugins via #channel | |||
!load RelayNext | |||
* '''RelayNext''' is a next generation relayer system for Limnoria, designed with two-way relays in mind. It is intended as a replacement for the stock Relay plugin, and an alternative to the LinkRelay plugin. | |||
* RelayNext supports relaying between channels with different names, and stores its entries in a database instead of the configuration, preventing various forms of entry corruption. | |||
* You need make sure your bot is connected on the network you want to relay.. creating a relay is simple, simply run: | |||
<code>!relaynext add Your-relay-name #channel1@networkOne #somewhere@networkTwo</code> | |||
=== NuWeather === | |||
git clone <nowiki>https://github.com/jlu5/Limnoria-NuWeather</nowiki> NuWeather | |||
* You need load the plugins | |||
!load NuWeather | |||
* You need set the backend | |||
!config plugins.NuWeather.defaultBackend weatherstack | |||
* Now you need and account to get an API key | |||
* Grab one here https://weatherstack.com/ | |||
* Now time to set the keys | |||
!config plugins.NuWeather.apikeys.weatherstack HEREYOURKEYS | |||
* Now via channel | |||
!setweather YourLocation | |||
!weather | |||
=== Web === | |||
URL Previews in a channel | |||
!load Web | |||
!config channel #Buzznet supybot.plugins.Web.titleSnarfer true | |||
== Manual:IRC RC Bot == | |||
* To create an IRC bot to display recent changes to your Wiki | |||
=== LocalSettings.php === | |||
* Add the following to your local settings file (see $wgRCFeeds): | |||
// IRC # port: 1338 | |||
$wgRCFeeds['ircfeed'] = array( | |||
'formatter' => 'IRCColourfulRCFeedFormatter', | |||
'uri' => 'udp://127.0.0.1:1338', | |||
'add_interwiki_prefix' => false, | |||
'omit_bots' => true, | |||
); | |||
=== SOCAT and ircII (or similar cli irc client) === | |||
* Use socat instead of netcat. Some versions of netcat (on Debian at least) stop listening after receiving the first RC entry, because the wiki changes the port used to send the UDP packet. | |||
socat -T5 - udp4-listen:1338,reuseaddr,fork | ircII -d -c \#<channel> <nick> <irc_server> | |||
* Use -T5 to specify a timeout (5 seconds here) after which each UDP connection will be closed for inactivity. Otherwise, the fork option will create more and more processes for each connection, potentially reaching the open file description limit or exhaust your server resources. | |||
Latest revision as of 18:04, 5 October 2025
BUZZNET IRC NETWORK
This Wiki is Under Construction And Updated Every Day....
This is a Private Network. We can remove you at any time, for any reason.
This is a table of notable bots on Buzznet.
- If you host a bot related to service, join it to #services.
- Make sure he have the flag +b for (Is a Bot) when connect
Getting Started with Limnoria/Supybot
Introduction
- Ok, so you’ve decided to try out Limnoria. That’s great!
- Limnoria, is the best IRC bot in the world :)
Initial Setup
- YOU NEED ROOT
- First create a user call supybot
adduser supybot
- You need to add your user to sudoers list
nano /etc/sudoers
- ADD this line to user privilege specification
supybot ALL=(ALL:ALL) ALL
- Switch to the new user with
su supybot
- Is the time to installation
sudo apt install limnoria
- you may create a ‘runbot’ directory inside your home directory.
mkdir runbot
- Now you can cd to your ‘runbot’ directory,
cd runbot
- and from within it run
supybot-wizard
, which will walk you through a series of questions to generate the bot config file.
supybot-wizard
- Once you generate the config file, which will be named
yourbotnick.conf
(where “yourbotnick” is the nick you have chosen for your bot in the wizard), it will be placed in your ‘runbot’ directory. (
- Now to start the bot, run, still from within the ‘runbot’ directory:
supybot -d yourbotnick.conf
- The operation succeeded xD
Limnoria Plugins
- make sure you clone your plugins in this directory ~/runbot/plugins
- is always a good choice to load PluginDownloader do this command in the channel
!load PluginDownloader
RelayNext
git clone https://github.com/jlu5/Limnoria-RelayNext RelayNext
- Load the plugins via #channel
!load RelayNext
- RelayNext is a next generation relayer system for Limnoria, designed with two-way relays in mind. It is intended as a replacement for the stock Relay plugin, and an alternative to the LinkRelay plugin.
- RelayNext supports relaying between channels with different names, and stores its entries in a database instead of the configuration, preventing various forms of entry corruption.
- You need make sure your bot is connected on the network you want to relay.. creating a relay is simple, simply run:
!relaynext add Your-relay-name #channel1@networkOne #somewhere@networkTwo
NuWeather
git clone https://github.com/jlu5/Limnoria-NuWeather NuWeather
- You need load the plugins
!load NuWeather
- You need set the backend
!config plugins.NuWeather.defaultBackend weatherstack
- Now you need and account to get an API key
- Grab one here https://weatherstack.com/
- Now time to set the keys
!config plugins.NuWeather.apikeys.weatherstack HEREYOURKEYS
- Now via channel
!setweather YourLocation
!weather
Web
URL Previews in a channel
!load Web
!config channel #Buzznet supybot.plugins.Web.titleSnarfer true
Manual:IRC RC Bot
- To create an IRC bot to display recent changes to your Wiki
LocalSettings.php
- Add the following to your local settings file (see $wgRCFeeds):
// IRC # port: 1338 $wgRCFeeds['ircfeed'] = array( 'formatter' => 'IRCColourfulRCFeedFormatter', 'uri' => 'udp://127.0.0.1:1338', 'add_interwiki_prefix' => false, 'omit_bots' => true, );
SOCAT and ircII (or similar cli irc client)
- Use socat instead of netcat. Some versions of netcat (on Debian at least) stop listening after receiving the first RC entry, because the wiki changes the port used to send the UDP packet.
socat -T5 - udp4-listen:1338,reuseaddr,fork | ircII -d -c \#<channel> <nick> <irc_server>
- Use -T5 to specify a timeout (5 seconds here) after which each UDP connection will be closed for inactivity. Otherwise, the fork option will create more and more processes for each connection, potentially reaching the open file description limit or exhaust your server resources.