Network Hierarchy and Administration

Darc — Thu, 18 Dec 2008 14:44:38 GMT

Current revision posted to TheZoneIRC Network by Darc on 12/18/2008 6:44:38 AM

Network Hierarchy and Administration

Filed under: servicesadministration, networkhierarchy, administrationnetwork, server, hierarchyservices

Due to some recent confusion, I wanted to make some things clear in a light-hearted (and awesome) way. I want to take some time to outline the structure of administration as it currently stands.

Defense of Network Administration
(Not that it needs to be defended. "Because I said so..." works for us most of the time.)

Let's suppose we live in a world where there is only 1 server, and only a hand full of admin. How do we choose to administrate our IRC experience? Because of the lack of multiple servers and server admin, it makes sense for the operators to maintain total control of the server and services. After all, giving the IRC ops an O:Line in the first place indicates you trust them. And it only affects you, so who cares?

What I want to look at is... why is this different when there are 2+ servers?

Let’s suppose again that you are the Server Administrator. You run Server-1, and, to avoid a giving a feeling of any sort of priority or importance, we'll call the server you are linked with Server-A. You spent some time getting your channels registered and some rules for the usage of nicks or hosts setup... How do you feel about the Server Administrator of Server-A (the other guy) making services changes to the config or rules affecting the registration of channels on your server (or some other thing you cared enough about to set a policy for) without your consent or input? My guess is, you probably don't feel too good about that.

But why? The other guy made those changes on his server. I can hear you screaming, "But it affected me! Just because that person has an IRC server does not mean they should be entitled to powers that affect the servers of other people in that way, unless we establish that is their role." Looking at it this way, I think there's even an argument that could be made against Server Administrators having global (affective on all servers) power at all when O:Lined on a network.

Okay. So who controls the services? Like I stated above, "Unless we establish that is their role." The services controller should be the person we establshedestablished to run them... within the guidelines we set when they started running. You might be thinking "you said we established." Yes I did. You might want to ask, "Who is this 'we' you speak of?" That answer is simple. The people in the room when it was established. You don't think congress gets credit for writing the Constitution. We trust their judgementjudgment, and it works out for us.

Fast forward a few servers.... Now there are 8. Who runs services? The person we agreed would run them.

Somebody said, "Why can't I show up and link and instantly be a member of this governing 'we'?" And the answer is simple.

TheZone IRC Network is a network. You are a server. You can't expect to show up to EFnet and govern over their services. Well, I suppose anyone can in a way since they don't have services, so we'll use DALnet instead, but only because EFnet doesn't have services. My point is... when there is an already existing group of Server Administrators in a network, they have reached an accord about the way the network is to be run. They have submitted the reigns of global network matters to network administration, and try to build their servers in any way they can. When you link, asking them to be okay with a new person able to G:Line on their network bears a lot of questions. Wouldn't you be concerned if you were already present and we linked someone new? Asking them to be okay with a new services governor is a whole other thing. Services Administrations can getpass on certain services, revealing passwords. You can separate that from Services Operators, sure, but the point remains the same -- do you want them to have control over your stuff... or do you just want to trust Network Administration to do it? That's a no brainer.

As a Server Administrator with only one server, you are a network administrator (in a network of one -- kind of like when you're in the army, but went rogue and everyone else thought you were stupid (which you are -- do you know we have airplanes now?)). With a link situation, there has to be someone to make sure the IRCd's are the same (or compatible) versions, make sure any network wide code modifications are made and in place, ensure connectivity is optimized and secured during essential times, as well as regulate network wide guidelines as a means of bringing unity together and ensuring that everyone, users and admin alike, have a fair and enjoyable IRC experience on the network as a whole.

Think about it this way too. When you link to TheZone IRC Network -- you, your attitudes and behavior, your resolve, your thoughts, the way you present yourself -- all that, is a representative of TheZone IRC Network as a whole. If you G:Line someone from the network, and it was the President (and people cared), headlines everywhere read 'The President GLined from TheZone IRC Network." This of course would cause mass confusion as no one would know what a GLine is... and they'd google TheZone IRC Network, (which is awesome, so take advantage if he happens to stop by). If someone hates you, they'll hate us. If they love you, they love us. Why? Because you went from a "you" to a "we." And as part of "we" you can take advantage of the benefits of being a part of us, and all our awesome. But this can work out to your benefit. If someone hates us, you have the opportunity to say "Oh yeah.. no... they've got some hang ups... yeah... no doubt... but people that run my server are a little different and a little more friendly (not to insult anyone's friendliness, or lack thereof, except for ________)." You can distance yourself from us without delinking by simply presenting yourself in a different light if you so choose.

Current Network Administration, and TheZone History Lesson - 101

So, now you may ask... who holds this ever so heavy responsibility, the coveted title "Network Administrator"?! On TheZone IRC Network, there's a reason Syber holds the nickname "God." It was him, dos, and judge that started it up in the first place.

You might be asking "Well, Darc, how did YOU get there?"

A little while back, I was the "God" of a network called IdleWhores IRC Network. At the time of our TheZone merge, we had 5 servers linked. When the merge happened, my Server Administrators and I eventually dropped the network name IdleWhores (which preserved itself only in the form of a channel - #IdleWhores), and there were 4 Network Administrators: Syber, dos, pre, and myself.

(A merge is the terminology used to describe a linking between two individual and totally separate networks (a collection of servers linked together in unity) coming together to form one larger network. A link is the terminology used to describe a linking of one server to another server or a larger network.)

So where are dos and pre?

Well, they pre-tty (haha) much don't have a whole ton of interest in IRC at the moment, so they spend time with their families and play on their Xbox 360s. But I'm sure if either of them wanted to be active Network Administrators tomorrow, they could be. They're good guys, know alot about alot, and started this thing in the beginning. But until such a time that they desire to be IRCool again, Syber and I are the guys that run the show.

In reality, I think Syber has the one up between him and myself. When we merged, we used TheZone's services, we use TheZone's name, we use TheZone's website (registered to Syber), and so on. #TheZone -- is Syber's channel. He owns it. (Well, and dos I think too, technically.) But Syber runs it. So in #TheZone, the buck stops there. On the network, we generally collaborate for ideas and advice, and do what we feel is best. And I don't remember the last time we disagreed, if ever. We seem to have a lot of the same goals and values when it comes to the network. That helps us keep things balanced between who does what. We're both capable developers. We can say "I'll do this, you do that." And break to go do it, and get things done faster.

On a side note, we're also incredibly lazy... so that sucks. But at the moment we're totally in IRC mode, so for the record if there's some idea you have, let us know, because we'll be more likely to do it now than when we feel we're "done."

Will things stay the way they are? Hopefully not. We'd like nothing more than to be FORCED to add to the list of servers, IRC operators, and Network Administrators -- just so long that the reason is that the userbase has grown beyond the servers we already have, and the number of servers has grown to be unmanagable unmanageable by only two Network Administrators.

Instructions for Gaining Network Administration Status - (advanced)

Want to be a Network Administrator? I'd give you this advice:

    1) Learn to Administrate ...a server as thoroughly as Syber and myself, including full shell / IRCd installation and configuration (among other IRC things such as eggdrop, services, etc)...
    2) Earn our Trust - Be logical, friendly, rational, calm, not overly zealous, and most importantly -- USEFUL. Causing drama with us or other admin automatically docks you points. Why? Because we aren't going to promote someone we scrap with. That's asking for punishment.
    3) Get a Server - You can't go from IRC operator or a regular user to Network Administrator. Well, I suppose you could if you wanted to -- somewhere else. Only in a world where our userbase was flourishing and the servers / services became unmanageable for us alone would a RELIABLE and TRUSTWORTHY Server Administrator be considered for esclation escalation to Network Administration -- IF needed.
    4) Build the Network - Get enough users / servers on the network so that we need you. This also shows interest in the network as a whole as apposed to just your server. Unless you show us the love (that you care about the network and the people on it), we aren't going to marry you. Period, no execptionsexceptions. There are already two chiefs... we need some indians Indians (and not the Cleveland Indians... because I'm a Pittsburgh Pirates fan).
    5) Realize that while ability and talen talent is king, Attitude is Queen -- and wears the pants in the monarchy. If you're whining and begging about gaining this status, or being utterly annoying always... you will more than likely be viewed as someone who wants a power trip and is too immature for it, and will likely never see the +N flag on your nick -- at least not on our network. So if you do just want a power trip -- hide it. Because we aren't here to stroke your already-too-large ego. We're stroking our own already, and we only have two hands (one to stroke ego, the other to type IRCawesome commands.) And if you'd like to join in the effort to stroke our egos, that's more than OK. No, it won't get you net-admin brownie points. But once you're around awesome long enough -- it gets on ya! :D

