I've been doing a couple of tests and the second part apparently has something to do with the first. Let's use my second MD5 hash (d0fc2939c777e488f630b074199e6fcf) for the following example. If we were to use another IP, i.e. www.valvesoftware.com (69.28.175.118), generated an MD5 hash from it...
Yeah, the first 32 characters is an MD5 hash of your IP. The other 32 are unknown. The weird thing is that it doesn't just accept any random string for the next 32 characters. For example, here's one of my UIDs:
c0bfe170ddc59b73110e1f87c7108764d0fc2939c777e488f630b074199e6fcf
My current IP is...
The main problem is simply deciphering the other hidden messages and/or clues (if they exist or couse), then we'd have to figure out where to use them. So far we've tinkered with the SWF to wits' end when it comes to its functionality. Then we have the PHP file which unfortunately is impossible...
That's what you get for living in the future. :P
[e] I found something else:
The first hash is in fact your IP. Not very useful I know, but it's something.
Seems like my anagram theory went bust; none of these make sense. What's odd is that it was the first URL that showed up in Google when looking for "the cake is a lie," though.
From what I can tell the UID is made up of two MD5 hashes (two 32 character strings). The first one is always the same, e3c11ce7d3288d99dff0d164ccf66135 and the other one is random, maybe generated from a timestamp in seconds, Unix time even.