Difference between revisions of "EliteBNC"
Iota.spencer (talk | contribs) (It would help if I updated this more...) |
|||
| Line 6: | Line 6: | ||
'''Robby''' (USA) - Co-owner, Accounts Administrator, Website Administrator, Service Bot Developer<br /> | '''Robby''' (USA) - Co-owner, Accounts Administrator, Website Administrator, Service Bot Developer<br /> | ||
'''Armageddon''' (AUS) - Co-owner, Servers Administrator, Owner of Alpha/Delta/Epsilon/Gamma/Omega/Zeta servers, Accounts Administrator, Website Administrator<br /> | '''Armageddon''' (AUS) - Co-owner, Servers Administrator, Owner of Alpha/Delta/Epsilon/Gamma/Omega/Zeta servers, Accounts Administrator, Website Administrator<br /> | ||
''' | '''Boomer`''' (AUS) - Accounts Administrator<br /> | ||
''' | '''Russell''' (UK) – Technical Advisor, Owner of Rho server, Accounts Administrator<br /> | ||
''' | '''Timmi''' (IN) – Accounts Administrator, Servers Co-administrator (Delta/Epsilon)<br /> | ||
== Server Locations/IP Counts: == | == Server Locations/IP Counts: == | ||
'''Alpha''' – | '''Alpha''' – Nevada, United States – 3 IPv4, 7 IPv6 (native) | ||
'''Delta''' – New York, United States – 4 IPv4<br /> | <br /> | ||
'''Epsilon''' – Amsterdam, Netherlands – | '''Delta''' – New York, United States – 4 IPv4 | ||
'''Gamma''' – United States – 5 IPv4<br /> | <br /> | ||
''' | '''Epsilon''' – Amsterdam, Netherlands – 5 IPv4, 6 IPv6 (native) | ||
'''Sigma''' – | <br /> | ||
''' | '''Gamma''' – New Jersey, United States – 5 IPv4 | ||
'''Zeta''' – France – 1 IPv4, 6 IPv6 | <br /> | ||
'''Kappa''' – Texas, United States – 1 IPv4, 1 IPv6 (native) | |||
<br /> | |||
'''Rho''' – Cheshire, United Kingdom – 4 IPv4, 1 IPv6 (native) | |||
<br /> | |||
'''Sigma''' – Nuernberg, Germany – 3 IPv4, 7 IPv6 (native) | |||
<br /> | |||
'''Tau''' – New Jersey, United States – 1 IPv4, 1 IPv6 (native) | |||
<br /> | |||
'''Theta''' - Pennsylvania, United States – 3 IPv4 | |||
<br /> | |||
'''Zeta''' – Roubaix, France – 1 IPv4, 6 IPv6 (native) | |||
== Rules == | == Rules == | ||
1) Each user is restricted to 1 account per IRC network, 3 accounts total unless other arrangements are made. Attempted hoarding of accounts may result in you being banned from our service. | |||
<br /> | |||
2) Do not break any rule of the IRC network your account is assigned to. This includes ban evading, spamming, repeated flooding, harassment of the network’s staff, or any other rules the IRC network may have in place. | |||
<br /> | |||
3) Do not use our service for anything illegal, such as filesharing, child pornography, or soliciting children in an inappropriate manner. This will lead to your immediate removal from our service. | |||
<br /> | |||
4) Our service bot monitors account activity (connects, IPs, time online/offline. We do NOT log text, either on channel, PM or otherwise as per User Privacy regulations), we know when an account is banned/z:lined/k:lined/etc. This may lead to your account being removed, or at minimum blocked until we know the reason the IRC network took that action. G:lines for “too many host connections” or similar kills that are usually the result of issues on the network’s end are not counted. | |||
<br /> | |||
5) Any account not accessed (used via IRC client) after 3 days of being accepted will be deleted as an ‘unused account’. Setting it up via the webpanel and parking it in channels does not count as being accessed. If you do not receive the information email or have problems accessing your account, please contact the staff. | |||
<br /> | |||
6) Any account less than 180 days old that is idle for 30 days or more will be removed unless you contact the staff. If you have had your account for 180 days, the idle time is 40 days before being removed. | |||
<br /> | |||
7) Any ‘parking’ account set up then idle for 5 or more days will be removed. If you don’t use it, you lose it. | |||
<br /> | |||
We do not allow our users to change their IRC servers on their own. If you need to have the IRC server changed or additional servers for the same IRC network added, please contact staff in one of the IRC #EliteBNC channels (see the list on our home page), or via email at: support@elitebnc.org. | |||
Thanks, EliteBNC staff. | |||
Revision as of 21:04, 10 March 2013
About Us
The current staff of EliteBNC came together volunteering their servers and/or services for another free bouncer service. We decided to split off and start our own service, with a better commitment to not just supporting the users, but stronger stability of the service itself. We took extra time to get this service set up properly instead of just rushing into things, and that will reflect in the product we bring to you. We are sure you will see the difference and enjoy your stay with us.
Staff:
Robby (USA) - Co-owner, Accounts Administrator, Website Administrator, Service Bot Developer
Armageddon (AUS) - Co-owner, Servers Administrator, Owner of Alpha/Delta/Epsilon/Gamma/Omega/Zeta servers, Accounts Administrator, Website Administrator
Boomer` (AUS) - Accounts Administrator
Russell (UK) – Technical Advisor, Owner of Rho server, Accounts Administrator
Timmi (IN) – Accounts Administrator, Servers Co-administrator (Delta/Epsilon)
Server Locations/IP Counts:
Alpha – Nevada, United States – 3 IPv4, 7 IPv6 (native)
Delta – New York, United States – 4 IPv4
Epsilon – Amsterdam, Netherlands – 5 IPv4, 6 IPv6 (native)
Gamma – New Jersey, United States – 5 IPv4
Kappa – Texas, United States – 1 IPv4, 1 IPv6 (native)
Rho – Cheshire, United Kingdom – 4 IPv4, 1 IPv6 (native)
Sigma – Nuernberg, Germany – 3 IPv4, 7 IPv6 (native)
Tau – New Jersey, United States – 1 IPv4, 1 IPv6 (native)
Theta - Pennsylvania, United States – 3 IPv4
Zeta – Roubaix, France – 1 IPv4, 6 IPv6 (native)
Rules
1) Each user is restricted to 1 account per IRC network, 3 accounts total unless other arrangements are made. Attempted hoarding of accounts may result in you being banned from our service.
2) Do not break any rule of the IRC network your account is assigned to. This includes ban evading, spamming, repeated flooding, harassment of the network’s staff, or any other rules the IRC network may have in place.
3) Do not use our service for anything illegal, such as filesharing, child pornography, or soliciting children in an inappropriate manner. This will lead to your immediate removal from our service.
4) Our service bot monitors account activity (connects, IPs, time online/offline. We do NOT log text, either on channel, PM or otherwise as per User Privacy regulations), we know when an account is banned/z:lined/k:lined/etc. This may lead to your account being removed, or at minimum blocked until we know the reason the IRC network took that action. G:lines for “too many host connections” or similar kills that are usually the result of issues on the network’s end are not counted.
5) Any account not accessed (used via IRC client) after 3 days of being accepted will be deleted as an ‘unused account’. Setting it up via the webpanel and parking it in channels does not count as being accessed. If you do not receive the information email or have problems accessing your account, please contact the staff.
6) Any account less than 180 days old that is idle for 30 days or more will be removed unless you contact the staff. If you have had your account for 180 days, the idle time is 40 days before being removed.
7) Any ‘parking’ account set up then idle for 5 or more days will be removed. If you don’t use it, you lose it.
We do not allow our users to change their IRC servers on their own. If you need to have the IRC server changed or additional servers for the same IRC network added, please contact staff in one of the IRC #EliteBNC channels (see the list on our home page), or via email at: support@elitebnc.org.
Thanks, EliteBNC staff.