Alternatively, grow a network of your own... a few servers and a decent amount of reliable/regular users/server administrators of your own, and perhaps we'd merge and you'd have it by default. Maybe. No promises though, and don't let the door hit you in the butt on the way out. Building an IRC network (already a mostly dying breed for smaller networks and networks that refuse public warez trading) is a lot of fun I hear.

Cap, Recap, and RebottleRe-bottle

Network Hierarchy, IRCd's:

    Network Administrators
        - Server Administrators
            - IRC Operators
                - Channel Owners
                    - Registered Users
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Network Hierarchy, Services:

    Services Root Administrators (Full Root Access, including to Services Shell)
        - Services Administrators (Full in-IRC access)
            - Services Operators (Partial in-IRC Access)
                - Bender / Calculon / ProxyServ (not real access, I just liked the idea of making you feel like artificial intelligence eggdrop bots have more access than you.)
                    - Registered Users (Public in-IRC Access)
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

On TheZone IRC Network, Network Administrators also serve as Services Administrators. Syber and I alone hold the position of Services Root Administrators. What does that mean? Basically, that we have all power and authority to modify anything, including the source code (if desired) of the services. Is there more than one needed? No, but if one of us gets hit by a bus, there's someone to pick up the slack. Also, there's the concern that California will drop into the pacific at some point, in which time Paul will be swimming a whole lot, and would probably not care much about the network. Unless of course he felt he could recruit some sharks or something to join as users. Then he'd make pitches between breaths and breast strokes. But I also hear that water beings have a little trouble with keeping computers not broke, so I don't think that'd really work out. :( We aren't racist, I promise. But it'd be pretty cool to chat online with a real shark, huh? I suppose if California were to drop off, the services / hub server / web server / DNS server would go bye bye too as it is located in California. Yeah... nevermind... we'd be S.O.L. Oh well... it was worth the try.

In short.... As always, your suggestions, comments, and opinions will be gladly accepted and reviewed.... and then we'll do what we want anyway, naturally claiming any and all great ideas you have as our own, and promptly procrastinating on anything not important while simultaneously putting off all important things until we can't live without doing them anymore. We are NetAdmin. This is our vow. Okay cool.

Disclaimer: The I-don't-care attitude may or may not be the real, actual opinions or thoughts of the administration of TheZone IRC Network. Unless it changes more of your life than your on-the-line online chat habits.... WHO CARES?

Network Hierarchy and Administration

Darc — Thu, 18 Dec 2008 14:38:27 GMT
Revision 6 posted to TheZoneIRC Network by Darc on 12/18/2008 6:38:27 AM

Network Hierarchy and Administration

Filed under: services, network, administration, server, hierarchy

Due to some recent confusion, I wanted to make some things clear in a light-hearted (and awesome) way. I want to take some time to outline the structure of administration as it currently stands.

Defense of Network Administration
(Not that it needs to be defended. "Because I said so..." works for us most of the time.)

Let's suppose we live in a world where there is only 1 server, and only a hand full of admin. How do we choose to administrate our IRC experience? Because of the lack of multiple servers and server admin, it makes sense for the operators to maintain total control of the server and services. After all, giving the IRC ops an O:Line in the first place indicates you trust them. And it only affects you, so who cares?

What I want to look at is... why is this different when there are 2+ servers?

Let’s suppose again that you are the Server Administrator. You run Server-1, and, to avoid a giving a feeling of any sort of priority or importance, we'll call the server you are linked with Server-A. You spent some time getting your channels registered and some rules for the usage of nicks or hosts setup... How do you feel about the Server Administrator of Server-A (the other guy) making services changes to the config or rules affecting the registration of channels on your server (or some other thing you cared enough about to set a policy for) without your consent or input? My guess is, you probably don't feel too good about that.

But why? The other guy made those changes on his server. I can hear you screaming, "But it affected me! Just because that person has an IRC server does not mean they should be entitled to powers that affect the servers of other people in that way, unless we establish that is their role." Looking at it this way, I think there's even an argument that could be made against Server Administrators having global (affective on all servers) power at all when O:Lined on a network.

Okay. So who controls the services? Like I stated above, "Unless we establish that is their role." The services controller should be the person we establshed to run them... within the guidelines we set when they started running. You might be thinking "you said we established." Yes I did. You might want to ask, "Who is this 'we' you speak of?" That answer is simple. The people in the room when it was established. You don't think congress gets credit for writing the Constitution. We trust their judgement, and it works out for us.

Fast forward a few servers.... Now there are 8. Who runs services? The person we agreed would run them.

Somebody said, "Why can't I show up and link and instantly be a member of this governing 'we'?" And the answer is simple.

TheZone IRC Network is a network. You are a server. You can't expect to show up to EFnet and govern over their services. Well, I suppose anyone can in a way since they don't have services, so we'll use DALnet instead, but only because EFnet doesn't have services. My point is... when there is an already existing group of Server Administrators in a network, they have reached an accord about the way the network is to be run. They have submitted the reigns of global network matters to network administration, and try to build their servers in any way they can. When you link, asking them to be okay with a new person able to G:Line on their network bears a lot of questions. Wouldn't you be concerned if you were already present and we linked someone new? Asking them to be okay with a new services governor is a whole other thing. Services Administrations can getpass on certain services, revealing passwords. You can separate that from Services Operators, sure, but the point remains the same -- do you want them to have control over your stuff... or do you just want to trust Network Administration to do it? That's a no brainer.

As a Server Administrator with only one server, you are a network administrator (in a network of one -- kind of like when you're in the army, but went rogue and everyone else thought you were stupid (which you are -- do you know we have airplanes now?)). With a link situation, there has to be someone to make sure the IRCd's are the same (or compatible) versions, make sure any network wide code modifications are made and in place, ensure connectivity is optimized and secured during essential times, as well as regulate network wide guidelines as a means of bringing unity together and ensuring that everyone, users and admin alike, have a fair and enjoyable IRC experience on the network as a whole.

Think about it this way too. When you link to TheZone IRC Network -- you, your attitudes and behavior, your resolve, your thoughts, the way you present yourself -- all that, is a representative of TheZone IRC Network as a whole. If you G:Line someone from the network, and it was the President (and people cared), headlines everywhere read 'The President GLined from TheZone IRC Network." This of course would cause mass confusion as no one would know what a GLine is... and they'd google TheZone IRC Network, (which is awesome, so take advantage of this opportunity of you can)if he happens to stop by). If someone hates you, they'll hate us. If they love you, they love us. But Why? Because you went from a "you" to a "we." And as part of "we" you can take advantage of the reverse is not always truebenefits of being a part of us, and all our awesome. People But this can enjoy work out to your channel on our networkbenefit. If someone hates us, and dislike the rest of you have the network for whatever reason opportunity to say "Oh yeah.. no... theywant've got some hang ups... yeah... no doubt... but people that run my server are a little different and a little more friendly (not to insult anyone's friendliness, or lack thereof, except for ________)." You can distance yourself from us without delinking by simply presenting yourself in a different light if you so choose.

Current Network Administration, and TheZone History Lesson - 101

So, now you may ask... who holds this ever so heavy responsibility, the coveted title "Network Administrator"?! On TheZone IRC Network, there's a reason Syber holds the nickname "God." It was him, dos, and judge that started it up in the first place.

You might be asking "Well, Darc, how did YOU get there?"

A little while back, I was the "God" of a network called IdleWhores IRC Network. At the time of our TheZone merge, we had 5 servers linked. When the merge happened, my Server Administrators and I eventually dropped the network name IdleWhores (which preserved itself only in the form of a channel - #IdleWhores), and there were 4 Network Administrators: Syber, dos, pre, and myself.

(A merge is the terminology used to describe a linking between two individual and totally separate networks (a collection of servers linked together in unity) coming together to form one larger network. A link is the terminology used to describe a linking of one server to another server or a larger network.)

So where are dos and pre?

Well, they pre-tty (haha) much don't have a whole ton of interest in IRC at the moment, so they spend time with their families and play on their Xbox 360s. But I'm sure if either of them wanted to be active Network Administrators tomorrow, they could be. They're good guys, know alot about alot, and started this thing in the beginning. But until such a time that they desire to be IRCool again, Syber and I are the guys that run the show.

In reality, I think Syber has the one up between him and myself. When we merged, we used TheZone's services, we use TheZone's name, we use TheZone's website (registered to Syber), and so on. #TheZone -- is Syber's channel. He owns it. (Well, and dos I think too, technically.) But Syber runs it. So in #TheZone, the buck stops there. On the network, we generally collaborate for ideas and advice, and do what we feel is best. And I don't remember the last time we disagreed, if ever. We seem to have a lot of the same goals and values when it comes to the network. That helps us keep things balanced between who does what. We're both capable developers. We can say "I'll do this, you do that." And break to go do it, and get things done faster.

On a side note, we're also incredibly lazy... so that sucks. But at the moment we're totally in IRC mode, so for the record if there's some idea you have, let us know, because we'll be more likely to do it now than when we feel we're "done."

Will things stay the way they are? Hopefully not. We'd like nothing more than to be FORCED to add to the list of servers, IRC operators, and Network Administrators -- just so long that the reason is that the userbase has grown beyond the servers we already have, and the number of servers has grown to be unmanagable by only two Network Administrators.

Instructions for Gaining Network Administration Status - (advanced)

Want to be a Network Administrator? I'd give you this advice:

    1) Learn to Administrate ...a server as thoroughly as Syber and myself, including full shell / IRCd installation and configuration (among other IRC things such as eggdrop, services, etc)...
    2) Earn our Trust - Be logical, friendly, rational, calm, not overly zealous, and most importantly -- USEFUL. Causing drama with us or other admin automatically docks you points. Why? Because we aren't going to promote someone we scrap with. That's asking for punishment.
    3) Get a Server - You can't go from IRC operator or a regular user to Network Administrator. Well, I suppose you could if you wanted to -- somewhere else. Only in a world where our userbase was flourishing and the servers / services became unmanageable for us alone would a RELIABLE and TRUSTWORTHY Server Administrator be considered for esclation to Network Administration -- IF needed.
    4) Build the Network - Get enough users / servers on the network so that we need you. This also shows interest in the network as a whole as apposed to just your server. Unless you show us the love (that you care about the network and the people on it), we aren't going to marry you. Period, no execptions. There are already two chiefs... we need some indians (and not the Cleveland Indians... because I'm a Pittsburgh Pirates fan).
    5) Realize that while ability and talen is king, Attitude is Queen -- and wears the pants in the monarchy. If you're whining and begging about gaining this status, or being utterly annoying always... you will more than likely be viewed as someone who wants a power trip and is too immature for it, and will likely never see the +N flag on your nick -- at least not on our network. So if you do just want a power trip -- hide it. Because we aren't here to stroke your already-too-large ego. We're stroking our own already, and we only have two hands (one to stroke ego, the other to type IRCawesome commands.) And if you'd like to join in the effort to stroke our egos, that's more than OK. No, it won't get you net-admin brownie points. But once you're around awesome long enough -- it gets on ya! :D

