Editing Talk:99: Binary Heart
|
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| + | The heart pattern isn't symmetric, could the masked-out bits make a message? [[Special:Contributions/141.101.64.29|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. {{unsigned|LostFire}} | 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. {{unsigned|LostFire}} | ||
| Line 12: | Line 14: | ||
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? [[Special:Contributions/141.101.89.205|141.101.89.205]] 01:04, 18 May 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? [[Special:Contributions/141.101.89.205|141.101.89.205]] 01:04, 18 May 2014 (UTC) | ||
| − | This [http://www.binaryhexconverter.com/binary-to-ascii-text-converter Binary-to-Ascii converter | + | This [http://www.binaryhexconverter.com/binary-to-ascii-text-converter Binary-to-Ascii converter] tool can be used to decode the sequence to a string. --[[User:Pudder|Pudder]] ([[User talk: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 | 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 | ||
[[User:Atrix256|Atrix256]] ([[User talk:Atrix256|talk]]) 02:30, 25 January 2015 (UTC) | [[User:Atrix256|Atrix256]] ([[User talk:Atrix256|talk]]) 02:30, 25 January 2015 (UTC) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
