docs(twitter): add 27 new NOTimothyLottes threads (Jul 2026 Linux dev bringup)

Processed 38 URLs from the user's list. 1 was already in the corpus
(2072194202851549432). 9 were duplicates within the new batch (same
post IDs at different anchor URLs); removed those. This commit
contains the 27 unique new threads.

Content spans the Jul 2026 era and is mostly Lottes's Linux
development environment bringup work:
- 1674757854471806977: 'Nothing Oriented Programming' (NOP) philosophy
- 1990260050485797063: reversed projection matrices
- 2030722033286328426: STP conspiracy theory
- 2058166883044516181: 'crap-o-grammers' C++ bloat-ware critique
- 2060191401883619479: relevant timestamp article
- 2060730425929080874: CPU clock code (TSC)
- 2061123768429211767: no-debugger-debug + mmap log pre-history
- 2061416116694442141: Windows thread priority
- 2061933917137932437: mmap'd page file
- 2061937134756380682: Windows HIGHEST_PRIORITY_CLASS
- 2062031187023982879: back running 640x480 on VGA CRTs
- 2064858927829745887: on Linux now (SteamOS)
- 2065804972378243476: nanorc done + iPhone font issue
- 2065832746757341482: cross compilation up
- 2065872197147578751: @axelgneiting bypassing libc
- 2066184005632786736: Linux mlockall
- 2070337342854832468: why not pselect/ppoll/epoll_pwait2
- 2070734717825986566: deterrant to ALSA = parsing through snd_pcm_open
- 2071415096304193820: aplay to actually play a wave file
- 2071706805114216559: 'ALSA hell month continues'
- 2071937360288235902: Linux thread priority code
- 2072135292115427728: Linux doesn't allow priority increase by default
- 2072445315370590266: 'Wine workarounds - I could just detect'
- 2072506103401754653: snd_pcm_sw_params for ALSA
- 2072804183992922296: starting on WDM/KS audio for WIN32
- 2073096069529907441: re-trying WASAPI
- 2073110092447203466: CPP_(obj) for mmdeviceapi

Cleanup: removed 9 duplicate dirs (same posts at different anchor URLs),
script temp files, and the '1857803914604618029' which was already a
duplicate of '1857820858162753661' (mmap log canonical).

docs/twitter/2061416116694442141/thread.md

@@ -0,0 +1,31 @@
+---
+title: "Windows thread priority. SeIncreaseBasePriorityPrivilege required to play in the"
+author: "NOTimothyLottes"
+handle: "@NOTimothyLottes"
+post_url: "https://x.com/NOTimothyLottes/status/2061416116694442141"
+post_id: "2061416116694442141"
+timestamp: "2026-06-01 11:54:36"
+post_count: 4
+reply_count: 2
+repost_count: 0
+like_count: 10
+view_count: 1196
+---
+
+# @NOTimothyLottes — Windows thread priority. SeIncreaseBasePriorityPrivilege required to play in the
+
+## Post 1 (2026-06-01 11:54:36)
+
+Windows thread priority. SeIncreaseBasePriorityPrivilege required to play in the (fake)"Realtime" class -BUT- apparently there is AvSetMmThreadCharacteristics() for "Pro Audio" and AvSetMmThreadPriority() which can bring up priority into realtime. Curious if games using today?
+
+## Post 2 (2026-06-01 11:56:24) — reply to Post 1
+
+Either way NtSetInformationThread() seems to be the way to just set {1-15} (non-realtime class) priority directly without the silly clamp(priorityClassBase+threadPriority,1,15) business
+
+## Post 3 (2026-06-02 03:59:06) — reply to Post 1
+
+@NOTimothyLottes I don’t think your even suppose to change your thread’s priority in general anymore, it just messes with scheduling.
+
+## Post 4 (2026-06-02 10:32:37) — reply to Post 3
+
+@iamwhosiam Try using low latency pro audio tools and disabling the app’s authorization for high priority scheduling