Alternatively, grow a network of your own... a few servers and a decent amount of reliable/regular users/server administrators of your own, and perhaps we'd merge and you'd have it by default. Maybe. No promises though, and don't let the door hit you in the butt on the way out. Building an IRC network (already a mostly dying breed for smaller networks and networks that refuse public warez trading) is a lot of fun I hear.

Cap, Recap, and Rebottle

Network Hierarchy, IRCd's:

    Network Administrators
        - Server Administrators
            - IRC Operators
                - Channel Owners
                    - Registered Users
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Network Hierarchy, Services:

    Services Root Administrators (Full Root Access, including to Services Shell)
        - Services Administrators (Full in-IRC access)
            - Services Operators (Partial in-IRC Access)
                - Bender / Calculon / ProxyServ (not real access, I just liked the idea of making you feel like artificial intelligence eggdrop bots have more access than you.)
                    - Registered Users (Public in-IRC Access)
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

On TheZone IRC Network, Network Administrators also serve as Services Administrators. Syber and I alone hold the position of Services Root Administrators. What does that mean? Basically, that we have all power and authority to modify anything, including the source code (if desired) of the services. Is there more than one needed? No, but if one of us gets hit by a bus, there's someone to pick up the slack. Also, there's the concern that California will drop into the pacific at some point, in which time Paul will be swimming a whole lot, and would probably not care much about the network. Unless of course he felt he could recruit some sharks or something to join as users. Then he'd make pitches between breaths and *** breast strokes. But I also hear that water beings have a little trouble with keeping computers not broke, so I don't think that'd really work out. :( We aren't racist, I promise. But it'd be pretty cool to chat online with a real shark, huh? I suppose if California were to drop off, the services / hub server / web server / DNS server would go bye bye too as it is located in California. Yeah... nevermind... we'd be S.O.L. Oh well... it was worth the try.

In short.... As always, your suggestions, comments, and opinions will be gladly accepted and reviewed.... and then we'll do what we want anyway, naturally claiming any and all great ideas you have as our own, and promptly procrastinating on anything not important while simultaneously putting off all important things until we can't live without doing them anymore. We are NetAdmin. This is our vow. Okay cool.

Disclaimer: The I-don't-care attitude may or may not be the real, actual opinions or thoughts of the administration of TheZone IRC Network. Unless it changes more of your life than your on-the-line online chat habits.... WHO CARES?

Network Hierarchy and Administration

Darc — Fri, 12 Dec 2008 23:29:10 GMT
Revision 5 posted to TheZoneIRC Network by Darc on 12/12/2008 3:29:10 PM

Network Hierarchy and Administration

Filed under: services, network, administration, server, hierarchy

Due to some recent confusion, I wanted to make some things clear in a light-hearted (and awesome) way. I want to take some time to outline the structure of administration as it currently stands.

Defense of Network Administration
(Not that it needs to be defended. "Because I said so..." works for us most of the time.)

Let's suppose we live in a world where there is only 1 server, and only a hand full of admin. How do we choose to administrate our IRC experience? Because of the lack of multiple servers and server admin, it makes sense for the operators to maintain total control of the server and services. After all, giving the IRC ops an O:Line in the first place indicates you trust them. And it only affects you, so who cares?

What I want to look at is... why is this different when there are 2+ servers?

Let’s suppose again that you are the Server Administrator. You run Server-1, and, to avoid a giving a feeling of any sort of priority or importance, we'll call the server you are linked with Server-A. You spent some time getting your channels registered and some rules for the usage of nicks or hosts setup... How do you feel about the Server Administrator of Server-A (the other guy) making services changes to the config or rules affecting the registration of channels on your server (or some other thing you cared enough about to set a policy for) without your consent or input? My guess is, you probably don't feel too good about that.

But why? The other guy made those changes on his server. I can hear you screaming, "But it affected me! Just because that person has an IRC server does not mean they should be entitled to powers that affect the servers of other people in that way, unless we establish that is their role." Looking at it this way, I think there's even an argument that could be made against Server Administrators having global (affective on all servers) power at all when O:Lined on a network.

Okay. So who controls the services? Like I stated above, "Unless we establish that is their role." The services controller should be the person we establshed to run them... within the guidelines we set when they started running. You might be thinking "you said we established." Yes I did. You might want to ask, "Who is this 'we' you speak of?" That answer is simple. The people in the room when it was established. You don't think congress gets credit for writing the Constitution. We trust their judgement, and it works out for us.

Fast forward a few servers.... Now there are 8. Who runs services? The person we agreed would run them.

Somebody said, "Why can't I show up and link and instantly be a member of this governing 'we'?" And the answer is simple.

TheZone IRC Network is a network. You are a server. You can't expect to show up to EFnet and govern over their services. Well, I suppose anyone can in a way since they don't have services, so we'll use DALnet instead, but only because EFnet doesn't have services. My point is... when there is an already existing group of Server Administrators in a network, they have reached an accord about the way the network is to be run. They have submitted the reigns of global network matters to network administration, and try to build their servers in any way they can. When you link, asking them to be okay with a new person able to G:Line on their network bears a lot of questions. Wouldn't you be concerned if you were already present and we linked someone new? Asking them to be okay with a new services governor is a whole other thing. Services Administrations can getpass on certain services, revealing passwords. You can separate that from Services Operators, sure, but the point remains the same -- do you want them to have control over your stuff... or do you just want to trust Network Administration to do it? That's a no brainer.

