<?xml version="1.0" encoding="utf-8"?>
<!-- 
     draft-rfcxml-general-template-standard-00
  
     This template includes examples of the most commonly used features of RFCXML with comments 
     explaining how to customise them. This template can be quickly turned into an I-D by editing 
     the examples provided. Look for [REPLACE], [REPLACE/DELETE], [CHECK] and edit accordingly.
     Note - 'DELETE' means delete the element or attribute, not just the contents.
     
     Documentation is at https://authors.ietf.org/en/templates-and-schemas
-->
<?xml-model href="rfc7991bis.rnc"?>  <!-- Required for schema validation and schema-aware editing -->
<!-- <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> -->
<!-- This third-party XSLT can be enabled for direct transformations in XML processors, including most browsers -->


<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<!-- If further character entities are required then they should be added to the DOCTYPE above.
     Use of an external entity file is not recommended. -->

<rfc
  xmlns:xi="http://www.w3.org/2001/XInclude"
  category="info"
  docName="draft-rfcxml-general-the-new-webiquette-00"
  ipr="trust200902"
  obsoletes=""
  updates=""
  submissionType="IETF"
  xml:lang="en"
  version="3">
<!-- [REPLACE] 
       * docName with name of your draft
     [CHECK] 
       * category should be one of std, bcp, info, exp, historic
       * ipr should be one of trust200902, noModificationTrust200902, noDerivativesTrust200902, pre5378Trust200902
       * updates can be an RFC number as NNNN
       * obsoletes can be an RFC number as NNNN 
