docs(twitter): add 1591646625692553216 corpus (NOTimothyLottes self-modifying-binary update)

1-post thread, Nov 13 2022. 'My prefered method of managing application
data was the self-modifying-binary: (a.) on launch copy binary to
temp file, (b.) launch temp file, (c.) exit, (d.) now temp file
execution can freely modify origional binary.' Cleanest description
of his update/install pattern.

docs/twitter/1591646625692553216/thread.md

@@ -0,0 +1,19 @@
+---
+title: "My prefered method of managing application data was the 'self-modifying-binary':"
+author: "NOTimothyLottes"
+handle: "@NOTimothyLottes"
+post_url: "https://x.com/NOTimothyLottes/status/1591646625692553216"
+post_id: "1591646625692553216"
+timestamp: "2022-11-13 04:18:21"
+post_count: 1
+reply_count: 0
+repost_count: 0
+like_count: 0
+view_count: 0
+---
+
+# @NOTimothyLottes — My prefered method of managing application data was the 'self-modifying-binary':
+
+## Post 1 (2022-11-13 04:18:21)
+
+My prefered method of managing application data was the 'self-modifying-binary': (a.) on launch copy binary to temp file, (b.) launch temp file, (c.) exit, (d.) now temp file execution can freely modify origional binary :)

docs/twitter/1591646625692553216/thread_data.json

@@ -0,0 +1,22 @@
+{
+  "root_post_id": "1591646625692553216",
+  "posts": [
+    {
+      "post_id": "1591646625692553216",
+      "author": "NOTimothyLottes",
+      "handle": "NOTimothyLottes",
+      "text": "My prefered method of managing application data was the 'self-modifying-binary': (a.) on launch copy binary to temp file, (b.) launch temp file, (c.) exit, (d.) now temp file execution can freely modify origional binary :)",
+      "timestamp": "2022-11-13 04:18:21",
+      "media_urls": [],
+      "reply_to_id": null,
+      "quote_of_id": null,
+      "metrics": {
+        "reply_count": 0,
+        "repost_count": 0,
+        "like_count": 0,
+        "view_count": 0
+      }
+    }
+  ],
+  "source_url": "https://x.com/NOTimothyLottes/status/1591646625692553216"
+}