As a Server Administrator with only one server, you are a network administrator (in a network of one -- kind of like when you're in the army, but went rogue and everyone else thought you were stupid (which you are -- do you know we have airplanes now?)). With a link situation, there has to be someone to make sure the IRCd's are the same (or compatible) versions, make sure any network wide code modifications are made and in place, ensure connectivity is optimized and secured during essential times, as well as regulate network wide guidelines as a means of bringing unity together and ensuring that everyone, users and admin alike, have a fair and enjoyable IRC experience on the network as a whole.

Think about it this way too. When you link to TheZone IRC Network -- you, your attitudes and behavior, your resolve, your thoughts, the way you present yourself -- all that, is a representative of TheZone IRC Network as a whole. If you G:Line someone from the network, and it was the President (and people cared), headlines everywhere read 'The President GLined from TheZone IRC Network." This of course would cause mass confusion as no one would know what a GLine is... and they'd google TheZone IRC Network, (which is awesome, so take advantage of this opportunity of you can). If someone hates you, they'll hate us. If they love you, they love us. But the reverse is not always true. People can enjoy your channel on our network, and dislike the rest of the network for whatever reason they want.

Current Network Administration, and TheZone History Lesson - 101

So, now you may ask... who holds this ever so heavy responsibility, the coveted title "Network Administrator"?! On TheZone IRC Network, there's a reason Syber holds the nickname "God." It was him, dos, and judge that started it up in the first place.

You might be asking "Well, Darc, how did YOU get there?"

A little while back, I was the "God" of a network called IdleWhores IRC Network. At the time of our TheZone merge, we had 5 servers linked. When the merge happened, my Server Administrators and I eventually dropped the network name IdleWhores (which preserved itself only in the form of a channel - #IdleWhores), and there were 4 Network Administrators: Syber, dos, pre, and myself.

(A merge is the terminology used to describe a linking between two individual and totally separate networks (a collection of servers linked together in unity) coming together to form one larger network. A link is the terminology used to describe a linking of one server to another server or a larger network.)

So where are dos and pre?

Well, they pre-tty (haha) much don't have a whole ton of interest in IRC at the moment, so they spend time with their families and play on their Xbox 360s. But I'm sure if either of them wanted to be active Network Administrators tomorrow, they could be. They're good guys, know alot about alot, and started this thing in the beginning. But until such a time that they desire to be IRCool again, Syber and I are the guys that run the show.

In reality, I think Syber has the one up between him and myself. When we merged, we used TheZone's services, we use TheZone's name, we use TheZone's website (registered to Syber), and so on. #TheZone -- is Syber's channel. He owns it. (Well, and dos I think too, technically.) But Syber runs it. So in #TheZone, the buck stops there. On the network, we generally collaborate for ideas and advice, and do what we feel is best. And I don't remember the last time we disagreed, if ever. We seem to have a lot of the same goals and values when it comes to the network. That helps us keep things balanced between who does what. We're both capable developers. We can say "I'll do this, you do that." And break to go do it, and get things done faster.

On a side note, we're also incredibly lazy... so that sucks. But at the moment we're totally in IRC mode, so for the record if there's some idea you have, let us know, because we'll be more likely to do it now than when we feel we're "done."

Will things stay the way they are? Hopefully not. We'd like nothing more than to be FORCED to add to the list of servers, IRC operators, and Network Administrators -- just so long that the reason is that the userbase has grown beyond the servers we already have, and the number of servers has grown to be unmanagable by only two Network Administrators.

Instructions for Gaining Network Administration Status - (advanced)

Want to be a Network Administrator? I'd give you this advice:

    1) Learn to Administrate ...a server as thoroughly as Syber and myself, including full shell / IRCd installation and configuration (among other IRC things such as eggdrop, services, etc)...
    2) Earn our Trust - Be logical, friendly, rational, calm, not overly zealous, and most importantly -- USEFUL. Causing drama with us or other admin automatically docks you points. Why? Because we aren't going to promote someone we scrap with. That's asking for punishment.
    3) Get a Server - You can't go from IRC operator or a regular user to Network Administrator. Well, I suppose you could if you wanted to -- somewhere else. Only in a world where our userbase was flourishing and the servers / services became unmanageable for us alone would a RELIABLE and TRUSTWORTHY Server Administrator be considered for esclation to Network Administration -- IF needed.
    4) Build the Network - Get enough users / servers on the network so that we need you. This also shows interest in the network as a whole as apposed to just your server. Unless you show us the love (that you care about the network and the people on it), we aren't going to marry you. Period, no execptions. There are already two chiefs... we need some indians (and not the Cleveland Indians... because I'm a Pittsburgh Pirates fan).
    5) Realize that while ability and talen is king, Attitude is Queen -- and wears the pants in the monarchy. If you're whining and begging about gaining this status, or being utterly annoying always... you will more than likely be viewed as someone who wants a power trip and is too immature for it, and will likely never see the +N flag on your nick -- at least not on our network. So if you do just want a power trip -- hide it. Because we aren't here to stroke your already-too-large ego. We're stroking our own already, and we only have two hands (one to stroke ego, the other to type IRCawesome commands.) And if you'd like to join in the effort to stroke our egos, that's more than OK. No, it won't get you net-admin brownie points. But once you're around awesome long enough -- it gets on ya! :D

Alternatively, grow a network of your own... a few servers and a decent amount of reliable/regular users/server administrators of your own, and perhaps we'd merge and you'd have it by default. Maybe. No promises though, and don't let the door hit you in the butt on the way out. Building an IRC network (already a mostly dying breed for smaller networks and networks that refuse public warez trading) is a lot of fun I hear.

Cap, Recap, and Rebottle

Network Hierarchy, IRCd's:

    Network Administrators
        - Server Administrators
            - IRC Operators
                - Channel Owners
                    - Registered Users
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Network Hierarchy, Services:

    Services Root Administrators (Full Root Access, including to Services Shell)
        - Services Administrators (Full in-IRC access)
            - Services Operators (Partial in-IRC Access)
                - Bender / Calculon / ProxyServ (not real access, I just liked the idea of making you feel like artificial intelligence eggdrop bots have more access than you.)
                    - Registered Users (Public in-IRC Access)
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

On TheZone IRC Network, Network Administrators also serve as Services Administrators. Syber and I alone hold the position of Services Root Administrators. What does that mean? Basically, that we have all power and authority to modify anything, including the source code (if desired) of the services. Is there more than one needed? No, but if one of us gets hit by a bus, there's someone to pick up the slack. Also, there's the concern that California will drop into the pacific at some point, in which time Paul will be swimming a whole lot, and would probably not care much about the network. Unless of course he felt he could recruit some sharks or something to join as users. Then he'd make pitches between breaths and *** strokes. But I also hear that water beings have a little trouble with keeping computers not broke, so I don't think that'd really work out. :( We aren't racist, I promise. But it'd be pretty cool to chat online with a real shark, huh? I suppose if California were to drop off, the services / hub server / web server / DNS server would go bye bye too as it is located in California. Yeah... nevermind... we'd be S.O.L. Oh well... it was worth the try.

In short.... As always, your suggestions, comments, and opinions will be gladly accepted and reviewed.... and then we'll do what we want anyway, naturally claiming any and all great ideas you have as our own, and promptly procrastinating on anything not important while simultaneously putting off all important things until we can't live without doing them anymore. We are NetAdmin. This is our vow. Okay cool.

Disclaimer: The I-don't-care attitude may or may not be the real, actual opinions or thoughts of the administration of TheZone IRC Network. Unless it changes more of your life than you your on-the-line online chat habits.... WHO CARES?

Network Hierarchy and Administration

Darc — Fri, 12 Dec 2008 20:32:27 GMT
Revision 4 posted to TheZoneIRC Network by Darc on 12/12/2008 12:32:27 PM

Network Hierarchy and Administration

Filed under: services, network, administrationservices , server, hierarchy

Due to some recent confusion, I wanted to make some things clear in a light-hearted (and awesome) way. I want to take some time to outline the structure of administration as it currently stands.

Defense of Network Administration
(Not that it needs to be defended. "Because I said so..." works for us most of the time.)

Let's suppose we live in a world where there is only 1 server, and only a hand full of admin. How do we choose to administrate our IRC experience? Because of the lack of multiple servers and server admin, it makes sense for the operators to maintain total control of the server and services. After all, giving the IRC ops an O:Line in the first place indicates you trust them. And it only affects you, so who cares?

What I want to look at is... why is this different when there are 2+ servers?

Let’s suppose again that you are the Server Administrator. You run Server-1, and, to avoid a giving a feeling of any sort of priority or importance, we'll call the server you are linked with Server-A. You spent some time getting your channels registered and some rules for the usage of nicks or hosts setup... How do you feel about the Server Administrator of Server-A (the other guy) making services changes to the config or rules affecting the registration of channels on your server (or some other thing you cared enough about to set a policy for) without your consent or input? My guess is, you probably don't feel too good about that.

But why? The other guy made those changes on his server. I can hear you screaming, "But it affected me! Just because that person has an IRC server does not mean they should be entitled to powers that affect the servers of other people in that way, unless we establish that is their role." Looking at it this way, I think there's even an argument that could be made against Server Administrators having global (affective on all servers) power at all when O:Lined on a network.

Okay. So who controls the services? Like I stated above, "Unless we establish that is their role." The services controller should be the person we establshed to run them... within the guidelines we set when they started running. You might be thinking "you said we established." Yes I did. You might want to ask, "Who is this 'we' you speak of?" That answer is simple. The people in the room when it was established. You don't think congress gets credit for writing the Constitution. We trust their judgement, and it works out for us.

Fast forward a few servers.... Now there are 8. Who runs services? The person we agreed would run them.

Somebody said, "Why can't I show up and link and instantly be a member of this governing 'we'?" And the answer is simple.

TheZone IRC Network is a network. You are a server. You can't expect to show up to EFnet and govern over their services. Well, I suppose anyone can in a way since they don't have services, so we'll use DALnet instead, but only because EFnet doesn't have services. My point is... when there is an already existing group of Server Administrators in a network, they have reached an accord about the way the network is to be run. They have submitted the reigns of global network matters to network administration, and try to build their servers in any way they can. When you link, asking them to be okay with a new person able to G:Line on their network bears a lot of questions. Wouldn't you be concerned if you were already present and we linked someone new? Asking them to be okay with a new services governor is a whole other thing. Services Administrations can getpass on certain services, revealing passwords. You can separate that from Services Operators, sure, but the point remains the same -- do you want them to have control over your stuff... or do you just want to trust Network Administration to do it? That's a no brainer.

As a Server Administrator with only one server, you are a network administrator (in a network of one -- kind of like when you're in the army, but went rogue and everyone else thought you were stupid (which you are -- do you know we have airplanes now?)). With a link situation, there has to be someone to make sure the IRCd's are the same (or compatible) versions, make sure any network wide code modifications are made and in place, ensure connectivity is optimized and secured during essential times, as well as regulate network wide guidelines as a means of bringing unity together and ensuring that everyone, users and admin alike, have a fair and enjoyable IRC experience on the network as a whole.

Think about it this way too. When you link to TheZone IRC Network -- you, your attitudes and behavior, your resolve, your thoughts, the way you present yourself -- all that, is a representative of TheZone IRC Network as a whole. If you G:Line someone from the network, and it was the President (and people cared), headlines everywhere read 'The President GLined from TheZone IRC Network." This of course would cause mass confusion as no one would know what a GLine is... and they'd google TheZone IRC Network, (which is awesome, so take advantage of this opportunity of you can). If someone hates you, they'll hate us. If they love you, they love us. But the reverse is not always true. People can enjoy your channel on our network, and dislike the rest of the network for whatever reason they want.

Current Network Administration, and TheZone History Lesson - 101

So, now you may ask... who holds this ever so heavy responsibility, the coveted title "Network Administrator"?! On TheZone IRC Network, there's a reason Syber holds the nickname "God." It was him, dos, and judge that started it up in the first place.

You might be asking "Well, Darc, how did YOU get there?"

A little while back, I was the "God" of a network called IdleWhores IRC Network. At the time of our TheZone merge, we had 5 servers linked. When the merge happened, my Server Administrators and I eventually dropped the network name IdleWhores (which preserved itself only in the form of a channel - #IdleWhores), and there were 4 Network Administrators: Syber, dos, pre, and myself.

(A merge is the terminology used to describe a linking between two individual and totally separate networks (a collection of servers linked together in unity) coming together to form one larger network. A link is the terminology used to describe a linking of one server to another server or a larger network.)

So where are dos and pre?

Well, they pre-tty (haha) much don't have a whole ton of interest in IRC at the moment, so they spend time with their families and play on their Xbox 360s. But I'm sure if either of them wanted to be active Network Administrators tomorrow, they could be. They're good guys, know alot about alot, and started this thing in the beginning. But until such a time that they desire to be IRCool again, Syber and I are the guys that run the show.

In reality, I think Syber has the one up between him and myself. When we merged, we used TheZone's services, we use TheZone's name, we use TheZone's website (registered to Syber), and so on. #TheZone -- is Syber's channel. He owns it. (Well, and dos I think too, technically.) But Syber runs it. So in #TheZone, the buck stops there. On the network, we generally collaborate for ideas and advice, and do what we feel is best. And I don't remember the last time we disagreed, if ever. We seem to have a lot of the same goals and values when it comes to the network. That helps us keep things balanced between who does what. We're both capable developers. We can say "I'll do this, you do that." And break to go do it, and get things done faster.

On a side note, we're also incredibly lazy... so that sucks. But at the moment we're totally in IRC mode, so for the record if there's some idea you have, let us know, because we'll be more likely to do it now than when we feel we're "done."

Will things stay the way they are? Hopefully not. We'd like nothing more than to be FORCED to add to the list of servers, IRC operators, and Network Administrators -- just so long that the reason is that the userbase has grown beyond the servers we already have, and the number of servers has grown to be unmanagable by only two Network Administrators.

Instructions for Gaining Network Administration Status - (advanced)

Want to be a Network Administrator? I'd give you this advice:

    1) Learn to Administrate ...a server as thoroughly as Syber and myself, including full shell / IRCd installation and configuration (among other IRC things such as eggdrop, services, etc)...
    2) Earn our Trust - Be logical, friendly, rational, calm, not overly zealous, and most importantly -- USEFUL. Causing drama with us or other admin automatically docks you points. Why? Because we aren't going to promote someone we scrap with. That's asking for punishment.
    3) Get a Server - You can't go from IRC operator or a regular user to Network Administrator. Well, I suppose you could if you wanted to -- somewhere else. Only in a world where our userbase was flourishing and the servers / services became unmanageable for us alone would a RELIABLE and TRUSTWORTHY Server Administrator be considered for esclation to Network Administration -- IF needed.
    4) Build the Network - Get enough users / servers on the network so that we need you. This also shows interest in the network as a whole as apposed to just your server. Unless you show us the love (that you care about the network and the people on it), we aren't going to marry you. Period, no execptions. There are already two chiefs... we need some indians (and not the Cleveland Indians... because I'm a Pittsburgh Pirates fan).
    5) Realize that while ability and talen is king, Attitude is Queen -- and wears the pants in the monarchy. If you're whining and begging about gaining this status, or being utterly annoying always... you will more than likely be viewed as someone who wants a power trip and is too immature for it, and will likely never see the +N flag on your nick -- at least not on our network. So if you do just want a power trip -- hide it. Because we aren't here to stroke your already-too-large ego. We're stroking our own already, and we only have two hands (one to stroke ego, the other to type IRCawesome commands.) And if you'd like to join in the effort to stroke our egos, that's more than OK. No, it won't get you net-admin brownie points. But once you're around awesome long enough -- it gets on ya! :D

Alternatively, grow a network of your own... a few servers and a decent amount of reliable/regular users/server administrators of your own, and perhaps we'd merge and you'd have it by default. Maybe. No promises though, and don't let the door hit you in the butt on the way out. Building an IRC network (already a mostly dying breed for smaller networks and networks that refuse public warez trading) is a lot of fun I hear.

Cap, Recap, and Rebottle

Network Hierarchy, IRCd's:

    Network Administrators
        - Server Administrators
            - IRC Operators
                - Channel Owners
                    - Registered Users
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Network Hierarchy, Services:

    Services Root Administrators (Full Root Access, including to Services Shell)
        - Services Administrators (Full in-IRC access)
            - Services Operators (Partial in-IRC Access)
                - Bender / Calculon / ProxyServ (not real access, I just liked the idea of making you feel like artificial intelligence eggdrop bots have more access than you.)
                    - Registered Users (Public in-IRC Access)
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

On TheZone IRC Network, Network Administrators also serve as Services Administrators. Syber and I alone hold the position of Services Root Administrators. What does that mean? Basically, that we have all power and authority to modify anything, including the source code (if desired) of the services. Is there more than one needed? No, but if one of us gets hit by a bus, there's someone to pick up the slack. Also, there's the concern that California will drop into the pacific at some point, in which time Paul will be swimming a whole lot, and would probably not care much about the network. Unless of course he felt he could recruit some sharks or something to join as users. Then he'd make pitches between breaths and *** strokes. But I also hear that water beings have a little trouble with keeping computers not broke, so I don't think that'd really work out. :( We aren't racist, I promise. But it'd be pretty cool to chat online with a real shark, huh? I suppose if California were to drop off, the services / hub server / web server / DNS server would go bye bye too as it is located in California. Yeah... nevermind... we'd be S.O.L. Oh well... it was worth the try.

In short.... As always, your suggestions, comments, and opinions will be gladly accepted and reviewed.... and then we'll do what we want anyway, naturally claiming any and all great ideas you have as our own, and promptly procrastinating on anything not important while simultaneously putting off all important things until we can't live without doing them anymore. We are NetAdmin. This is our vow. Okay cool.

Disclaimer: The I-don't-care attitude may or may not be the real, actual opinions or thoughts of the administration of TheZone IRC Network. Unless it changes more of your life than you on-the-line online chat habits.... WHO CARES?

Network Hierarchy and Administration

Darc — Fri, 12 Dec 2008 20:32:27 GMT
Revision 3 posted to TheZoneIRC Network by Darc on 12/12/2008 12:32:27 PM

Network Hierarchy and Administration

Filed under: services, network administration , services server hierarchy

Defense of Network Administration (Not that it needs to be defended. "Because I said so..." works for us most of the time.)
Due to some recent confusion, I wanted to clear make some things up a bit (clear in a light-hearted (and awesomeway)) way. I want to take some time to outline the structure of administration as it currently stands. To clarify, I'm not at all saying

