Event JSON
{
"id": "d4b43b730951f010c548a7b9eed83cb67edff71a565024cd1389d6dc41dd7a0f",
"pubkey": "47f54409a4620eb35208a3bc1b53555bf3d0656b246bf0471a93208e20672f6f",
"created_at": 1710159790,
"kind": 1,
"tags": [
[
"t",
"retrocomputing"
],
[
"t",
"retrogaming"
],
[
"t",
"computer"
],
[
"t",
"16bit"
],
[
"t",
"8bit"
],
[
"t",
"gamedev"
],
[
"t",
"1980s"
],
[
"t",
"1990s"
],
[
"t",
"graphics"
],
[
"proxy",
"https://graphics.social/users/metin/statuses/112077032027088605",
"activitypub"
]
],
"content": "When I was a 16-bit game graphics creator, I got accustomed to thinking in multiples of 16, for sprite dimensions, game scenery patterns, image resolutions, RGB color values and more.\n\nThat became a lasting habit. Even now, long after thinking in multiples of 16 was necessary, I'm still entering 16, 32, 48, 64, et cetera, when numerical input is required. Does anyone happen to recognize this? 🙂\n\n#RetroComputing #RetroGaming #computer #16bit #8bit #GameDev #1980s #1990s #graphics\n\nhttps://cdn.masto.host/graphicssocial/media_attachments/files/112/076/981/254/189/718/original/4198a216dea07cfa.png",
"sig": "5556ba80f31c4f4f8b9758e2f1cf3627ab51869d1b50fbbff5c4fc0742c9e412e12b1d549ed0ece520d95c3f03dc70e1c582cfa5c0351b72796cc0a386557c6b"
}
