{
  "root_post_id": "1688022114962374656",
  "posts": [
    {
      "post_id": "1688018382543597568",
      "author": "NOTimothyLottes",
      "handle": "NOTimothyLottes",
      "text": "1st SPC project: to be based on vintage 640x480 render (VGA style), +fallback to 640x240 for 15 KHz arcade CRTs (PGM-esk), and CRT shader scaling on Deck and OLED/LCD. Use mix of render pixel aspect changes, running less than 480 lines, and letter-box to keep integer Y scaling.",
      "timestamp": "2023-08-06 02:45:18",
      "media_urls": [
        "https://pbs.twimg.com/media/F20LgFtWQAAMtcv?format=png&name=orig"
      ],
      "reply_to_id": null,
      "quote_of_id": null,
      "metrics": {
        "reply_count": 1,
        "repost_count": 0,
        "like_count": 3,
        "view_count": 708
      }
    },
    {
      "post_id": "1688019698904969216",
      "author": "NOTimothyLottes",
      "handle": "NOTimothyLottes",
      "text": "My 15 KHz CRT output path when docked is HD Fury Nano (won't do <480p) doing HDMI to VGA, with a sync combiner (to workaround GBS-C bug), into GBS-C which line drops 480p ~60Hz to 240p ~60Hz and outputs component. The 640 width gets maintained even if some CRTs cannot resolve it.",
      "timestamp": "2023-08-06 02:50:32",
      "media_urls": [],
      "reply_to_id": "1688018382543597568",
      "quote_of_id": null,
      "metrics": {
        "reply_count": 1,
        "repost_count": 0,
        "like_count": 0,
        "view_count": 188
      }
    },
    {
      "post_id": "1688021533904510976",
      "author": "NOTimothyLottes",
      "handle": "NOTimothyLottes",
      "text": "Presents issues for UI, namely that my bitmap fonts need to look good in both 480p and 240p modes, so for editor (assembler) I'm going with a font that uses right angles and designed around 2x2 stroke width, in a 8x16 (pow2) bitmap, so 640x240p still gets a readable 8x8 (below)",
      "timestamp": "2023-08-06 02:57:50",
      "media_urls": [
        "https://pbs.twimg.com/media/F20Ogh8XoAAq7hR?format=png&name=orig"
      ],
      "reply_to_id": "1688019698904969216",
      "quote_of_id": null,
      "metrics": {
        "reply_count": 1,
        "repost_count": 0,
        "like_count": 1,
        "view_count": 439
      }
    },
    {
      "post_id": "1688022114962374656",
      "author": "NOTimothyLottes",
      "handle": "NOTimothyLottes",
      "text": "The next challenge is overscan safety, since real non-VGA CRTs will be used in development. The Y axis has an easy fix, simply keep cursor pinned in the 'safe' zone, but still print lines in the overscan area (so they can be seen when attached to non-overscan CRTs/etc too).",
      "timestamp": "2023-08-06 03:00:08",
      "media_urls": [],
      "reply_to_id": "1688021533904510976",
      "quote_of_id": null,
      "metrics": {
        "reply_count": 0,
        "repost_count": 0,
        "like_count": 1,
        "view_count": 340
      }
    }
  ],
  "source_url": "https://x.com/NOTimothyLottes/status/1688022114962374656"
}