Built on the generic matrix-appservice-node framework.Written in Node.js, designed to be run using forever.This means Matrix users can join non-existent room aliases and have the application service quickly track an IRC channel and create a room with that alias, allowing the join request to succeed. The bot can lazily create rooms on demand.If you tried to do this as a client-side bot, you would need one event stream connection per virtual user. Events are pushed to the application service directly. The bot can trivially manage hundreds of users.aliases which would then clash with the operation of the bot. This prevents humans from register for #irc_. This prevents humans from registering for user IDs which would then clash with the operation of the bot. The use of the Application Services API means: Ident support : This allows usernames to be authenticated for virtual IRC clients, which means IRC bans can be targeted at the Matrix user rather than the entire application service.IRC nick changing support : Matrix users are no longer forced to use "M-" nicks and can change them by sending "!nick" messages directly to the bridge. ![]() Likewise, Matrix users can invite the virtual user IDs to a room and a PM to the IRC nick will be made. Two-way PM support : IRC users can PM the virtual "M-" users and private Matrix rooms will be created.Dynamic channel-to-matrix room bridging : This allows Matrix users to join any channel on an IRC network, rather than being forced to use one of the specific channels configured.You can specify specific channels and specific room IDs, and messages will be bridged. Specific channel-to-matrix room bridging : This is what the original IRC bot did. ![]() In this blog post, I want to outline some of the features and techniques of the IRC application service which we've been working on over the past few weeks. This spurred the development of Application Services which I introduced in my previous post. As we started to rely on it more and more though, we realised that there were things that were impossible for simple client-side bots to do by themselves. This bot simply sent IRC messages when it received Matrix messages and vice versa. For some time now we've had an IRC bot sitting on specific channels to "bridge" together IRC and Matrix. Naturally, we also use Matrix to communicate with each other. Like a lot of open source projects, we use IRC a lot. This post has now been edited into a guide - you can find the source in github, and the formatted guide on the website!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |