23-02-2016, 10:34 PM
(This post was last modified: 12-05-2017, 02:45 PM by Knight_Errant.)
Private Rooms
Anyone who joins LibraIrc may own their own private room and may also choose their own operaters and have their own rules, however, LibraIrc Admin expects all room owners to adhere to some basic rules which are linked as part of our ToS (Terms of Service). These are as follows
1. Rooms must be registered with an acceptable title, for example #cybersex, #incest_lovers, #pedo_lovers are not acceptable and brings the standard expected of the server into disrepute and will result in Admin closing the room
2. Rooms used to store floodbots , abusers and chatters who create troubles in public channels are not allowed and will be immediately closed by Admin
3. Rooms used to hold bots which are held there to hold rooms or help other users in their rooms as “guards” “!Seen bots” “TriviaBots” “weather bots” “FunBots” are allowed but the maximum allowed in any private room is 50.
4. IRCops do not normally interfere with any owners private rooms but do reserve the right to do so if they are found to be used for any illegal activities, such as drug dealing, the grooming of minors are just two examples which will immediately result in the room being closed and the owner removed/banned from the Network
5. As the server grows some big private rooms maybe placed on the web pages, should this be the case the owners will be required to totally adhere with LibraIrc’s full ToS (Terms of Service)
6. Chanops are allowed to own a private room or be in a friends private room but are expected to act responsibly. Any breaches of points 1,2 or 4 above will result in their access as a chanop being removed.
To register your own room you will first of all need to ensure your own nick is registered. Simply type /join #your_room_Name_Here and then register the room as follows /msg chanserv REGISTER #room_name (password). Once this is done you can then set access levels for any of your friends whom you wish to have some kind of status in the room from simple voicing to having a joint owner or successor. Any user who you make a successor will automatically take over the room should you decide to drop it or if your nick drops. Joint ownership or making a user a successor is a high risk and should only be done if you absolutely trust the user, many room takeovers have happened in the past due to breaches of trust.
IRCops do not normally interfere with private rooms, however, should a room owner approach an IRCop for assistance, for example due to their channel being constantly flooded, if an IRCop is active they will try to assist if asked.
IRCops sometimes get complaints in private from users about being kicked or banned from private rooms, should this happen the IRCop will always in the first instance refer the user to the room owner or owners pointing out that it is a private room and as such the IRCops do not make any private room rules. At the end of the day room owners can have whom they wish in their own rooms as long as they do not breach the rules set out above.
For information the present IRCops on LibraIrc are libra, Sicilia, Knight_Errant, and Wildcard. These IRCops form the Administrative Team for the LibraIrc Network and owners should be aware that at any time a member of this team may override and enter any private room should they suspect or has been reported that illegal activity is/has been taking place which may damage the reputation of the LibraIrc Network
Some Basic Access Commands
ACCESS SET allows you to set specific flags on a user above or below a certain role or lets you change the role a user is in. Multiple flags should be seperated by a space and have the modifier (+ or -) in front of each flag.
Syntax: [tt]ACCESS <#channel> SET <user> <role|flags>[/tt]
Flags:
[tt]+voice - Enables use of the voice/devoice commands.[/tt] [tt]+autovoice - Enables automatic voice.[/tt] [tt]+halfop - Enables use of the halfop/dehalfop commands.[/tt] [tt]+autohalfop - Enables automatic halfop.[/tt] [tt]+op - Enables use of the op/deop commands.[/tt] [tt]+autoop - Enables automatic op.[/tt] [tt]+protect - Enables use of the protect/deprotect commands.[/tt] [tt]+owner - Enables use of the owner/deowner commands.[/tt] [tt]+set - Enables use of the set command.[/tt] [tt]+invite - Enables use of the invite and getkey commands.[/tt] [tt]+remove - Enables use of the kick, kickban, ban and unban commands.[/tt] [tt]+remove - Enables use of the ban and unban commands.[/tt] [tt]+remove - Enables use of the unban command.[/tt] [tt]+recover - Enables use of the recover and clear commands.[/tt] [tt]+acl-change - Enables modification of channel access lists.[/tt] [tt]+topic - Enables use of the topic and topicappend commands.[/tt] [tt]+acl-view - Enables viewing of channel access lists.[/tt] [tt]+successor - Marks the user as a successor.[/tt] [tt]+founder - Grants full founder access.[/tt]
Anyone who joins LibraIrc may own their own private room and may also choose their own operaters and have their own rules, however, LibraIrc Admin expects all room owners to adhere to some basic rules which are linked as part of our ToS (Terms of Service). These are as follows
1. Rooms must be registered with an acceptable title, for example #cybersex, #incest_lovers, #pedo_lovers are not acceptable and brings the standard expected of the server into disrepute and will result in Admin closing the room
2. Rooms used to store floodbots , abusers and chatters who create troubles in public channels are not allowed and will be immediately closed by Admin
3. Rooms used to hold bots which are held there to hold rooms or help other users in their rooms as “guards” “!Seen bots” “TriviaBots” “weather bots” “FunBots” are allowed but the maximum allowed in any private room is 50.
4. IRCops do not normally interfere with any owners private rooms but do reserve the right to do so if they are found to be used for any illegal activities, such as drug dealing, the grooming of minors are just two examples which will immediately result in the room being closed and the owner removed/banned from the Network
5. As the server grows some big private rooms maybe placed on the web pages, should this be the case the owners will be required to totally adhere with LibraIrc’s full ToS (Terms of Service)
6. Chanops are allowed to own a private room or be in a friends private room but are expected to act responsibly. Any breaches of points 1,2 or 4 above will result in their access as a chanop being removed.
To register your own room you will first of all need to ensure your own nick is registered. Simply type /join #your_room_Name_Here and then register the room as follows /msg chanserv REGISTER #room_name (password). Once this is done you can then set access levels for any of your friends whom you wish to have some kind of status in the room from simple voicing to having a joint owner or successor. Any user who you make a successor will automatically take over the room should you decide to drop it or if your nick drops. Joint ownership or making a user a successor is a high risk and should only be done if you absolutely trust the user, many room takeovers have happened in the past due to breaches of trust.
IRCops do not normally interfere with private rooms, however, should a room owner approach an IRCop for assistance, for example due to their channel being constantly flooded, if an IRCop is active they will try to assist if asked.
IRCops sometimes get complaints in private from users about being kicked or banned from private rooms, should this happen the IRCop will always in the first instance refer the user to the room owner or owners pointing out that it is a private room and as such the IRCops do not make any private room rules. At the end of the day room owners can have whom they wish in their own rooms as long as they do not breach the rules set out above.
For information the present IRCops on LibraIrc are libra, Sicilia, Knight_Errant, and Wildcard. These IRCops form the Administrative Team for the LibraIrc Network and owners should be aware that at any time a member of this team may override and enter any private room should they suspect or has been reported that illegal activity is/has been taking place which may damage the reputation of the LibraIrc Network
Some Basic Access Commands
ACCESS SET allows you to set specific flags on a user above or below a certain role or lets you change the role a user is in. Multiple flags should be seperated by a space and have the modifier (+ or -) in front of each flag.
Syntax: [tt]ACCESS <#channel> SET <user> <role|flags>[/tt]
Flags:
[tt]+voice - Enables use of the voice/devoice commands.[/tt] [tt]+autovoice - Enables automatic voice.[/tt] [tt]+halfop - Enables use of the halfop/dehalfop commands.[/tt] [tt]+autohalfop - Enables automatic halfop.[/tt] [tt]+op - Enables use of the op/deop commands.[/tt] [tt]+autoop - Enables automatic op.[/tt] [tt]+protect - Enables use of the protect/deprotect commands.[/tt] [tt]+owner - Enables use of the owner/deowner commands.[/tt] [tt]+set - Enables use of the set command.[/tt] [tt]+invite - Enables use of the invite and getkey commands.[/tt] [tt]+remove - Enables use of the kick, kickban, ban and unban commands.[/tt] [tt]+remove - Enables use of the ban and unban commands.[/tt] [tt]+remove - Enables use of the unban command.[/tt] [tt]+recover - Enables use of the recover and clear commands.[/tt] [tt]+acl-change - Enables modification of channel access lists.[/tt] [tt]+topic - Enables use of the topic and topicappend commands.[/tt] [tt]+acl-view - Enables viewing of channel access lists.[/tt] [tt]+successor - Marks the user as a successor.[/tt] [tt]+founder - Grants full founder access.[/tt]
![[Image: 2m4dtfs.png]](http://i66.tinypic.com/2m4dtfs.png)