-->

  <front>
    <title abbrev="The New Webiquette">The New Webiquette</title>
    <!--  [REPLACE/DELETE] abbrev. The abbreviated title is required if the full title is longer than 39 characters -->

    <seriesInfo name="Internet-Draft" value="draft-rfcxml-general-the-new-webiquette-00"/>
   
    <author fullname="Kate" initials="K" role="editor" surname="Kate">
      <!-- [CHECK]
             * initials should not include an initial for the surname
             * role="editor" is optional -->
    <!-- Can have more than one author -->
      
    <!-- all of the following elements are optional -->
      <address>
        <postal>
          <!-- Reorder these if your country does things differently -->
          <country>Germany</country>
          <!-- Uses two letter country code -->
        </postal>        
        <email>kate_9023+rfc-editor@systemli.org</email>  
      </address>
    </author>
   
    <date year="2022"/>
    <!-- On draft subbmission:
         * If only the current year is specified, the current day and month will be used.
         * If the month and year are both specified and are the current ones, the current day will
           be used
         * If the year is not the current one, it is necessary to specify at least a month and day="1" will be used.
    -->

    <area>General</area>
    <workgroup>Internet Engineering Task Force</workgroup>
    <!-- "Internet Engineering Task Force" is fine for individual submissions.  If this element is 
          not present, the default is "Network Working Group", which is used by the RFC Editor as 
          a nod to the history of the RFC Series. -->

    <keyword>webiquette</keyword>
    <!-- [REPLACE/DELETE]. Multiple allowed.  Keywords are incorporated into HTML output files for 
         use by search engines. -->

    <abstract>
      <t>The inspiration for this document came from RFC 1855 ("Netiquette"), which is now partially obsolete and no longer maintained. A lot has happened on the Internet since then (social media, video conferencing, deepfakes, ad networks), which should be applied in a netiquette. Like in RFC 1855 this is only a minimal standard. </t>
    </abstract>
 
  </front>

  <middle>
    
    <section>
      <name>Introduction</name>
      <t>A Webiquette to make the internet a better place.</t>
      
      <section>
        <name>Requirements Language</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
          "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
          RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
          interpreted as described in BCP 14 <xref target="RFC2119"/>
          <xref target="RFC8174"/> when, and only when, they appear in
          all capitals, as shown here.</t>
      </section>
      <!-- [CHECK] The 'Requirements Language' section is optional -->

    </section>

   <section anchor="status">
   <name>Status of the Memo</name>
   <t>This memo does not specify an Internet standard of any kind.</t>
   </section>
   
    <section anchor="user-guidelines">
    <name>User Guidelines"</name>
    <t>For making the Internet a place where many people feel comfortable, it needs some rules. What you can do in particular as a regular user can be found in section 1.1 to 1.4.</t>
    </section>
    
    <section anchor="one-to-one-messaging">
      <name>One-to-One-Messaging</name>
      <t>We are talking about a direct conversation with a person (in writing). This can be via email, chat, private message in social media or similar. </t>
           
      <ul>
        <li>If you Do not have anything important to say, say nothing.</li>
      </ul>
      
      <ul>
        <li>Ensure you are calm before you reply. If needed try to wait a night before reacting to a text.</li>
      </ul>

      <ul>
        <li>Avoid sentences that are written exclusively in capital letters. This looks as if YOU ARE SHOUTING.</li>
      </ul>

      <ul>
        <li>Use smilies or emojies to convey emotions in a message. Use them wisely and not excessively ;-) </li>
      </ul>

      <ul>
        <li>Use irony and sarcasm wisely. Your counterpart does not see you and your text might come across as overly agressive.</li>
      </ul>

      <ul>
        <li>Speaking of language. Do not impose your language on other people. Do not (impose to) correct other persons' way of speaking.</li>
      </ul>

      <ul>
        <li>If someone is using a nickname/pseudonym/username, respect the users privacy, even if you know the person. Do not use the real name online without permission. </li>
      </ul>

      <ul>
        <li>Assume when you write an email or a private message on social media that it can be read and analyzed by third parties. Think carefully about what you write or use proper encryption.  </li>
      </ul>

      <ul>
        <li>Your counterpart may have another cultural background, other values, speaks other languages or has a different form of humor than you do. Keep that in mind when communicating. </li>
      </ul>


      <ul>
        <li>Keep in mind that people may be located all around the globe when communicating online. Do not assume an immediate response. The person could be sleeping, at work, or busy otherwise.</li>
      </ul>

      <ul>
        <li>Do not expect strangers on the Internet to help you with general technical questions. Do not just write to people you know on the Internet and expect a response to help you. If you have technical questions, turn to appropriate internet forums, mailing lists, chat rooms etc. who are there to help.</li>
      </ul>

      <ul>
        <li>Do not send chain letters. Just do not.</li>
      </ul>

      <ul>
        <li>Do not send an unsolicited wall of text. People are busy and do not have the time to read through unfiltered content. If you can not avoid a long text: Proofread it, make it more readable (e.g. add more paragraphs) and check if the context makes sense before you send it. If necessary include a short summary.</li>
      </ul>


      <ul>
        <li>If you answer to a longer text or a couple of days later make sure you Do not send TOFU (Text Over, Fullquote Under). Always refer or quote the paragraphs you are answering to and shorten your reply by skipping the unnecessary parts.</li>
      </ul>

      <ul>
        <li>Do not send SPAM e-mails. A lot of countries have Anti-Spam-Laws.</li>
      </ul>

      <ul>
        <li>Do not distribute pornographic (e.g. nude pictures) or violent material. Not even if it is already on the Internet. You never know if the people who are on the pictures know about it or if the recipient wants to see it.</li>
      </ul>

      <ul>
        <li>Some social networks push you via gamification to send a picture every day to people close to you, which leads to many pictures of shoes, trains and other things just to achieve this goal. A friendship is not bound to such things. Remember that you can disturb other people in public and/or violate privacy laws. Also remember that the picture you send to your friend also consumes bandwidth and money.</li>
      </ul>

      <ul>
        <li>Always check if your messaging a single person or a group of people before sending.</li>
      </ul>

      <ul>
        <li>Implement the RFC rule RFC760 and RFC791: In general, an implementation should be conservative in its sending behavior, and liberal in its receiving behavior for Messages: In general, a message should be conservative in its sending behavior, and liberal in its receiving behavior. </li>
      </ul>

     </section>   

    <!-- NEW SECTION BEGINNING HERE-->


    <section anchor="one-to-many-messaging">
      <name>One-to-Many-Messaging</name>
      <t>This can represent a conversation with several participants via mail, mailing lists, chat, forum, microblogging services, social media or similar. All rules from One-to-One Messaging also appear to One-to-Many Messaging but One-to-Many also includes:</t>

      <ul>
        <li>Read the comments in a room before you participate in a discussion. When the atmosphere is already heated up, do not put oil in the flames.</li>
      </ul>

      <ul>
        <li>Do not hijack a topic or post. Thread hijacking means when someone opens a thread on a forum or comment a certain topic that a single person or more use this thread for off-topic, have a conversation within the conversation or point or use it for other opportunities e. g. other cases (or making money). This is rude behaviour. Open a topic by yourself about what you would would like to talk about, but do not use a popular topic for your own profit.</li>
      </ul>

      <ul>
        <li>Before you ask a question use a search engine. Do not expect anyone to serve you the answers, especially if they are easy to find. But do not do it if it is a personal question.</li>
      </ul>

      <ul>
        <li>>Adapt your language to the subculture you are joining. If you talk in a very high-pitched way in a casual forum, no one will take you seriously. Just as you should remain formal in a professional business forum.</li>
      </ul>

      <ul>
        <li>Ask permission before reposting any text. With a #followerpower or similar tag you can usually assume that the text can be reposted.</li>
      </ul>

      <ul>
        <li>Do not take screenshots of forum posts, posts, video conferences and share them with third parties (not even in a "private" chat) without first asking permission from all concerned.</li>
      </ul>

      <ul>
        <li>Do not participate in flamewars and shitstorms. Neither by posting or reacting to one.</li>
      </ul>

      <ul>
        <li>Make sure your posts are readable. Use proper punctuation. Also Do not (ab)use special characters for your sentence to look "cooler". This is important for all people who use a screenreader. Avoid too many special characters in your text such as / * : + # - remember this will also be read by a screenreader in most cases</li>
      </ul>

      <ul>
        <li>Speaking of screenreaders: If you add a picture to a post, use an alternative text to describe its contents, so someone who can not see also has a chance to grasp its context.</li>
      </ul>

      <ul>
       <li>Do not post information of others (also called doxxing) such as names, photos, contact information without explicit permission. Also keep in mind that a lot of countries have strict privacy laws.</li>
      </ul>

      <ul>
       <li>Do not publicly ask users for their name, age, gender, ethnicity, place of residence, religion, sexual orientation, political interest or even indirectly for skin color.  Personal information of other users are none of your business and they will tell them to you if there is any need to do so.</li>
      </ul>

      <ul>
        <li>In contexts where you are unsure about the used nick for someone or when unsure if all know that person's identity try to avoid such explicit markers.</li>
      </ul>

       <ul>
        <li>When discussing books, series, movies or games that others may not have read, seen or played, add the word "SPOILER" at the beginning of the sentence before telling story parts. Others should still be able to look forward to the content.</li>
      </ul>

       <ul>
        <li>Respect copyrighted material.</li>
      </ul>

       <ul>
        <li>Do not publicly archive content without permission. If the owner puts his content offline, respect that. Also, you may be violating copyright and privacy laws in some countries.</li>
      </ul>

       <ul>
        <li>Treat people as individuals. Do not write about to which group of people you do not want to talk to. This comes across as aggressive. </li>
      </ul>

       <ul>
        <li>Check if it is allowed to advertise on platforms before doing so. </li>
       </ul>

    </section>

    <!-- NEW SECTION BEGINNING HERE-->

  <section anchor="videoconferencing">
      <name>Videoconferences</name>
      <t>Video conferencing has become an integral part of our daily lives, so it's important that we use courtesies here as well.</t>
           
       <ul>
        <li>Do not record video or VoIP conferences without consent or permission. Violation of this rule is a criminal offense in some jurisdictions. </li>
       </ul>

      <ul>
        <li>If you are not speaking, mute yourself. </li>
       </ul>
 
      <ul>
        <li>Check your audio setup before entering conferences.</li>
       </ul>
 
      <ul>
        <li>Use a headset to avoid background noises.</li>
       </ul>
 
      <ul>
        <li>Respect if people Do not want to switch on their camera.</li>
       </ul>
 
      <ul>
        <li>If you have personal belongings in the background e. g. photos of your family or friends consider moving them away or blurring the video stream.</li>
       </ul>

      <ul>
        <li>If you are in two or more video conferences at the same time or you lurking around in a conference just in case someone shows up, make sure you mute one conference when you're joining another. Best would be you only join one conference at a time.</li>
       </ul>


      <ul>
        <li>Mute yourself when you sneeze, cough, burp. If you can not mute in time, apologize.</li>
       </ul>