Defense of Network Administration
(Not that it will needs to be in this fashion foreverdefended. "Because I 'd be the first person to sign the page to add more administrators IF the user base / number of servers required itsaid so... And I" works for us most of the time.)

Let'm s suppose we live in the front of whatever methods you want to try to get us there.

In a world where there is only 1 server, and only a hand full of admin. How do we choose to administrate our IRC experience? Because of the lack of multiple servers and server admin, it makes sense for the operators to maintain total control of the server and services. After all, at giving the discretion of IRC ops an O:Line in the server administratorsfirst place indicates you trust them. Why? Because any services action And it only affects the entire server as a wholeyou, so who cares?

What I want to look at is... Why why is this different when there are 2 2+ servers?

Well let

Let’s suppose YOU again that you are the Server Administrator. You run server 1Server-1, and, to avoid people thinking the servers are listed in order a giving a feeling of any sort of priority or importance, we'll call the server you are linked with server AServer-A. You spent some time getting your channels registered and some rules for the usage of nicks or hosts setup... How do you feel about the Server Administrator of Server-A (the other guy) making services changes to the config or rules affecting the registration of channels on your server , (or some other thing you cared enough about to set a policy for) without your consent or concerninput? You My guess is, you probably don't feel too good about that. Why

But why? The other guy made those changes on his server. I can hear you screaming, "But it affected me! Just because that person has an IRC server does not mean they should be entitled to powers that affect the servers of other people in that way, unless we establish that is their role. There" Looking at it this way, I think there's even an argument that could be made against server administrators Server Administrators having global (affective on all servers) power at all when O:Lined on a network.

Well OK

Okay. So who controls the services? Well, Like I submit to you: stated above, "Unless we establish that is their role." The services controller should be the person we agreed would establshed to run them... within the guidelines we set when they started running. You might be askingthinking "you said we established." Yes I did. You might want to ask, "Who is this 'we' you speak of?" That answer is simple. The people that were there in the room when they started runningit was established. You don't think congress gets credit for writing the Constitution. We trust their judgement, and it works out for us.

Fast forward a few servers.... Now there are 8. Who runs services? The person we agreed would run them.

You may now be asking

Somebody said, "why "Why can't I show up and link and instantly be a member of this governing 'we' member?" And the answer is simple.

We are

TheZone IRC Network is a network. You are a server. You can't expect to show up to EFnet and govern over their services. Okay Well, I suppose anyone can in a way since they don't have services, so we'll use DALnet instead, but only because EFnet doesn't have services. My point is... when there is an already existing group of Server Administrators in a network, they have reached an accord about the way the network is to be run. They have submitted the reigns of global network matters to network administration, and try to build their servers in any way they can. When you link, asking them being to be okay with a new person able to GLine G:Line on their network is one thing...bears a lot of questions.asking Wouldn't you be concerned if you were already present and we linked someone new? Asking them to be okay with a new services governor is a whole other thing.

Also.. Services Administrations can getpass on certain services, revealing passwords. You can separate that from Services Operators, sure, but the point remains the same -- do you want them to have the issue of non-services network control over your stuff... or do you just want to trust Network Administration to do it? That's a no brainer.

As a Server Administrator with only one server, you are a network administrator (in a network of one -- kind of like when you're in the army, but went rogue)rogue and everyone else thought you were stupid (which you are -- do you know we have airplanes now?)). With a link situation, there has to be someone to make sure the IRCd's are the same (or compatible) versions, make sure any network wide code modifications are made and in place, ensure connectivity is optimized and secured during essential times, as well as regulate network wide guidelines as a means of bringing unity together into and ensuring that everyone's , users and admin alike, have a fair and enjoyable IRC experience on the network as a whole.

Think about it this way too. When you link to TheZone IRC Network -- you, your attitudes and behavior, your resolve, your thoughts, the way you present yourself -- all thatparticular , is a representative of TheZone IRC Network as a whole. If you G:Line someone from the network, and it was the President (and people cared), headlines everywhere read 'The President GLined from TheZone IRC Network." This of course would cause mass confusion as no one would know what a GLine is... and they'd google TheZone IRC Network, (which is awesome, so take advantage of this opportunity of you can). If someone hates you, they'll hate us. If they love you, they love us. But the reverse is not always true. People can enjoy your channel on our network, and dislike the rest of the network for whatever reason they want.

Current Network Administration, and TheZone History Lesson - 101

So, now you may ask... who holds this ever so heavy responsibility?! The answer is simple... it's as clear as a bell... we all have real lives and need someone to tell.... ooooh... crap. Right. I was being poetic again. Sorry.responsibility, the coveted title "Network Administrator"?! On TheZone IRC Network, there's a reason Syber holds the nickname "God." It was him, dos, and judge that started it up in the first place.

Well

You might be asking "Well, Darc, how did I (Darc) YOU get herethere?"

A little while back, I was the "God" of a network called IdleWhores IRC Network(. At the time of our TheZone merge, we had 5 servers at link time with TheZone)linked. When we linked togetherthe merge happened, my server admins Server Administrators and I eventually dropped the network name IdleWhores , (which relinquished its network status to that preserved itself only in the form of a channel (#IdleWhores), - #IdleWhores), and there were 4 Network Administrators, myself, : Syber, dos, and pre, and myself. This

(A merge is what we refer the terminology used to as describe a merge -- linking between two individual and totally separate networks (a collection of servers linked together in unity) coming together to form one bigger larger network. (Please note that when a single server is added to our network, we refer to that as a A link, since the Server is a different level than a network (a collection of servers), as apposed the terminology used to describe a network linking with of one server to another network, which I suppose would be server or a merge.larger network.)

So where are dos and pre?

Well, they pre-tty (haha) much don't have a whole ton of interest in IRC at the moment, but so they spend time with their families and play on their Xbox 360s. But I'm sure if either of them wanted to be active Network Administrators tomorrow, they could be..be.as they They're good guyswho , know alot about alot, and started this thing in the beginning..beginning.but But until such a time that they desire to be IRCool again, Syber and I are the guys...guys that run the show.and really

In reality, I think Syber has the one up between him and myselfas when . When we merged, we used TheZone's services, we use TheZone's name, we use TheZone's website (registered to one Syber), and so on. #TheZone -- is Syber's channel. He owns it. (Well, and dos I think too, technically.) He But Syber runs it. The So in #TheZone, the buck stops there. On the network, we generally collaborate for ideas and advice, and do what we feel is best. And I don't remember the last time we disagreed, if ever. We seem to have a lot of the same goals and values when it comes to the network. That helps us keep things balanced between who does what. We're both capable developers. We can say "I'll do this, you do that." And break to go do it, and get things done faster.

On a side note, we're also incredibly lazy... so that sucks. But at the moment we're totally in IRC mode, so for the record if there's some idea you have, let us know, because we'll be more likely to do it now than when we feel we're "done."

Will things stay the way they are? Hopefully not. We'd like nothing more than to be FORCED to add to the list of servers, IRC operators, and network administrators, Network Administrators -- just so long that the driving force reason is an unmanageable-by-what-we-have-now (that the userbase has grown beyond the servers we already have, and growing) user basethe number of servers has grown to be unmanagable by only two Network Administrators.

Instructions for Gaining Network Administration Status - (advanced)

Want to be a network administratorNetwork Administrator? I'd give you this advice:

    1) Learn how to administrate a Administrate ...a server as thoroughly as Syber and myself, including full shell / IRCd config / good linux knowledge, installation and configuration (among other IRC things (eggdrop, such as eggdrop, services, etc)...
    2) Earn our trust (by being Trust - Be logical, friendly, rational, and calm(, not overly zealous, and most importantly -- USEFUL. Causing drama with us))us or other admin automatically docks you points. Why? Because we aren't going to promote someone we scrap with. That's asking for punishment.
    3) Get a Server. - You can't go from IRC op / operator or a regular user to Network Administrator. Well, I suppose you could if you wanted to -- somewhere else. Only in a world where our userbase was flourishing and the servers / services became unmanageable for us alone would a RELIABLE and TRUSTWORTHY Server Administrator be considered for esclation to Network Administration -- IF needed.
    4) Build the Network - Get enough users / servers on the network so that we need you. Otherwise.. This also shows interest in the network as a whole as apposed to just your server.forget Unless you show us the love (that you care about itthe network and the people on it), we aren't going to marry you. Period, no execptions. There are already two chiefs... we need some Indiansindians (and not the Cleveland Indians... because I'm a Pittsburgh Pirates fan).
    5) Realize that if while ability and talen is king, Attitude is Queen -- and wears the pants in the monarchy. If you're whining and begging about gaining this status, or being utterly annoying always... you will more than likely be viewed as someone who wants a power trip and is too immature for it, and will likely never see the +N flag on your nick -- at least not on our network. So if you do just want a power trip -- hide it. Because we aren't here to stroke your already-too-large ego. We're here stroking our own already, and we only have two hands (one to stroke our already-too-large egos.ego, the other to type IRCawesome commands.) And if you'd like to join is in that the effort to stroke our egos, that's more than OK. No, it won't get you net-admin brownie points. But once you're around awesome long enough -- it gets on ya! :D

