Rules

Official Rules

The tufts.io archive is entirely open source. This makes it easy to maintain and changes inherently have accountability. However, it also gives anyone the power to change virtually anything about the site.

We believe that this tool can be incredibly useful and we hope that individuals will do right by the community. That being said, we reserve the right to make final decisions regarding conflicts. To help us make those decisions, here are some basic rules:

Examples:

  • /free-cookies -> nsfw-website.com
  • Changing a link’s destination with the intention to mislead (/facebook -> facebook.com, later edit to myspace.com once people start using it)

Proper procedure is to contact the listed author on the appropriate post (see all posts). If no valid author is listed, contact team@tufts.io

If we cannot contact you via the author information you provided (eg: bad email, disabled email, no email provided), we reserve the right to make final decisions about the link and whether it can change ownership

  • “Expired link”: link is no longer relevant. Examples: facebook event that has passed, project that is dead, destination link gives an error page
  • “Reasonable contact”: a reasonable attempt to contact the author was made

5. First come, first serve

If a link is taken, do not try to create a new link to replace it. Please be respectful of people who authored links before you.

Anyone may “hold” a link by creating a dummy destination, but it is only valid for a maximum of two weeks before someone else can claim it. This can be renewed by updating the date of the link. This rule does not apply to links owned by tufts.io or tufts staff.

7. NSFW content, malicious content, spam, malware, or intentionally hateful content are subject to removal and user bans

Be reasonable about this. Everything is open source and thus all links are public. If someone complains about a link and we believe it violates this rule, we will remove it.

Hopefully we will never have to do this, but due to the open nature of this tool, we find it necessary to include this rule