Memcache Mystery


Every time I go back and try new commands on, I check to see if the LIST command is different…and I’m always reminded that there are three ‘memcache’ items on the list that (as far as I can tell) nobody has been able to access.

It’s been slowly eating at me ever since we first got access to the terminal, and more recently with all of the talk of Emily possibly being loop16. This entry in particular bothers me…


If Emily really is loop16 (or associated with it in some way), then reading the memory cache of the loop16 process would potentially be very informative. It could give us some real insight into the nature of loop16, and possibly Emily herself.

I’m sure everyone has already tried every command (or combination of commands) they can think of, but I have a hard time believing this is simply a dead end.


I’m guessing we’ll need the “full documentation” mentioned in the ‘help’ command to figure out what we’re missing


You do realize that we are all “memcache” too! A memcache is a general-purpose distributed memory caching system. It is often used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce the number of times an external data source (such as a database or API) must be read.

We are distributed around the world, we are used to speed up dynamic database(ARG)-driven website (ARG content) by caching data and objects (ARG content) in RAM (our brains) to reduce the “number of times and external data source must be read.” (reiterations of theories and solutions of content)! -)



Arhh!!! Where’s my tin foil!!!