Jump to content

Search the Community

Showing results for tags 'IRC'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • ChainScriptz
    • News
    • Site Updates
    • Add Links
    • Feedback and Comments
  • Miscellaneous
    • Welcome Intro
    • Jokes
    • Chit Chat
    • Radio Stations
    • Hot Picks
    • Test Forum
  • IRC Help and News
    • Scripting Help
    • IRCd Snippets
    • IRCd Chat
    • Chat Networks
    • Eggdrop
    • Script Reviews
    • mIRC Chat
    • IRC Servers & Rooms
    • mIRC Tutorials
    • IRC Clients
  • Tutorials
    • IRC Network Tutorials
    • IRC Client Tutorials
  • Coding Corner
    • WebSite Corner
  • Archives
    • MSN Chat
    • Defunct Chat Networks
    • Gallery
    • Old Scripting site archives
  • Sparkpea
  • Oasiz Chat
  • Phreik Chat
  • Icons & Toolbars
  • Koach.com
  • MTS Themes
  • MSN Old Scriptz
  • New Downloads
  • Support Files & DLL's
  • Vibe SN
  • Maztal
  • Slovenain Scriptz
  • Italian Scriptz
  • Turkish IRC Scriptz
  • Greek Scriptz
  • Script Support Files & DLL's
  • Groups
  • Security Software - Daily Updates
  • Security Programs - Updates
  • General Software - Updates
  • Other Operating Systems - Updates
  • Social Networks
  • Software Reviews
  • Security News and Alerts
  • Virus, Spyware and Trojan Removal
  • Security Bulletins


  • Info Addons
  • Buzzen
    • Buzzen Addons
    • Buzzen Archives
  • Sparkpea (ircwx)
    • Sparkpea Scripts (ircwx)
    • Sparkpea Connections (ircwx)
  • Chat Club
  • Evolutionchat
  • Essential chat
  • Scriptz(IRC)
  • IRC Bots
  • International Scripts(IRC)
  • Multiconn Scripts
  • TCN
  • Net4110
  • Script Support Files & DLL's
  • IRC Administration Resources
  • IRCd's
  • Server Clients
  • Phoenix Chat
  • Scripting Essentials
  • Phreik Chat
    • Addons
    • Games
  • MSN Archive Scripts
    • Addons
    • War Scriptz
    • MSN Addons
  • Sparkpea Scripts
    • Greek IRC Scriptz
    • Sparkpea Connections
    • Italian Scriptz
    • Sparkpea Addons
    • Slovenain Scriptz
    • Sparkpea Vincula Scripts
    • Turkish IRC Scriptz
    • sparkpea Trivia & Game scripts
    • Swedish Scripts
    • Russian Scriptz
    • French Scriptz
  • Tutorials
  • EggDrop
    • Anti-Spam Scripts
    • Info Scripts
  • Dlls

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 25 results

  1. Our website address https://www.wixchat.org Introductions Thank you very much for all those that involved in giving a good commitment and making "mIRC Wixchat Server" going smoothly well and stand firm until now. In a new millenium and modern world nowadays the application of "mIRC" to be somewhat outdated since it was launch in 1996, it was a first apps that builded for users to communicate and messaging without no boundaries. Between an era of its glorious age in 1996 - 2010, it was amongs a very popular social chat client that connecting peoples all around the world to communicates into each others and still carry out an outstanding performance until now. "Wixchat Server Network" has been using the same IRCD Server from Webmaster Incorporated known as "Webchat Server" founded by Sir Mark Owen. "Wixchat Server" is originally a server for opers to learn and practicing commands, but after users in "Webchat" has decreased then "Wixchat" has taken placed to become a "Second Home" for "Webchat’s Server" after "Unitedchat", this server has been using CR which is the same versions with Unitedchat. Management Management teams is trying to give full efforts to all users those connecting with Wixchat IRC Server Network, we have an experienced technical advisor and staffs in Network/Hosting/Shell etc, so you don't have to worry about your safety while in the Server. Your security is our priority. Your security is our priority. WixChat Founder Read More @https://www.wixchat.org/
  2. WHAT'S NEWInspIRCd v3.6.0 is now available, download it from the releases page. This release fixes a crash bug in the pgsql module as well as adding several minor features. Most notably: Added <class:snomasks> to allow configuring the snomasks that a server operator can use.Added support for the IRCv3 SETNAME specification.Added support for using environment variables in the server configuration using the &env.FOO; syntax.Fixed a crash in the pgsql module when connecting to a server fails.Fixed a bug where previously changed display hostnames would be reset when a hostname lookup finishes.Improved the error message shown when trying to load a module which is too old or too new for the current version.No breaking configuration changes have been made since the v3.0.0 release but if you are upgrading from v2 please consult our list of config changes in v3. The full change log can be found on the docs site or on GitHub.
  3. chain

    Interesting Read

    A WALK DOWN MEMORY LANEAlthough I was too young to read or write at the time it was created, and didn’t encounter it until later in my teenage years, IRC has been a major part of my life, and it most certainly defined who I am today. Once it entered my life, IRC took me far beyond the countryside village I was growing up in, and opened up a whole new world for me. It was in fact mIRC’s built-in scripting language that sparked my very first interest in programming, bots and bouncers that made me enter the realms of Linux, and the Wild West times of internet warfare that got me curious about networking and security. By the time IRC reached its peak in the early 2000’s, my entire social life had practically ceased to exist outside of it, and although other factors played a role in it as well, it is not a coincidence that I eventually ended up living in the very same city where IRC was born. IRC’s Influence On TechnologyWhile those are of course just personal, anecdotal experiences, there’s a far bigger picture to it, and IRC has played an important role in the development of the internet itself. Take IPv6 for example: we’ve heard for decades how the IPv4 address space is soon going to be exhausted, and IPv6 has been around as the promising savior for the majority of that time already. Yet it’s only become relevant to the wider public in the last few years, with ISPs slowly adapting to offer native IPv6 connections. Meanwhile, IRC servers supported IPv6 at the end of the 90’s, providing an actual real-world application for the new protocol, and an incentive for projects like XS26 and SixXS that offered IPv6 access to the general public by tunneling it over IPv4. For normies, IPv6 is about magic. For IRC users, it’s real.For anyone interested in anything related to networks or server administration, this was a wonderfully exciting new playground, and with the incomprehensible vast amount of addresses available within the IPv6 space, you could keep yourself busy for days just thinking of ways to put in perspective the number of IP addresses you had at your own, personal disposal now. But while you could have used a unique IP for each and every website request you ever make, it was in the end IRC that provided the best experimental environment for it, especially as it meant a virtually unlimited amount of possible IRC connections. This made it a lot easier to run several clients at once, even offering it as a service to others, and of course increase the presence of botnets, both for good and for evil. After all, IRC has always been the early internet battle field. Its general structure with interconnected servers, and channels with different privilege levels and authorities easily attracted rivalry and caused power struggles. Taking over channels became a favorite pastime for some people, and entire IRC crews have formed with the sole intention to terrorize and seize power over channels. These were the untamed times of attacking individual network connections to remove the channel operators or protective bots, large-scale DDoS attacks against IRC servers to cause netsplits and gain operator status on an isolated server, compromising other machines to run additional clients or bots for stronger numbers, or to circumvent geographical limitations of servers in other parts of the world. While those attacks weren’t necessarily new, IRC warfare gave somewhat of a wider and seemingly less consequential purpose for them, even if it was just for virtual dominance and the ego. They became common enough to raise awareness of weaknesses and vulnerabilities in networks and operating systems these attacks were exploiting, which over time improved their overall security. IRC’s Influence On SocietyBut the technical aspects aside, IRC has always been social. Of course, communicating with strangers on the internet wasn’t new, UseNet and BBSes had been around for years, but connecting people all over the world with each other in real time offered whole new possibilities. Chances are you would find channels dedicated to your city or area, to your hobbies and other interests, and all kinds of general chitter-chatter. You could get in contact with strangers you probably never would have met otherwise, sharing the same interests and discussions, free from most bias and prejudice. You could get in touch with opinions and life circumstances outside your own bubble, and you could get to know a person without ever seeing them. The world felt never bigger yet so intimate at the same time. IRC formed a life of its own that overlapped with the real world, and sparked new ventures in the online world. Channels formed ecosystems of their own, a unity to identify with. They had their own websites and held semi-regular user meetings where everyone would gather in a pub or a field outside town. Offline relationships started in IRC. The anonymous strangers who you only referred to by their nick suddenly became real persons. Predecessors of social media platforms emerged to follow-up your IRC presence, with Finland’s irc-galleria still alive and kicking to this date. Altogether, it was a wild and oftentimes surreal experience — no doubt nostalgia plays its role here, too. But the internet has simply changed since. IRC servers were predominantly run by volunteers in universities, research institutes, ISPs, and some smaller, pioneering tech companies. It was a free and open space, a place for exploration, with all the pros and cons that comes along with that. It was a landscape of thousands of individual channels, all doing their own thing, having their own rules and customs, and their own set of people in charge to keep things in control. IRC operators kept an eye on the servers and the network itself, but generally didn’t bother much about channel-internal business if they weren’t actively a part of it, as long as everything else was peaceful. It was everyone for themselves, but still together. Sadly, that doesn’t fit too well in today’s surroundings anymore. THE FUTURE OF IRCSo, is Mozilla’s decisions to abandon IRC going to have a larger impact on the remaining networks? Probably not. IRC’s decline isn’t a recent development, and since irc.mozilla.org is a standalone system for development inside Mozilla itself, in the big picture, it’s really more their personal problem. But as mentioned in the beginning, with the right angle, they might contribute a worthy replacement — and that could be a whole different story for IRC itself then. Admittedly, IRC does feel archaic today, and clearly stems from a time where data didn’t just magically appear from a cloud and communication details weren’t abstracted away. And it didn’t have to, it was basically a given to familiarize oneself with enough knowledge up front to be able to navigate about, which also helped filtering out the normies from the real world pestering one’s sanctuary. That gatekeeping attitude doesn’t work anymore though. Once again, the internet has changed; the audience, the content, the majority parties running the show behind the curtain, and the way people communicate with each other online have just changed since “back in the day”. Simple text just won’t do it anymore, people need emojis and memes to express themselves nowadays. While some aspects of this change are of questionable value, others should be appreciated and considered as an achievement. With all the fond memories I have about the golden days of IRC, I very much enjoy the progress we have made since, and the fact how normal and everyday the internet in general has become. Still, none of the modern forms of communication can replace what IRC was, and still is. Sure, the concept of channels also exists in most modern systems, but the large-scale interconnectivity and openness of IRC doesn’t. It’s everyone for themselves more than ever, with commercial entities competing for users in their own, isolated environments. And it makes perfect sense from a professional point of view — you wouldn’t really want to have company-internal communication in a public IRC network. Setting up a private network is of course an option, but if you go that far, you might as well choose Slack or the likes, with all its conveniences and modern feel. But from an open source point of view, it doesn’t sound like a desirable future where every project has its own communication channels in place, separated from all other projects. Any sense of being a community in the bigger picture would simply be lost this way. Well, we will see what Mozilla’s next steps are. The good news is that even if they make the “wrong” decision, it’s unlikely that it will have any lasting effects on IRC itself. But it would be a greatly missed opportunity to create an updated version of IRC that would fit in today’s world. Posted in Featured, Interest, Original Art, SliderTagged cyber warfare, human interaction, internet relay chat, irc, lifestyle, mozilla, remembrance, social network, society
  4. been testing a script from Westor looks very good so far and many added modules. some modules havent been working so ive contacted him to see if hes still doing updates. but its been fun!!
  5. ChainScriptz_Bot


    IntroductionIf you’re just getting started with IRC development, the first thing to look at would be the IRC core specifications RFC1459 and RFC2812. One of our members has also been writing a new core protocol document here, which you may find useful to consult. After that, our specifications page contains the extensions the IRCv3 Working Group has developed. All of the IRCv3 extensions are backwards-compatible with older IRC clients, and older IRC servers. Our roadmap details the specifications we have in the pipeline, and our GitHub repository is where most of our specification work is done. For any other questions, feel free to consult our FAQ page which contains all sorts of info about us and what we do. If you’re interested in talking with us, our discussion channel is #ircv3 on Freenode [webchat]. IRCv3 FeaturesStandardised account login using SASL to speed up registration and authentication. [3.1] [3.2]Providing the account information of other clients for the development of more advanced client features. [1] [2] [3]Optional metadata able to be attached to each message for easier, standardised extension development. [link]Instant away notifications, to let users know when other users go away or come back more quickly. [link]Showing the actual time a message was received, improving history playback from IRC bouncers. [link]Grouping related messages to simplify collapsing and display of those messages to users. [link]More Info : https://www.irccloud.com/
  6. Last night we experienced approximately 12 hours of downtime between around 18:00 and 06:40 UTC, caused by a prolonged period of internet routing issues which our ISP has attributed to a failed line card in one of their routers. This was our longest period of downtime in many years and we’re very sorry for the disruption it caused. Running a large service which interfaces with the venerable IRC protocol poses a different set of challenges to most modern web services: Firstly, we have to manage a large number of outbound IRC connections while ensuring as few disconnections as possible. Secondly, IRC networks expect our users to connect from a consistent set of IP addresses, and lastly, IRCCloud is subject to a high volume of distributed denial of service (DDoS) attacks. These constraints mean that our outbound connection servers, which actually make your outbound IRC connections, have been hosted for years by a specialist DDoS-resistant hosting service provided by a major ISP. This is a costly part of our infrastructure, and it wouldn’t be economical for us to completely duplicate these servers elsewhere to mitigate against rare situations like the one last night. Switching to another ISP - even if we could find one to provide the required servers at short notice - would involve a long process of getting new IP addresses whitelisted by IRC networks. Our current architecture also restricts us to running our outbound connection servers in relatively close proximity to the rest of our infrastructure (which is hosted on Amazon Web Services). Over the last few months we’ve been working on a significant update of our backend software to remove this restriction - in fact, we started rolling this update out yesterday. These improvements will make it easier for us to investigate other approaches for our outbound connection servers in future, and we’ll certainly be discussing network redundancy with our ISP and future providers. If you’re an IRCCloud subscriber, we’re happy to issue you a month’s refund in compensation for this downtime - drop us an email at team@irccloud.com. Tuesday January 22 2019 • posted by james Bouncer: connect with other clientsToday we’re launching one of our most requested features. Paid subscribers can now use 3rd party IRC clients to connect to the IRCCloud service, just as you would with a traditional bouncer. Open the menu for one of your IRC or Slack connections and choose the “Connect with another client…” option for details on how to connect. For IRC connections, you’ll be prompted to generate a unique server password. Backlog replayNote: backlog replay isn’t currently available for Slack connections Bouncer passwords are shown to you in the following format: bnc:xxxxxxxx… If you’d like the bouncer to replay missed messages whenever you reconnect with your client, you’ll need to change this format to include a clientid of your choosing. This is used to identify and track the messages your client has seen to make sure we only replay undelivered messages. The clientid can be anything, but can’t include spaces. Just make sure to use a different id for each client you use. Once you’ve chosen a clientid, rewrite your password in the following format: bnc@clientid:xxxxxxxx… For example, if your generated password was bnc:abcxyz and you chose laptop as a clientid, you’d connect with the following server password: bnc@laptop:abcxyz SecurityA bouncer password grants full access to the associated network connection, so make sure to keep it safe. You can revoke or regenerate a bouncer password at any time, in case you no longer need it or it becomes compromised. This will also disconnect any client currently using that password. Backlog timestampsThe latest versions of most 3rd party clients support the server-time IRCv3 feature, which the bouncer will use to provide the correct timestamp for backlog replay. However, some clients may need a little coaxing https://blog.irccloud.com
  7. Embedding a Kiwi IRC widget into your websiteEmbedding a Kiwi IRC widget on your website can be a great way to bring your community together or host an online event. No more linking to a long kiwirc.com address - you can keep your community and users on your own website while taking advantage of the well tested kiwiirc.com servers and functionality. At the very least you must know where you want your users to connect to. This will be an IRC network and a channel name. If you don't have either of these, feel free to use irc.kiwiirc.com as the network and any channel name of your choosing (letters and numbers only but starting with a # symbol). https://kiwiirc.com/embedding
  8. we're back in 2019 with a maintenance release for the 0.13 cycle, Quassel 0.13.1. Besides a handful of fixes and improvements over the previous release, 0.13.1 fixes a particularly annoying issue with 0.13.0 on Qt4-based systems where backlog messages would not all be fetched. I'd like to thank Janne "justJanne" Koschinski and Shane "digitalcircuit" Synan in particular for finding the cause for this problem, as well as implementing and testing the fix! So if you happen to run Quassel 0.13.0 on a system or distro still using Qt4, be sure to upgrade (or ask your friendly distro maintainers to do so), otherwise your chat history may be spotty... Official 0.13.0 builds for Windows and OSX already use Qt5, so they're not affected. Also any recent distro release should have done the migration already, as Qt5 has been out for quite some time. Quassel 0.13.1 also makes database schema upgrades more robust by making them resumable, and allows to configure the listen addresses for the built-in identd. Please see the ChangeLog for a full list of changes. As always, you can find the sources, as well as precompiled binaries for Windows and OSX on the downloads page. Cheers,
  9. t is with great pleasure that I can now announce that kiwiirc.com and its development is now sponsored by Private Internet Access. Some people may recognise the company as they have been sponsoring and helping out the IRC community for many years, such as the Freenode network. Having already shown their interest in pushing IRC forward and making sure that core IRC projects can stay afloat, it is a well suited match as a sponsor to the Kiwi IRC project as this can benefit every IRC network and community that uses the Kiwi IRC web client. So what does this mean for the project? There are no large changes being made. Kiwiirc.com and the open source project are still independent and run by volunteers. However, with the extra support, this allows me to be focusing on Kiwi IRC development much more closely and building up kiwiirc.com with new features and improvements at a faster pace. It’s not just development that’s involved in this project. Serving kiwiirc.com for an instant, always available web IRC client for any network out there has been the larger bulk of the project and has exploded in recent years, growing from hundreds to millions of users every month. This has been a personal financial drain for some time (handling IRC isn’t cheap!) since I have never wanted to start showing adverts, but we can now easily expand to be supporting the new growth and continue supporting every IRC network out there with a simple, modern IRC client for the web and mobile. What's happening next? There has been a lot of silence with progress in recent months due to the lack of time available towards this project, however with that changing now we can start to pick up the pace of development some more. Some highlights of whats currently happening: An entire re-write has been in the works with a development preview available here Amazing mobile and tablet device support The open source project and related projects has now moved into it’s own organisation, https://github.com/kiwiirc There has been some heavily requested features over time which I can now start putting resources into. I know some of these will be getting people excited so there will be another mention of these once the new release of Kiwi IRC has become generally available. More information on these will appear in the near future so be sure to be following @kiwiirc on twitter or the mailing list to be getting the updates as they happen! Or just come say hey on irc.freenode.net/#kiwiirc :) Finally, a big thanks to the new sponsor, PrivateInternetAccess, for helping not only Kiwi IRC but the IRC community as a whole. If you’re looking around for a VPN provider to keep yourself protected online, take a look at privateinternetaccess.com as they come highly recommended from many different sources and reviews! https://kiwiirc.com/
  10. chain

    Tat\'s Trivia Bot

    Added WPM questions.WPM*HoTMaiLWPM*The quick brown fox jumps over the lazy dogWPM*What a todo to die today at a minute or two to twoWPM*The world beyond the stars is full of stumps.WPM*The night is long and full of terrorsWPM*Winter is comingWhat is the chemical symbol for gold=*AuFixed /ask command. It was wonky and I never realized till I tried to use it to test /ask WPM: This is a test of the trivia bot.The added = formatting indicates that it should use exact mode. Which uses neither fix nor case insensitivity. This is also used for WPM questions Where failing to capitalize the letters results in a fail.Added /openquestions as a secret command that opens the question file. https://www.mediafire.com/?lf27b3zy29idj
  11. Welcome to [ D-BoT Scripting ] 2.0 Hi there, long time no see! After being gone for a long time, [D-BoT] is back as an English bot and now supports the international versions (.com and .dm) next to the .nl version of Omerta. On this website you will find all the basic information about [D-BoT] you need, for example the commands, some handy information about IRC, some basic statistics of the game and information on how to contact us. https://www.d-bot.net
  12. Finally 1.0Smuxi is celebrating its 10th anniversary! 10 years ago, Mirco Bauer made the first commit to the Smuxi source code repository and is still very committed to it. He started the Gnosmirc project in 2005 when the only way a 24/7 "always-on" experience with IRC meant you had to use a console based IRC client like bitchx, irssi or epic combined with screen and SSH. This looks very practical at first and is a powerful Unix-ish way of accomplishing that job, but it has the big downside that it doesn't integrate with a desktop environment like GNOME. A bit later the Gnosmirc project was renamed to Smuxi when the new code architecture allowed other frontend implementations besides the GNOME one. The ncurses/STFL based text frontend was later implemented and is considered stable and useful enough for day to day use, but still has some rough edges. WinForms and WPF frontends also exist but need more work to reach a usable state. At this point Smuxi 1.0 contains all features that we could have imagined and even goes beyond with very advanced features like message patterns or language agnostic scripting.
  13. chain


    Group chat for teams, friends, and communities. IRCCloud is an IRC client with a future. Stay connected, chat from anywhere, and never miss a message. https://www.irccloud.com
  14. >Hi everyone, UnrealIRCd 4.2.2 (stable) is now available for download. It contains several major enhancements, in particular with regards to flood controls. It also fixes a crash issue in the websocket module. Note that this is module is not loaded by default (only via modules.optional.conf or explicitly via a loadmodule "websocket"). Further information on changes can be found in the Release notice @ UnrealICD Release Announcment
  15. The RafaeLLa IRC Bot Services is an multi IRC channel bot, based on modules design, it's easy and is that anyone need for his/her channel, including an setup manager that you can easy setup it with your settings also you change/enable/disable any setting or any module from popups (Right click on Status Window), it has also a lot of modules that parsingwebsites information http://westor.ucoz.com
  16. Was looking around tonight and got on this IRC Client I like it a lot and its great to get ppl to talk on IRC easy setup!! https://kiwiirc.com/nextclient/
  17. IRC (Internet Relay Chat) has been around since 1988, which makes it ancient in Internet terms. And although it’s still used by hundreds of thousands of users around the world, IRC has seen a dramatic downturn in usage. We have talked to the creator of IRC, and others, about why the once so widely used technology has seemingly fallen out of favor with so many users. The origins of IRC We connected with Jarkko Oikarinen, the creator of IRC, who works at Google in Sweden, and he told us the story of how IRC was born. The first IRC Server. Photo courtesy of Wikipedia. Oikarinen says that he created IRC during three to four months in 1988 when he was a summer intern at the University of Oulu in Finland. At the time, Oikarinen was maintaining a local BBS (Bulletin Board System) called OuluBox and the chat system there needed refreshing. While working on the updated chat system he also wanted to allow participants from the Internet who didn’t need to be logged in to OuluBox to participate in chat. Thus, IRC was born. Since then, IRC has served as an invaluable way of communicating for scores of users around the world. For almost whatever you’d like to discuss or get help with, there’s been an IRC network and channel that would serve your interests. But since the arrival of the new century, IRC has dropped in popularity, with users moving to other forms of communication like the web and social media. We took a look at the numbers to see just how bad it is for IRC. IRC has lost 60% of its users since 2003 It’s clear that overall IRC usage, both in terms of users as well as channels, has been in steady decline for many years. In fact, IRC has lost 60% of its users since 2003, a dramatic fall in numbers for any service. Oikarinen attributes the decline in IRC to a trend of commercialization on the Internet. “Companies want to bring users to their walled gardens,” he says, to ”keep the user’s profiles locked there and not make it easy for users to leave the garden and take their data with them.” IRC’s distributed nature does not fit with the walled garden approach, says Oikarinen. So instead of supporting open communication tools like IRC, companies invest money in making their own solutions, he claims. Christian Lederer, also known as “phrozen77,” is the webmaster of IRC-Junkie.org and he’s had his pulse on the IRC community for many years. According to Lederer, the decline in IRC usage has many possible reasons behind it: Lederer lists large and prolonged DDoS attacks in the early 2000s as one main reason behind the decline. The attacks disrupted many IRC networks, including the most popular ones, and crippled the chat experience for users. When the networks were back up again, many users had migrated elsewhere or abandoned IRC completely. Software piracy and the spreading of warez, is another reason Lederer points to. In the early days of IRC, finding such content was a major reason why some users connected to IRC networks. Over the years, users have found new and easier ways of obtaining warez, like P2P, resulting in less of a need for IRC. Social networking also played an important part of users fleeing IRC. With services like Facebook, Twitter, Linkedin, and others, users found it more convenient to communicate through the social network rather than logging in to an IRC channel. Finally, Lederer points to declining costs and increasing availability of cheap and reliable hosting. If someone disagreed with the way a network was run, they could suddenly start his or her own. In doing so, they could potentially take the channel they operated and their users with them, thereby decimating the numbers of the bigger networks even further. So the decline in IRC usage is a complex issue with no straightforward answers. But it’s not all bad news, as we’ll see next. Among top IRC networks, Freenode bucks the trend If we look more closely at the top six IRC networks and chart their development since 2003, it’s clear there are winners and losers. As you can see, QuakeNet, EFnet, and IRCNet have lost a lot of users, while DALnet and Rizon are floundering without moving much up or down. But it’s not all doom and gloom in the world of IRC, however. Freenode.net is not following the typical trend. Rather it seems to be growing by leaps and bounds, up 486% from 2003 to 2012 in terms of users. According to Freenode’s blog, the network passed 80,000 concurrent connections on April 2, 2012. In fact, Freenode has, according to these numbers, just become the number one IRC network in the world, just bypassing QuakeNet. Christel Dahlskjaer, President of Peer-Directed Projects Center(PDPC), the organization that operates Freenode, explains the network’s growth with its focus on free and open source software. “Freenode has indeed grown and continues to grow,” Dahlskjaer explains. “Freenode has never been a ‘traditional’ IRC network though. Our users tend to come to Freenode because they contribute to or use a free and open source (or other peer-directed) project that has a channel or more on the network. Then in turn other projects come to Freenode because there is a lot of overlap when it comes to users and contributors across the various projects.” “In short, Freenode isn’t growing because it is Freenode or because it is IRC. Freenode is growing because of the projects that chose to make Freenode ‘home’ are growing,” Dahlskjaer summarizes. On the question of whether Freenode’s current good fortune is sustainable, Dahlskjaer is direct. “I see no reason to think that growth is likely to stall anytime soon. For the last six years at least, Freenode has been very steady,” she says. Where is IRC headed? It’s clear that IRC is declining in overall usage but growing in certain niche areas. Perhaps that’s where the future of IRC lies. Lederer says that IRC has to innovate to compete with easy-to-use solutions such as Facebook. This, in turn, is driven by a change in mindset of developers of IRC-related software, who have to drive this innovation, client-wise as well as protocol and server-wise. To Oikarinen,“more interoperability” with other systems such as 3D virtual worlds, multimedia, etc. is one “interesting path forward.” Oikarinen is no longer actively involved in the development of IRC, but he says that it’s up to individuals now. “It does not necessarily require a large team to make significant progress. Just one person can make a huge difference,” Oikarinen says. Lederer makes a similar point, saying that some stand-alone clients are already pushing the boundaries of what is possible on IRC. He points to projects like KVIrc, which brought video chat to traditional IRC, as well as Konversation, with which several IRC users can share a virtual whiteboard. Long live IRC Although there’s no reason to think that IRC will disappear anytime soon, there’s also cause for concern about the future of the once so popular technology. Although Freenode can serve as an example of a growing IRC community, that, in and of itself does not mean the future is secure for IRC. We at Pingdom recognize the tremendous value that IRC has brought to users around the world for many years, and hope that IRC will keep being widely used. In fact, we’ve just set up our own IRC server, which we have some exciting plans for. https://royal.pingdom.com/irc-is-dead-long-live-irc/
  18. chain

    EggDrop Install irc

    This will show you how to Install an eddDrop Bot on your irc server
  19. Spiderscript V3 by Chain View File I'm hoping this Is an untouched, compressed version of the original Spiderscript. Submitter Dodge Submitted 09/21/2018 Category Buzzen Archives  
  20. Version 3.0.0


    I'm hoping this Is an untouched, compressed version of the original Spiderscript.
  21. Internet Relay Chat (IRC) has lost 60 percent of its users, going from 1 million in 2003 to about 400,000 today. And IRC channels? In 2003 there were 500,000; now there is half that number. This is due in large part to the advent of the Web, social media, and tools that can do a lot more than plain text can do. IRC Is Not DeadBut is it dead as Royal Pingdom declared last week? I hear about IRC all the time in the geek world. I asked on Twitter and Facebook if people use it and, sure enough, the open-source and developer crowd shot right back that it is still their chat world of choice. Geeks from Chartio, Basho, Canonical, Citrix and active members in OpenStack and Cloudstack all said they use IRC. Canonical’s Alan Pope: But IRC is not all that it used to be, morphing into services such as Campfire. Hello, RobotThen Redmonk Analyst Donnie Berkholz pinged me about Chatbot, a GitHub chat project ruled by Hubot, which the GitHub ops team developed. Campfire is the defacto communications tool for the ops team. Hubot is a bot that sits in the middle, showing the team what has happened instead of telling them. Hubot is open source, written in CoffeeScript on Node.js. It is a standardized way to share scripts between everyone’s robots. At GitHub the team uses Hubot to connect its various tools that the team has written over JSON APIs. It also connects to external APIs. According to the Hubot web page: Chatbot is of particular use considering the way people work. A GitHub DevOps team may have members in Hawaii or Portland all working on the same project. Log into Campfire and a team member can see the new roll outs to the infrastructure. They can check the status of the branch’s last build. They can see how a GitHub app is performing. Chatbot allows for Hubot to become part of the conversation in Campfire. If you do work in a shell or a website, you have to tell people what you have done. In Chatbot, Hubot does that for you. Campfire is effective because it can show images and do things you just can’t do in the plain-text world of IRC. But all of IRC’s roots lie in this modern form of automation. Berkholz said this to me in an email interview: So IRC is not really dead at all. It’s just turning into a robot — like everything else.
  22. The Pro's & Con's https://www.slant.co/topics/1265/~best-irc-clients-for-windows
  23. Internet Relay Chat (IRC) was born in 1988 to help people message each over over the pre-web internet. While many other programs have become more popular since then, such as Whatsapp, Google Allo, and Slack, IRC lives on primarily in developer communities. Now, IRC developers are updating the venerable protocol to revitalize it for the 21st century. IRC, the grandfather of online chat systems, is trying to make a comeback with a new, unified version. The new IRC, IRCv3, includes several new features: Standardized account login using Simple Authentication and Security Layer (SASL). This speeds up user registration and authentication. SASL is a framework for providing authentication and data security services in connection-oriented protocols. As such, it's ideal for IRC.Expanded user account information. On IRC, users can log in using several different clients and via many servers. This function provides additional data so users can be more easily identified and makes it easier to jump from IRC public channel messages to private messages and back again.Optional message metadata. This will make it easier to add tags to messages.Instant away notifications. This enables users to know when other users go away or come back more quickly.Show message received times. Since IRC works over networks of peer-to-peer (P2P) servers it was often difficult to see when someone actually received a message. This will give users message delivery times that are accurate to within a millisecond.Grouping related messages. This introduces a new IRC "batch" client capability. It will make it easier to track message threads across an IRC channel.Many of these features have already been present in some IRC clients. The IRCv3 Working Group is a group of IRC client and server programmers working to enhance, maintain, and perhaps most important of all, standardize the IRC protocol. Even with all these changes, the new IRC looks a lot like the old IRC. No matter what IRC client you us, for example, mIRC, WeeChat, Pidgin, or if you connect to IRC servers via a web gateway, IRC remains a short -- one line -- series of text driven online communities. Doesn't sound practical? Tell Twitter that. It's where they got the idea that 140 characters was enough. Unlike Google Hangouts or Skype, IRC doesn't include video or Voice-over-Internet Protocol (VoIP). It also doesn't automatically delete messages after they've been received like Snapchat. On the other hand, IRC is still very handy. As Adobe pointed out recently with email, just because a technology is old, doesn't mean it's not useful.
  24. chain

    New Tcl Archive

    Greetings Eggheads, As you might have noticed, the egghelp.org Tcl script archive has not been accepting new submissions for the past several years. The egghelp forum still hosts script releases, but the egghelp Tcl script archive has always been the most popular resource to search for Eggdrop Tcl scripts. We are proud to announce that after this slight hiatus, the egghelp archive will be replaced with one that is open for NEW SUBMISSIONS! slennox, the long-standing owner of the site, unfortunately notified us a while ago that he does not have the time to maintain the original egghelp.org anymore. We would like to express our heartfelt appreciation to him for hosting undoubtedly the most important third party Eggdrop resource site for well over a decade. It is certainly a major reason why Eggdrop is still so popular today. Even without recent script additions, egghelp.org still remains the most popular resource for instructions, Tcl scripts and modules, and the most active Eggdrop forum we can find. With that, we also want to thank slennox for his full support in transitioning the resources, the forum and the Tcl archive to a new maintainer, Richard. Richard has been administrating the egghelp.org forum for several months now, and we are very excited to announce that he has finished rewriting the Tcl archive for full use! It is live at tclarchive.org, hosts the old scripts of egghelp.org (thanks to slennox for providing them), and accepts NEW SUBMISSIONS! So head over there, upload your scripts and browse the existing content :) http://www.eggheads.org/
  25. Version v1.0


    ###################################### # #ChainScriptz IRC Admin App Installer. # ###################################### This program installs software useful to IRC Administrators to generate ssl certifate, key and pem files for operators and usersto identify with services and securely oper.
  • Create New...