Die FAQ zur MAUS Freiburg

Andere wichtige FAQs und Hinweise


RFC 1855 - eine Netiquette



Information Services (Gopher, Wais, WWW, ftp, telnet)
- Make clear what's available for copying and what is not.
- Describe what's available on your site, and your organization. Be
sure any general policies are clear.
- Keep information, especially READMEs, up-to-date. Provide READMEs
in plain ascii text.
- Present a list of mirrors of your site if you know them. Make
sure you include a statement of copyright applicable to your mirrors.
List their update schedule if possible.
- Make sure that popular (and massive) information has the
bandwidth to support it.
- Use conventions for file extensions - .txt for ascii text; .html
or .htm for HTML; .ps for Postscript; .pdf for Portable Document
Format; .sgml or .sgm for SGML; .exe for non-Unix executables, etc.
- For files being transferred, try to make filenames unique in the
first eight characters.
- When providing information, make sure your site has something
unique to offer. Avoid bringing up an information service which simply
points to other services on the Internet.
- Don't point to other sites without asking first.
- Remember that setting up an information service is more than just
design and implementation. It's also maintenance.
- Make sure your posted materials are appropriate for the
supporting organization.
- Test applications with a variety of tools. Don't assume
everything works if you've tested with only one client. Also, assume
the low end of technology for clients and don't create applications
which can only be used by Graphical User Interfaces.
- Have a consistent view of your information. Make sure the look
and feel stays the same throughout your applications.
- Be sensitive to the longevity of your information. Be sure to
date time-sensitive materials, and be vigilant about keeping this
information well maintained.
- Export restrictions vary from country to country. Be sure you
understand the implications of export restrictions when you post.
- Tell users what you plan to do with any information you collect,
such as WWW feedback. You need to warn people if you plan to publish
any of their statements, even passively by just making it available to
other users.
- Make sure your policy on user information services, such as
homepages, is well known.