Statically generated site for Redbrick
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

4.7 KiB

title date type
Regulations 2016-04-17 16:22:40 about
  1. Members wishing to run networked programs must first obtain the permission of the committee. The committee reserves the right to shut down such programs without notice.
  2. Members wishing to make an announcement to the membership are encouraged to use the Newsgroup system, but in cases where mailing the membership is considered vital, the permission of the committee must be obtained first.
  3. Spamming other users is an offense (e.g. mass mailing, system-wide write messages, or flooding chat rooms) unless a practical need to do so has been presented to the committee, and their permission obtained for such a mass communication.
  4. Users are requested to take all reasonable precautions to ensure the security of their account, and to comply with the instructions of Redbrick’s System Administrators and with their guidelines on security.
  5. The reprovision of Dublin City University Networking Society Services or Equipment requires the approval of the committee.
  6. Certain file types are banned by our web server and users should not try to circumvent this rule. For more information on the restricted file types and getting access, contact Helpdesk.

The following regulations are additional to the Society’s own rules...


  • These regulations are for the protection of the system and the society. We have a small but dedicated Admin team.
  • Regulation 1, about networked programs, is primarily for security reasons. Networked programs are programs which allow non-system users to interact with them, say via TCP/IP. There is an inherent security risk here.
  • Regulations 2 and 3 are self-explanatory, spam is not on!!
  • Regulation 4 should be an obvious assumption for any accounts you hold.
  • Regulation 5 is simply to safeguard that we can control what services are provided to others (similar to regulation 1), only the Admin team can really judge what we can support. Also, private members should not be giving “accounts” to others, their account is for their own use only.

Rules For #lobby.

Users must obtain the permission of the committee before using bots/scripts in #lobby.

  • Users are not to spam the channel.
  • Users should not encourage others to enter IRC commands that might be harmful or that produce undesirable effects.
  • Users are not to direct people to unsafe or inappropriate links without prior warning of their content.
  • Ops are, as a general rule, a committee privilege. While they may be used by others on occasion, they are only for administrative/emergency use. Abuse of ops will lead to their removal.
  • Offences shall be dealt with by the committee and may lead to banning, repeated offences may lead to disuserment.
  • Ops should endeavour to use common sense when enforcing the rules.

Authorized Bots in #lobby

  • mincebot
  • teh
  • creadak

User Agreement

By logging into Redbrick you agree to these terms and conditions.

  1. Redbrick is governed by various regulations, as detailed above
  2. Redbrick take no responsibility for the integrity of user data stored or developed using Redbrick. While Redbrick will endeavour to provide a backup service to all users, Redbrick cannot ultimately guarantee protection from system failures, user accidents or malicious activities by other users. So please don’t leave the only copy of your 4th year final project on Redbrick! :o) Redbrick offers no guarantee of user privacy. Redbrick administrators have the power to search accounts and all user data therein for any material that is considered to be illegal (by the regulations we mentioned above) or that pose a security threat to other user accounts or even the system as a whole. Redbrick will endeavour to make all user accounts secure by default but it is impossible to ‘police’ all user activities, which may include attempts to ‘trojan’ or subvert other user accounts.
  3. Any attempts to undermine or breach the security of Redbrick or any user’s account will be taken as a serious matter, and will be subject to appropriate punishment as determined by the committee. Such punishments will typically amount to a disabling of the user’s account for a certain period. All other services (events, talks, tutorials) that Redbrick provide to members will of course still be available to the user.
  4. Redbrick reserve the right to update this agreement at any time in the future. Should this be necessary, you will be asked to agree to these terms and conditions again with the new agreement replacing previous versions.