“Entry is Consent” Channels — Acceptable Use

For a long time, “Entry is consent” was used in channel topics and entry messages when a person joined.

  • Submissives agreed to any form of use by dominants upon entry.
  • Dominants agreed to be ‘broken’ upon entry.
  • Consenting to hypnosis for various things upon entry.
  • Any variation on the above and other obscure instances we’ve come across.

Because Cuff-Link is pro-consent, and the idea of consent is tantamount in most of our decisions regarding what people can and cannot do under our ToS, we have had to revisit this particular mode of operating channels.

It is no longer acceptable to gain consent in this manner from other users, especially since clients have the ability to block topics and notices. We now require that explicit consent be gained at least once upon entry by each person consenting to a thing. To do this, you will need to either ensure people have registered nicknames or you will have to drum up a bot that will voice users with a trigger. Admins, if they see topics or entry messages or any other form of notice stating “entry is consent” or anything similar to this, will change said messages to indicate this isn’t okay, and please come to #help and read this post for more information.

Please note, if you want to be strict about submissives being available for use, while you have to gain explicit consent from them for this, if they decide to revoke consent, it is your responsibility to remove them from the channel if they won’t leave on their own. In addition to this, you must be clear on what is involved in having given consent:

  • Use for sexual favours.
  • Use for non-sexual serving.
  • CNC use [although we absolutely would prefer that CNC only be done between long-time partners or in established TPE relationships. See our CNC post for more.
  • Hypnosis.
  • Enduring rotten vegetation being lobbed at you.
  • Etcetera, etcetera, etcetera.

No Bot:

  • Tell users who must consent to be present to give explicit consent that time for subsequent visits to the channel.
  • Use ChanServ to add the user to the auto-voice list with: /cs vop #channel add nickname
  • Users who wish to revoke consent may either ask a chanop to remove them from the vop list or they may do so themselves by issuing this command:
    • /cs vop #channel del NickservAccountName
    • **In order to use the above command, you *must* use your NickServ Account Name. If you’re unsure which nickname that is, /whois yourself, and it will be the name attached to the “Is logged in as” or “Is identified as” line.
  • Channel owners who do not wish to have a person in their channel anymore, can, of course, use the /remove, /cs akick, /ban, and /kick options, which are at their disposal.

With Bot/unregistered nicknames:

Simply program the bot to respond to a !consented or !consent or trigger, which will then tell the bot to voice the person. If the person does not consent, and you don’t want to make an exception for them, then use /remove or /kick and /ban. If there is enough interest in such a bot, the Network Admins may be willing to create one for this purpose and have it join to channels that wish to make use of it — please note: unlike our profile bots, if we do create a service for this, the bot will not be customisable. It will do the following, and the following alone:

  • !consent – voice the user who consents to use.
  • !revoke – revoke consent will /remove the user from the channel.

However, if you have one of our profile bots in your channel, we could create an add-on feature that would do this for you, but if that is the case, you would not be able to use the voice-on-profile feature.

If we do implement such a network service, it will be available to all channels. We will not require a user minimum in order to implement the feature, however it will require that the channel be registered for a certain period of time and that the channel has an active population, even if small. If you’re interested in a feature of this sort, please say so in the comments below!


Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.