Alternatively, grow a network of your own... a few servers and a decent amount of reliable/regular users/server administrators of your own, and perhaps we'd merge and you'd have it by default. Maybe. No promises though, and don't let the door hit you in the butt on the way out. Building an IRC network (already a mostly dying breed for smaller networks and networks that refuse public warez trading) is a lot of fun I hear.

Cap, recapRecap, and rebottleRebottle

Network Hierarchy, IRCd's:

    Network Administrators
        - Server Administrators
            - IRC Operators
                - Channel Owners
                    - Registered Users
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Network Hierarchy, Services:

    Services Root Administrators (Full Root Access, including to Services Shell)
        - Services Administrators (Full in-IRC access)
            - Services Operators (Partial in-IRC Access)
                - Bender / Calculon / ProxyServ (not real access, I just liked the idea of making you feel like artificial intelligence eggdrop bots have more access than you.)
                    - Registered Users (Public in-IRC Access)
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Syber and I

On TheZone IRC Network, Network Administrators also serve as Services Administrators. Syber and I alone hold the position of Services Root Administrators. What does that mean? Basically, that we have all power and authority to modify anything, including the source code (if desired) of the services. Is there more than one needed? No, but if one of us gets hit by a bus, there's someone to pick up the slack. Also, there's the concern that California will drop into the pacific at some pointin time, but as the services / hub server / web server / DNS server is located in California, I'd say we're S.O.L. if that happens anyway. Plus which time Paul will be swimming for a whilewhole lot, and would probably not care a whole lot much about the networkat the time. Unless of course he felt he could recruit some sharks or something to join as users. Then he'd make pitches between breaths and *** strokes. But I also hear that water beings have a little trouble with keeping computers not broke, so I don't think that'd really work out. :( We aren't racist, I promise. But it'd be pretty cool to chat online with a real shark, huh? I suppose if California were to drop off, the services / hub server / web server / DNS server would go bye bye too as it is located in California. Yeah... nevermind... we'd be S.O.L. Oh well... it was worth the try.

In short.... As always, your suggestions, comments, and opinion opinions will be gladly accepted and reviewed.... and then we'll do what we want anyway, naturally claiming any and all great ideas you have as our own, and promptly procrastinating on anything not important , and while simultaneously putting off all important things until we can't live with however it is without doing them anymore. We are NetAdmin. This is our vow. Okay cool.

Disclaimer: The I donI-don't care t-care attitude may or may not be the real, actual opinions or thoughts of the administration of TheZone IRC Network. Unless it changes more of your life than you on-the-line online chat habits.... WHO CARES?

Network Hierarchy and Administration

Darc — Fri, 12 Dec 2008 19:16:49 GMT
Revision 2 posted to TheZoneIRC Network by Darc on 12/12/2008 11:16:49 AM

Network Hierarchy and Administration

Filed under: services, network administrationservices , server hierarchy

Defense of Network Administration (Not that it needs to be defended. "Because I said so..." works for us most of the time.)

Due to some recent confusion, I wanted to clear some things up a bit (in a light-hearted and awesome way). I want to take some time to outline the structure of administration as it currently stands. To clarify, I'm not at all saying it will be in this fashion forever. I'd be the first person to sign the page to add more administrators IF the user base / number of servers required it. And I'm in the front of whatever methods you want to try to get us there.

In a world where there is only 1 server, and only a hand full of admin, it makes sense for the operators to maintain total control of the server and services, at the discretion of the server administrators. Why? Because any services action affects the entire server as a whole. Why is this different when there are 2 servers?

Well let’s suppose YOU are the Server Administrator. You run server 1, and, to avoid people thinking the servers are listed in order of importance, you are linked with server A. How do you feel about the Server Administrator making services changes affecting the registration of channels on your server, without your consent or concern? You probably don't feel too good about that. Why? Just because that person has an IRC server does not mean they should be entitled to powers that affect the servers of other people in that way. There's even an argument that could be made against server administrators having global (affective on all servers) power at all.

Well OK. So who controls the services? Well, I submit to you: the person we agreed would run them... within the guidelines we set when they started running. You might be asking, "Who is this 'we' you speak of?" The people that were there when they started running. Fast forward a few servers.... Now there are 8. Who runs services? The person we agreed would run them.

You may now be asking, "why can't I show up and link and instantly be a governing 'we' member?" And the answer is simple.

We are a network. You are a server. You can't expect to show up to EFnet and govern over their services. Okay, DALnet, but only because EFnet doesn't have services. My point is... when there is an already existing group of Server Administrators, them being okay with a new person able to GLine on their network is one thing.... asking them to be okay with a new services governor is a whole other thing.

Also... you have the issue of non-services network control. As a Server Administrator with only one server, you are a network administrator (in a network of one -- kind of like when you're in the army, but went rogue). With a link situation, there has to be someone to make sure the IRCd's are the same (or compatible) versions, make sure any network wide code modifications are made and in place, ensure connectivity is optimized and secured during essential times, as well as regulate network wide guidelines as a means of bringing unity together into everyone's experience on that particular network.

Current Network Administration, and TheZone History Lesson - 101

So, now you may ask... who holds this ever so heavy responsibility?! The answer is simple... it's as clear as a bell... we all have real lives and need someone to tell.... ooooh... crap. Right. I was being poetic again. Sorry. On TheZone IRC Network, there's a reason Syber holds the nickname "God." It was him, dos, and judge that started it up in the first place.

Well how did I (Darc) get here? A little while back, I was the "God" of a network called IdleWhores IRC Network (we had 5 servers at link time with TheZone). When we linked together, my server admins and I eventually dropped the name IdleWhores, which relinquished its network status to that of a channel (#IdleWhores), and there were 4 Network Administrators, myself, Syber, dos, and pre. This is what we refer to as a merge -- two individual separate networks coming together to form one bigger network. (Please note that when a single server is added to our network, we refer to that as a link, since the Server is a different level than a network (a collection of servers), as apposed to a network linking with another network, which I suppose would be a merge.)

dos and pre pre-tty (haha) much don't have a whole ton of interest in IRC at the moment, but I'm sure if either of them wanted to be active tomorrow, they could be... as they're good guys who started this thing in the beginning... but until such a time that they desire to be IRCool again, Syber and I are the guys.... and really I think Syber has the one up between him and myself as when we merged, we used TheZone's services, we use TheZone's name, we use TheZone's website (registered to one Syber), and so on. #TheZone -- is Syber's channel. He owns it. (Well, and dos I think too, technically.) He runs it. The buck stops there.

Will things stay the way they are? Hopefully not. We'd like nothing more than to be FORCED to add to the list of servers, operators, and network administrators, just so long that the driving force is an unmanageable-by-what-we-have-now (and growing) user base.

Instructions for Gaining Network Administration Status - (advanced)

Want to be a network administrator? I'd give you this advice:

    1) Learn how to administrate a server as thoroughly as Syber and myself, including full shell / IRCd config / good linux knowledge, and other IRC things (eggdrop, services, etc)...
    2) Earn our trust (by being logical, rational, and calm (with us))
    3) Get a Server. You can't go from IRC op / regular user to Network Administrator. Only in a world where our userbase was flourishing and unmanageable for us would a RELIABLE and TRUSTWORTHY Server Administrator be considered -- IF needed.
    4) Get enough users / servers on the network so that we need you. Otherwise... forget about it. There are already two chiefs... we need some Indians.
    5) Realize that if you're whining and begging about gaining this status, you will more than likely be viewed as someone who wants a power trip, and will likely never see the +N flag on your nick -- at least not on our network. So if you do just want a power trip -- hide it. Because we aren't here to stroke your already-too-large ego. We're here to stroke our already-too-large egos. And if you'd like to join is in that effort, that's more than OK. No, it won't get you net-admin brownie points.

Alternatively, grow a network of your own... a few servers and a decent amount of reliable/regular users/server administrators of your own, and perhaps we'd merge and you'd have it by default. Maybe. No promises though, and don't let the door hit you in the butt on the way out. Building an IRC network (already a mostly dying breed for smaller networks and networks that refuse public warez trading) is a lot of fun I hear.

Cap, recap, and rebottle

