This article is just an expression of an opinion Full Metal Lion
developed over his time on the Island. It is not an official policy or endorsed by any moderator or admin.1)2)3)4)5)6)
(Not to be confused with inclusionism
, the philosophy that the wiki should have lots of pages on many topics)
Enclusionism is a
doctrine guideline conjecture play on words philosophyn opinion that states that if an Islandy resource7) can be hosted on the Improbable Island servers, then it probably should be. For the average player trying to manage resources, this translates to putting lots of things into the Enquirer, especially the Wiki of Lies or the Gallery of Shame.8)
The core reasoning behind enclusionism is that things which are not hosted on the Island's servers tend to be lost with time. The Island has been around since 2008, which makes it old in Internet years. The Island has outlasted a surprisingly large amount of websites. Of course, you have the cases where a player sets up a website to host some Island-related resources and the domain name lapses9) after a couple of years as the player loses interest10)11)12), but the Island also outlasted userscripts.org, which was a real website that had millions of visits per month.13)
Even if a website doesn't stop existing, it might delete or move the data, or the Island community might forget where to find it14)15) It's hard to tell whether the Island will outlast a given website or vice versa, but we have pretty good odds on the prediction that the Island will not outlast itself,16) ergo the Island's servers are a good place to store things to prevent them from being lost.
One must be smart in the application of this principle, though. For instance, not all parts of the server are created equal: it's easier to find things in the wiki than the forum; the bio of a character is probably not a great place to put permanent, publicly interesting information not about that character; and /dev/null is not a good place to store things at all. Keeping a copy of encluded information on your own hard drive may also prove to be useful!
Furthermore, enclusion should usually be nondestructive. If you'll examine the examples below, you'll find that the ones that were encluded from somewhere else have a link to that original place. One should try to get the permission of the person who created the resource one is encluding, if possible.17) However, if the unencluded resource can be locked, with directions to edit the version on the wiki, this might reduce redundancy. Additionally, if every agrees that the old resource can be destroyed safely after enclusion, and there are no very important links pointing to the old resource, then destroying the unencluded resource could save some space on a hard drive somewhere, or reduce redundancy. Backups are important, but they don't usually have to be public.
Obvious examples of this philosophy in practice can be found at the wiki pages Loaders, Titan Hunting, the Greasemonkey namespace and Lions. More subtle examples can be found in, say, the text color list.