# Talk:99: Binary Heart

The heart pattern isn't symmetric, could the masked-out bits make a message? 141.101.64.29 17:11, 2 February 2015 (UTC)

The l's and 0's in the binary translation make the code: 10101010011010010, which if you remove either the first or the last digit and convert to text make either, ªi OR TÒ which isn't very helpful. -- ‎LostFire (talk) (please sign your comments with ~~~~)

10101010011010010 in hexadecimal is 154D2 which could mean "I'm sad too". Noit (talk) 00:34, 27 September 2013 (UTC)

I wondered why he didn't include space characters, but then I realized that ASCII 32 makes for too much white space (only one bit is set) which might spoil the random appearance of the background. Also, shouldn't there be a Doctor Who reference in there somewhere? Just saying... 108.162.219.58 18:28, 24 January 2014 (UTC)

This may be part of the reason for 'O' as well; 'o' only has 2 unset bits. ('O' is '01001111', 'o' is '01101111'). 199.27.128.181 23:55, 21 January 2015 (UTC)

Maybe the mixture of o's and O's is only there so that the sequence of bits doesn't contain a single repeating sequence. 108.162.216.84 20:47, 8 March 2014 (UTC)

On the 'o's and 'O's - Converting 011001110010111 from binary to decimal gives 13207. Googling that number only gives hits about Syracuse. Does anyone know if there's a connection there? 141.101.89.205 01:04, 18 May 2014 (UTC)

This Binary-to-Ascii converter tool can be used to decode the sequence to a string. --Pudder (talk) 12:23, 18 December 2014 (UTC)

Some of the o's in love are capitalized and some of the o's in you are capitalized but no other letter in any other position has mixed capitalization. If you take a lower case o to be a 0 and a capital o to be a 1, that gives you the string of binary digits: 011001110010111. Unfortunately that is 15 bits, not 16 so not quite enough for two letters, but apparently the first 8 bits are "g". If we append a 0 to the last 7 bits, it becomes "g.", if we use a 1 it becomes "g/". Neither seems likely to be anything that i can tell. in hex, those 15 digits become 0x3397. Appending a 0 it's 0x672E and appending a 1 it's 0x672F. Negating the bits (in case 1's and 0's were reversed) didn't seem to help either unfortunately. I think there is more to the o and O's but not sure what it is :P Atrix256 (talk) 02:30, 25 January 2015 (UTC)