Network Hierarchy, IRCd's:

    Network Administrators
        - Server Administrators
            - IRC Operators
                - Channel Owners
                    - Registered Users
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Network Hierarchy, Services:

    Services Root Administrators (Full Root Access, including to Services Shell)
        - Services Administrators (Full in-IRC access)
            - Services Operators (Partial in-IRC Access)
                - Bender / Calculon / ProxyServ (not real access, I just liked the idea of making you feel like artificial intelligence eggdrop bots have more access than you.)
                    - Registered Users (Public in-IRC Access)
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Syber and I also serve as Services Root Administrators. Is there more than one needed? No, but if one of us gets hit by a bus, there's someone to pick up the slack. Also, there's the concern that California will drop into the pacific at some point in time, but as the services / hub server / web server / DNS server is located in California, I'd say we're S.O.L. if that happens anyway. Plus Paul will be swimming for a while, and would probably not care a whole lot about the network at the time. Unless he felt he could recruit some sharks or something to join as users. Then he'd make pitches between breaths and *** strokes. But I also hear that water beings have a little trouble with keeping computers not broke, so I don't think that'd really work out. :( We aren't racist, I promise. But it'd be pretty cool to chat online with a real shark, huh? Oh well... it was worth the try.

In short.... As always, your suggestions, comments, and opinion will be gladly accepted and reviewed.... and then we'll do what we want anyway, claiming any and all great ideas you have as our own, and promptly procrastinating on anything not important, and putting off all important things until we can't live with however it is anymore. We are NetAdmin. This is our vow. Okay cool.

Disclaimer: The I don't care attitude may or may not be the real, actual opinions or thoughts of the administration of TheZone IRC Network. Unless it changes more of your life than you on-the-line online chat habits.... WHO CARES?

Network Hierarchy and Administration

Darc — Fri, 12 Dec 2008 19:16:49 GMT
Revision 1 posted to TheZoneIRC Network by Darc on 12/12/2008 11:16:49 AM

Defense of Network Administration (Not that it needs to be defended. "Because I said so..." works for us most of the time.)

Due to some recent confusion, I wanted to clear some things up a bit (in a light-hearted and awesome way). I want to take some time to outline the structure of administration as it currently stands. To clarify, I'm not at all saying it will be in this fashion forever. I'd be the first person to sign the page to add more administrators IF the user base / number of servers required it. And I'm in the front of whatever methods you want to try to get us there.

In a world where there is only 1 server, and only a hand full of admin, it makes sense for the operators to maintain total control of the server and services, at the discretion of the server administrators. Why? Because any services action affects the entire server as a whole. Why is this different when there are 2 servers?

Well let’s suppose YOU are the Server Administrator. You run server 1, and, to avoid people thinking the servers are listed in order of importance, you are linked with server A. How do you feel about the Server Administrator making services changes affecting the registration of channels on your server, without your consent or concern? You probably don't feel too good about that. Why? Just because that person has an IRC server does not mean they should be entitled to powers that affect the servers of other people in that way. There's even an argument that could be made against server administrators having global (affective on all servers) power at all.

Well OK. So who controls the services? Well, I submit to you: the person we agreed would run them... within the guidelines we set when they started running. You might be asking, "Who is this 'we' you speak of?" The people that were there when they started running. Fast forward a few servers.... Now there are 8. Who runs services? The person we agreed would run them.

You may now be asking, "why can't I show up and link and instantly be a governing 'we' member?" And the answer is simple.

We are a network. You are a server. You can't expect to show up to EFnet and govern over their services. Okay, DALnet, but only because EFnet doesn't have services. My point is... when there is an already existing group of Server Administrators, them being okay with a new person able to GLine on their network is one thing.... asking them to be okay with a new services governor is a whole other thing.

Also... you have the issue of non-services network control. As a Server Administrator with only one server, you are a network administrator (in a network of one -- kind of like when you're in the army, but went rogue). With a link situation, there has to be someone to make sure the IRCd's are the same (or compatible) versions, make sure any network wide code modifications are made and in place, ensure connectivity is optimized and secured during essential times, as well as regulate network wide guidelines as a means of bringing unity together into everyone's experience on that particular network.

Current Network Administration, and TheZone History Lesson - 101

So, now you may ask... who holds this ever so heavy responsibility?! The answer is simple... it's as clear as a bell... we all have real lives and need someone to tell.... ooooh... crap. Right. I was being poetic again. Sorry. On TheZone IRC Network, there's a reason Syber holds the nickname "God." It was him, dos, and judge that started it up in the first place.

Well how did I (Darc) get here? A little while back, I was the "God" of a network called IdleWhores IRC Network (we had 5 servers at link time with TheZone). When we linked together, my server admins and I eventually dropped the name IdleWhores, which relinquished its network status to that of a channel (#IdleWhores), and there were 4 Network Administrators, myself, Syber, dos, and pre. This is what we refer to as a merge -- two individual separate networks coming together to form one bigger network. (Please note that when a single server is added to our network, we refer to that as a link, since the Server is a different level than a network (a collection of servers), as apposed to a network linking with another network, which I suppose would be a merge.)

dos and pre pre-tty (haha) much don't have a whole ton of interest in IRC at the moment, but I'm sure if either of them wanted to be active tomorrow, they could be... as they're good guys who started this thing in the beginning... but until such a time that they desire to be IRCool again, Syber and I are the guys.... and really I think Syber has the one up between him and myself as when we merged, we used TheZone's services, we use TheZone's name, we use TheZone's website (registered to one Syber), and so on. #TheZone -- is Syber's channel. He owns it. (Well, and dos I think too, technically.) He runs it. The buck stops there.

Will things stay the way they are? Hopefully not. We'd like nothing more than to be FORCED to add to the list of servers, operators, and network administrators, just so long that the driving force is an unmanageable-by-what-we-have-now (and growing) user base.

Instructions for Gaining Network Administration Status - (advanced)

Want to be a network administrator? I'd give you this advice:

    1) Learn how to administrate a server as thoroughly as Syber and myself, including full shell / IRCd config / good linux knowledge, and other IRC things (eggdrop, services, etc)...
    2) Earn our trust (by being logical, rational, and calm (with us))
    3) Get a Server. You can't go from IRC op / regular user to Network Administrator. Only in a world where our userbase was flourishing and unmanageable for us would a RELIABLE and TRUSTWORTHY Server Administrator be considered -- IF needed.
    4) Get enough users / servers on the network so that we need you. Otherwise... forget about it. There are already two chiefs... we need some Indians.
    5) Realize that if you're whining and begging about gaining this status, you will more than likely be viewed as someone who wants a power trip, and will likely never see the +N flag on your nick -- at least not on our network. So if you do just want a power trip -- hide it. Because we aren't here to stroke your already-too-large ego. We're here to stroke our already-too-large egos. And if you'd like to join is in that effort, that's more than OK. No, it won't get you net-admin brownie points.

Alternatively, grow a network of your own... a few servers and a decent amount of reliable/regular users/server administrators of your own, and perhaps we'd merge and you'd have it by default. Maybe. No promises though, and don't let the door hit you in the butt on the way out. Building an IRC network (already a mostly dying breed for smaller networks and networks that refuse public warez trading) is a lot of fun I hear.

Cap, recap, and rebottle

Network Hierarchy, IRCd's:

    Network Administrators
        - Server Administrators
            - IRC Operators
                - Channel Owners
                    - Registered Users
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Network Hierarchy, Services:

    Services Root Administrators (Full Root Access, including to Services Shell)
        - Services Administrators (Full in-IRC access)
            - Services Operators (Partial in-IRC Access)
                - Bender / Calculon / ProxyServ (not real access, I just liked the idea of making you feel like artificial intelligence eggdrop bots have more access than you.)
                    - Registered Users (Public in-IRC Access)
                        - People We Couldn't Possibly Care Less About If Our Lives Depended On It (YOU ARE HERE)

Syber and I also serve as Services Root Administrators. Is there more than one needed? No, but if one of us gets hit by a bus, there's someone to pick up the slack. Also, there's the concern that California will drop into the pacific at some point in time, but as the services / hub server / web server / DNS server is located in California, I'd say we're S.O.L. if that happens anyway. Plus Paul will be swimming for a while, and would probably not care a whole lot about the network at the time. Unless he felt he could recruit some sharks or something to join as users. Then he'd make pitches between breaths and *** strokes. But I also hear that water beings have a little trouble with keeping computers not broke, so I don't think that'd really work out. :( We aren't racist, I promise. But it'd be pretty cool to chat online with a real shark, huh? Oh well... it was worth the try.

In short.... As always, your suggestions, comments, and opinion will be gladly accepted and reviewed.... and then we'll do what we want anyway, claiming any and all great ideas you have as our own, and promptly procrastinating on anything not important, and putting off all important things until we can't live with however it is anymore. We are NetAdmin. This is our vow. Okay cool.

Disclaimer: The I don't care attitude may or may not be the real, actual opinions or thoughts of the administration of TheZone IRC Network. Unless it changes more of your life than you on-the-line online chat habits.... WHO CARES?