|
|
| was this helpful? |
| yes |
|
63% |
[ 14 ] |
| no |
|
13% |
[ 3 ] |
| I didn't read it all because you were talking about me! |
|
22% |
[ 5 ] |
|
| Total Votes : 22 |
|
| Author |
Message |
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1122
|
 Posted: Aug 24, 2008 9:54am Post subject: |
 |
|
| darkwarrior wrote: | | The one thing with using an ircd and services package that suits the network's needs, especially on a brand new network is a bit difficult to do in the beginning. If it's a brand new network, that would be assuming that the network has no users at the moment, so how are you supposed to collect any input as to what the users want and feel comfortable with? You can't. |
Actually, yes you can. IRC administration is not something any sane person should attempt without any prior experience, yet sadly happens daily. That prior experience is gained from other networks, so you should already have an idea of what software can do what .. even if it's only limited to 1 ircd/services combination.
Secondly, opening your network to the public directly after you installed your first combo is a bad idea. You should experiment with you and perhaps a few firends that would likely become your initial staff. This experimenting will allow you to see what each services package can/can't do long before ever making your network public for users. You will find that you really like ircd1/services1 but don't like ircd2/services2. This step can also prove what each other admin likes as well as how well you work together as a team and make adjustments from there. You may find that you really don't like friend3 as an admin and should shift your staff accordingly. This step will also show you what kind of staff you realisticlly need. Case in point is services1 has auto-routing, so you will need less staff to insure that the servers stay connected, this means a smaller routing team. Additionally, services2 requires oper intervention when registering new channels, this feature may be perfect for your plans/goals but will inherantly require additional Channel Services staff to review and approve all channel registrations. The list goes on and on.
Third, you should have some form of idea as to what features you want to offer as well as what you want your theme to be long before you open to the public as well. Knowing what you and your staff want your network to offer or be will help you choose your ideal software because you can then match features and see what can/canot be done with each.
Remember the 5 P's. Prior Planning Prevents Poor Performance
Please see:
http://en.wikipedia.org/wiki/Comparison_of_IRC_daemons
http://en.wikipedia.org/wiki/Comparison_of_IRC_services
You can go a step further and insure you support as many clients as possible by reviewing http://en.wikipedia.org/wiki/Comparison_of_IRC_clients as well.
Forth, all your "learning" in regards to understanding how what features work a well as proper syntax usage on all commands should be also handled prior to public opening. This ties back into my first point above. This step can literally take weeks or months. Just because you know ircd1 and services1, doesn't mean that they are your best/only solution. If you really care about the success of your new network, you need to do a lot of homework between the time you configure your first combo and the time you open publicly.
As you can see. Opening a new network can be rather time consuming and no easy task, even for expereinced IRC Operators.
| Quote: |
The one problem with a unique feature/service is, due to the large amount of networks and features already in use, its kind of difficult to think of something new that the rest don't have. What advice would you offer to those who are trying to figure out what to add to their service?
|
Due to restrictions and lack of updates to the IRC protocol as a whole, it's rather hard to add new features while remaining compliant, but still possible. "Features" don't have to be IRC based, they can include your website or anything else related to your network.
I recommend thinking as a user, what would you consider useful? Opt-Out abilities for network announcements? the ability to set a "vacation" mode so that your nick deosn't expire when you are away from your favorite network for extended periods? A small website for your channel hosted by the network? webchat options usable on your website to drop web user directly into your channel? A free shell account to run an eggdrop bot from? A hosted botservice?
In short, what would YOU as a user like to see? |
|
| Back to top |
|
 |
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1122
|
|
| Back to top |
|
|
darkwarrior
Lurker
Joined: 02 Aug 2008
Posts: 172
|
| Posted: Aug 24, 2008 3:06pm Post subject: |
|
|
Wow, I never heard about that katslaw.. Then again, I have no business to know about it, as I choose not to use EFnet, so I really don't care what goes on there.. But regardless, I feel bad for that network and my help and/or services and hand will be held out to the admins/opers of efnet if help is required in anything.
Whether or not they deserved it is not the question. It still shouldn't of happened. People really need to grow up and stop this DDoS, and hacking of irc networks over personal issues. It's immature and lame. |
|
| Back to top |
|
|
PingBad
Guru
Joined: 05 Feb 2005
Posts: 2096
Location: New Zealand
|
| Posted: Aug 24, 2008 3:59pm Post subject: |
|
|
Well, katsklaw, certainly an interesting read (both in the article and in the comments departments)
However, iHaq (and the rest of 218) have done themselves no favors with this. They've openly admitted to compromising and accessing a remote machine using a method that they were not authorized to use (in this case, sniffing, probing, et al.) - on top of that, they have installed software (their patched IRCd) that they were (again) not authorized to do.
If my memory serves me well enough, that'll be roughly 5-10 yrs for the ring leader, and perhaps 2-5 for the minions of the 218 crew.
EFNet, I may not chat on your network, but I do feel for you - and hope you send these kids to the brig where they belong. |
|
| Back to top |
|
|
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1122
|
| Posted: Aug 24, 2008 4:14pm Post subject: |
|
|
| darkwarrior wrote: | | Wow, I never heard about that katslaw.. Then again, I have no business to know about it, as I choose not to use EFnet, so I really don't care what goes on there. |
The problem with that way of thinking is that it you will be limiting yourself greatly if you truely believe it.
What happens on any network other than yours can also happen to yours. So this same thing can happen to you and you will better educated if it does if you pay attention to the IRC community as a whole instead of just caring about your own network.
Additionally, it's far better to learn from other peoples mistakes than for you to have to live through the pain of experiencing it first hand before you learn.
So as a network admin, you have all the business in the world to know it. You as the network admin of an irc network represent your network to the irc community, thus you should be involved in the irc community.
Another example is that in the late 90's, DALnet had an experience where an IRCop inadvertantly banned *!*@* and instantly akilled about 70,000 users. DALnet learned from that experience by making it impossible make such a broad ban by adding additional checks in their ircd software. Some other ircd coders picked up on that and changed their code as well. Several years later, UnderNet experienced something very similar, had they payed attention and changed their ircd code as other had, they would have never experienced the issue themselves.
Another example is channel takeovers, DALnet again fixed this as best they could given the current technology and effectively eliminated the ability for someone to "ride a split" to takeover a channel. That was more than a decade ago and to this day, such takeovers occur on other networks.
So yes .. it pays to "care" about other networks than your own. |
|
| Back to top |
|
|
darkwarrior
Lurker
Joined: 02 Aug 2008
Posts: 172
|
| Posted: Aug 24, 2008 5:15pm Post subject: |
|
|
Well, I meant that its none of my business in the sense of why it happened. The fact that it happened definitely is a good reference of possible things that can happen to my network and I do definitely care about that and will definitely be working to make sure my network has necessary methods to prevent something like this.
If someone cares to explain, what exactly was the reason for this to happen, and any advice on preventing something like this in the future (especially for those reading this that have no idea about security, surely there are some) |
|
| Back to top |
|
|
youngblood
Newbie
Joined: 17 Apr 2008
Posts: 66
|
| Posted: Aug 24, 2008 8:10pm Post subject: claps for katsklaw |
|
|
| good job keep up the good work |
|
| Back to top |
|
|
|
|
| |
Register
Log in