</section>

    <!-- NEW SECTION BEGINNING HERE-->

  <section anchor="the-internet-use-in-general">
      <name>The Internet Use in General</name>
   <ul>
     <li>Do not use other people's voices or video files to create deepfakes, even if you do not intend to post them publicly. You do not know how responsibly the program and the AI behind it handles people's data. Always get permission first.</li>
   </ul>

   <ul>
     <li>If you post something in modeated places and it doesn't show up right away, wait and do not post it again. Some posts need to be approved first.</li>
   </ul>

   <ul>
    <li>Do not film or photograph people in distress (accident, argument, etc.) without permission. In many cultures, this is considered rude and illegal. Especially when you want to put it online afterwards. Always ask for permission.</li>
   </ul>

</section>

    <!-- NEW SECTION BEGINNING HERE-->
 

  <section anchor="admin-guidelines">
      <name>Admin Guidelines</name>
     

    <ul>
     <li>As an administrator and moderator you are a role model. Act like one.</li>
    </ul>

    <ul>
      <li>Check your websites privacy and security BEFORE you put it online.</li>
    </ul>

    <ul>
      <li>Provide contact information and check your mail regulary. </li>
    </ul>

    <ul>
      <li>Respond quickly to user concerns, especially when there is illegal content involved. </li>
    </ul>

    <ul>
      <li>Make sure that your privacy policy and your imprint (if required) are easy to understand and complete.</li>
    </ul>

    <ul>
      <li>Deliver on what you promise in the privacy policy.</li>
    </ul>

    <ul>
      <li>Remove personal user content, if your user asks for it. Observe the developments regarding data privacy laws in affected legislations and countries.</li>
    </ul>

    <ul>
      <li>Have a postmaster and a root alias address.</li>
    </ul>

    <ul>
      <li>Provide a security.txt in case security researchers find vulnerabilities in your system. </li>
    </ul>


    <ul>
      <li>Provide a robots.txt or/and adjust security settings against crawlers, if you provide personal information on your page.  </li>
    </ul>

    <ul>
      <li>Make sure you have an FAQ page, if necessary, and you update it frequently.  </li>
    </ul>


    <ul>
      <li>Have guidelines on how to deal with unlawful behaviour. Ensure consistent application of those rules.  </li>
    </ul>



    <ul>
      <li>Monitor your systems.</li>
    </ul>


    <ul>
      <li>Time passes quickly: What is current today can be outdated tomorrow. Ensure to date your articles, posts and other materials.Keep your documentation up-to-date. If you know information is out-of-date make sure to mark it as such or delete it. If someone is new to a topic or otherwise unfamiliar with specifics this may otherwise lead to people relying on those old information and thus making bad or even incorrect decisions based on it. In extreme cases this may even lead to security risks or even injury.</li>
    </ul>

    <ul>
      <li>When managing an community always act as just as possible and make your decisions transparent. Be impartial in your decisions and apply them equally in comparable situations.</li>
    </ul>

    <ul>
      <li>Last but not least: Treat users fair.</li>
    </ul>
</section>

    <section anchor="IANA">
    <!-- All drafts are required to have an IANA considerations section. See RFC 8126 for a guide.-->
      <name>IANA Considerations</name>
      <t>This memo includes no request to IANA.</t>
    </section>
    
    <section anchor="Security">
      <!-- All drafts are required to have a security considerations section. See RFC 3552 for a guide. -->
      <name>Security Considerations</name>
      <t>Security issues are not part of this memo.</t>
    </section>
    
    
    <!-- All drafts are required to have a security considerations section. See RFC 3552 for a guide. -->
  </middle>

  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.1855.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.0760.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.0791.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.8174.xml"/>
        <!-- The recommended and simplest way to include a well known reference -->
      </references>

    </references>
   

    <section anchor="Acknowledgements" numbered="false">
      <!-- [REPLACE/DELETE] an Acknowledgements section is optional -->
      <name>Acknowledgements</name>
      <t>I thank my beloved coffee machine for providing me with magic potion while writing.</t>
    </section>
    
 </back>
</rfc>
