Just uploaded our new Webpage including some Major Old informations about our history. -daniel Thuesday 30 July 2024
We updated our IRCd-Software to UnrealIRCd and also updated Anope-Services (yay @ who-m3 for the work he put into updating).
The servers now use valid ssl certificates signed by letsencrypt
.
Since we were at it we also updated our webpage, so welcome to your new webpage (yay @ daniel for messing the webpage up).
Blame scarlet for the chosen colors!
drak forbid me to update the Website for Lifetimefor using <pre> with green text on black background on all other websites i made, so this one is for drak only:
/ \ \ / \
| | \ | |
| `. | | :
` | | \| |
\ | / / \\\ --__ \\ :
\ \/ _--~~ ~--__| \ |
\ \_-~ ~-_\ |
\_ \ _.--------.______\| |
\ \______// _ ___ _ (_(__> \ |
\ . C ___) ______ (_(____> | /
/\ | C ____)/ \ (_____> |_/
/ /\| C_____) | (___> / \
| ( _C_____)\______/ // _/ / \
| \ |__ \\_________// (__/ |
| \ \____) `---- --' |
| \_ ___\ /_ _/ |
| / | | \ |
| | / \ \ |
| / / | | \ |
| / / \__/\___/ | |
| / | | | |
| | | | | |
-daniel Friday 26 July 2024 - 22:22:22
Well, its kinda new. We abandoned the old critenircd, as being based on an old version of UltimateIRCD (which myself and daniel put a lot of work into, with contribution from a couple others), because its code is completely obsolete. Abjects now runs on InspIRCd using Anope services 2.05. We will add any features needed to continue being the network you know, but we also have a lot of modern features now, such as SASL, Anope Cpanel web interface, and more. We also created some Server Admin Tools for creating password hashes, and generating oper blocks and link blocks for InspIRCd. Currently it will work for any server admin using that InspIRCd, so its public. We welcome any and all newcomers; channel content is un-moderated and almost completely unrestricted. There are a couple obvious things we wont allow. ~~drak 23 June 2017
It seems a couple people have the wrong impression regarding our AUP where bots or drone connections are concerned. Simply put, our MOTD is to make sure you understand that our right to removal is all-encompassing where bots are concerned, and that no bot connections are protected under any implied right to use our services. Thus, if we deem a a specific bot to be a negative presence, we can and will remove them without any requirement regarding "legality". In order to say that this means we are "harboring" anything, one would have to assume that all bot connections are illegal. This is far from reality. There are a lot of open source IRC bots that people use for various purposes. A couple of the most common are Eggdrops and eMechs. The eMechs even have "networking" capabilities, and they all have the ability to interact with users and perform activities on IRC. Often people use these for advanced channel management, amusement, and even relaying messages between channels they own on different networks. Another common legitimate bot is iroffer, and similar file sharing bots. Again, file sharing is a similar situation. A lot of it is legal, and again some is not. There are provisions available under DMCA establishing a protocol for notifying and removal of copyright infringements. The owner or a legitimate representative thereof can contact us, and we can and will work with them to get the problem solved. So what makes a bot illegal? Pretty much one thing: its hosting. Almost all bots that are 'illegal' are so die to how and where the owner hosts the bot. If the bot is hosted on a "hacked" machine, or on any resource that the bot owner does not have the right to host IRC processes, it becomes illegal. In almost all cases, if a bot is hosted on someone's personal internet connection, or on leased/paid hosting services, the bot itself is legal. In some cases the bot doesnt need to be hosted illegally to be "illegal", and a few examples are: 1. bots using proxies without proxy owner's authorization, or using hacked machines for proxies. 2. bots that are actively searching for vulnerable systems to exploit, aka "scanning". 3. bots that are engaged in activity to attack anyone or anyone's resources, such as DDoS, flooding, etc. Please keep in mind, that IRC "bots" are not hosted on our servers, any files they are "offering" are not hosted on our servers, and the only way we know anything is going on is if we receive a valid abuse contact. Just like almost any services, bots and file sharing both can be legal or illegal, depending on the means, the activity, and the rights to use of the user who is in control of said resource. Abjects network management provides neither bots or file sharing resources. -drak Wednesday 20 August 2014 - 15:15:52
Over the next few days we will be updating the IRCd's on all of our leafs. We apologize for any inconvenience that this may cause and we will try to keep the disturbance to a minimum. -scarlet Tuesday 03 December 2013 - 09:21:04
We are Proud to announce another Milestone. We've reached 15478 concurrent Users on Abjects 2007
Turner stated that in December 2006 and January 2007 individuals who identified themselves as members of the group Anonymous took Turner's website offline, costing him thousands of dollars in bandwidth bills. On January 19, 2007, Turner sued 4chan, eBaum's World, 7chan, Abjects IRC network, and other websites for copyright infringement. On January 22, 2007, he lost his plea for an injunction. In February 2007 4chan responded to the lawsuit. In April 2007, the judge asked the parties to submit information to schedule proceedings. However, Turner failed to respond. Mail from the court to Turner was returned as "Undeliverable". The judge dismissed the case in December 2007. (LINK
, LINK
)
2007
Well first, The Abjects IRC Network is a conglomerate of Criten, FreshIRC, untouchables and others who have moved here, and merged with us over time. We are the same staff and network you have come to know as Criten now, and we will continue to operate under the same ideals and philosophy, and hope to provide you with equal or better service in the coming years. The main reason we changed - the owner of the criten.net domain name has been missing for years, and amid feeble attempts to locate him, has not yet been reached. Now is time for the domain to be renewed, and it is not going to renew. I have been asked again and again why I havent tried to call his cell phone again, etc., but honestly - I dont want to go through this every year. SO.. its time for a change. For quite a long time now, we have been promoting an "alternative" DNS name for Criten, knowing full well we were going to do this - it has been in the works for nearly a year now. We have already notified all the search engines of changes to the DNS, and we will get the remaining few updated as soon as the change-over is complete. The channel and nickname databases from Criten are intact and well, and everything that is registered on Criten will remain registered on Abjects. Along with the changed Netname and DNS move, we will be updating our IRCd software with some changes that have been requested repeatedly, including stronger flood protection, restoration of user idle time in whois, and more. There are good and bad points to this move, but we believe it will work out for the best.
Hopefully, renewed interest in our network from the IRC community
Criten has had a very bad rep, getting rid of this would be a plus
Security in our network name - getting it fixed "this year" would leave us in the same boat next year.
losing the Criten name. People love it, people will miss it but we will move on!
We also plan to offer our registered users email forwarding and/or DNS names under one or more of our domains. This will not be implemented immediately as there are many other things to get done.
So, all in all, we believe this change will be for the best, and everyone will accept our new name for what it is,.. just a name. We are the same staff, network and people who have made criten what it was for the last couple years, so the only change is pure aesthetics. We hope to serve the IRC community with equal or better quality in the years to come and we know most people will be accepting of our change.
Best Regards,
Criten (NOW ABJECTS!) Staff.
15 November 2006
We have a new services module available exclusively to Criten, it allows voicing or half opping based on nick, it will allow the mode to be set on non-registered nicks also. See /msg chanserv help autoxop for more details. This module is only in testing, anything currently set using this mode will be lost when services restarts. Any problems, ideas, comments, bitching, complaints, or flaming should be directed to #development. 09 September 2006
Botserv request module, previously exclusive to Criten, coded by drak is now available for download from our website 27 March 2006
Extensive changes have been made to our IRCd, including channel flood protection (mode +f), anonymous channel mode (+u) and a channel linking mode (+L). 28 February 2006
There have been a few changes to Criten Services lately. Specifically, there have been added new commands to BotServ Service: Syntax: /msg botserv request [#chan] [flag] [nick] [ident] [vhost] [gecos] Parameters: CHANNEL - Initial assigned channel for your bot. FLAG - Specify private or public bot. - 0 = public, 1 = private. - If private is specified you will not be able to assign it to other channels. - Defaults to public. NICK - 16 chars max nick for your bot. - must not be a registered nick IDENT - 11 chars chars max ident for your bot. VHOST - 50 chars chars max vhost for your bot. - must contain at least one '.' - must contain at least 3 characters. GECOS - 35 chars chars max real name for your bot. Example: /msg botserv request 1 #me foo bar lame.net my bot This example would create a bot assigned to #me with foo!bar@lame.net (my bot) which is private, and cannot be assigned to any other channels. Note: Bots not assigned to any channels may be subject to deletion without warning! =~=~=~=~= Syntax: /msg botserv CANCEL [#CHANNEL] Parameters: CHANNEL - Nick of the requested bot to activate. Description: allows a user to remove their request for a channel bot. =~=~=~=~= Syntax: /msg botserv SHOW Description: allows a user to to view the status of their request(s). Many thanks to drak for his hard work :) 03 September 2005
Vhost are now available!! To get a vhost type /msg HostServ REQUEST vHost. vHost of course being replaced with the one you are asking for. Be advised that vhosts are subject to approval. If there is some exciting news or information you would like posted here please submit the information to Venomus. Upon approval it will be added promptly. 14 April 2004
We upgraded our ircds from liquidIRCd, which was running from a bahamut1.4.35 base, to a custom modified version of bahamut1.4.36. 27 January 2004
-------- Welcome ---------------------------------------------------
o Welcome to the Criten IRC Network
o Visit us @ http://www.criten.net/
-------- Network Rules ----------------------------------------------
o No Flooding o No DoS bots o No Clones o No Channel Wars
o No Takeovers o No Spamming o No Annoying o No Child Porn
o Bots are not allowed, but if your "client" doesn't bother us,
we might not bother it.
-------- Notice ----------------------------------------------
Network Operators are NOT allowed to get into channel affairs
unless the channel violates a network rule (listed above).
If you are experiencing treason, or just problem ops,
Please do NOT get the Network Operators involved.
-------- Disclaimer ------------------------------------------------
o Proxy and Drone (version) scans are issued upon connecting.
o If you wish not to be auto scanned please disconnect now!
o This server, its staff and the people hosting it are *NOT*
responsible for the content that passes through this server.
o Use of this server is a *privilege* which may be removed at
any time and for any reason by the friendly network operators.
o Each channel founder is responsible for policing their own channel(s)
by the correct laws and guidelines. Criten accepts no responsibility for
the actions of channel members or their founders.
-------- Contact ---------------------------------------------------
o The official channel of this network is #criten
o Problem? e-mail: abuse@criten.net
End of /MOTD
05 December 2003
Time for everyone to be updated on the current situation of the network. First off, we would like to thank everyone for their patience this past week, specifically, but also throughout the troubles we have had. There have been some major changes made to the network. Primarily, we will be changing the ircd used on the network from bahamut to hybrid. In accordance, we will also be switching to services compatible with the hybrid ircd. The change was made largely due to the fact that we usually cannot accomodate the number of people trying to connect to the network. The hybrid ircd is more efficient with a server's resources and bandwidth. This should allow the capacity per server to increase and should let more people on to the network. The down side, is that new services may mean everyone would have to re-register everything. We are trying our best to save the data from the old services, but everyone should be aware this is a possibility. There have also been some more changes to the administration of the network. All these efforts are to make Criten a better place for everyone. We are looking forward to a new direction and fresh start for the network. Please continue to be patient with us the over the next week or so as we fine-tune and settle into our new ircd and servers and modified administartion. As always, thanks for supporting Criten. 19 January 2003
This evening the network came under heavy attacks that brought down 95% of the network. We are currently investigating the situation however, unfortunately there have been no signs of things letting up. We will keep you updated as we find out more information. You can keep trying to use irc.criten.net as it will be updated as servers become available, although there is no telling what will be available. Also use midori.criten.net and midori2.criten.net these servers are available as I am posting this. On an unrelated note, Criten has had a slight change in administration. If this is of interest to you, you can check the updated staff page to check on a few subtractions made from our staff. 12 January 2003
Happy Birthday to us! Criten is 2 years old today. We would like to thank the users that have been here for two years and our newest users alike for your support of the network. We hope to earn your continued support for years to come. Thanks again and Happy Birthday Criten! 11 November 2002
At 2:48 EDT on September 9, 2002 Criten reached 10,000 concurrent users for the first time ever. This is a monumental milestone in our history. Thanks go out to all our users and staff that made it happen. 09 September 2002 - 02:48 EDT
The Criten IRC Network was established in November of the year 2000. The initial construction of the network was a time-intensive undertaking. Its founding members wished to create a network that would appeal to every user that connected to our network. In the beginning months we strived to establish an infrastructure that would provide the basis for network growth. This included employing working services and fine-tuning our servers for as close to perfection as we can come. In doing this, we were lucky to be able to expand the reaches of our network early. Our international community now boasts servers in Sweden, England, Norway, and Malaysia. We are extremely proud of the diversity our network exhibits and hope the diversity continues to be as strong in the future. Nowadays, the staff at Criten are working with what we've established to constantly try and improve the network in any way possible. We have an extremely dedicated staff who feel the future is bright for the network. We encourage user involvement and support. Please don't hesitate to join us in #criten, we welcome everyone. Thank you for visiting. November 2000