# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 9
# self = https://watcher.sour.is/conv/d6xdvyq
@lyse Ah, thanks for letting me know about the typo. 😅

“PM” stands for “Presentation Manager” and is/was common prefix for graphical OS/2 programs. The PM actually got replaced by the “Workplace Shell” in version 2.0, but somehow the PM prefix kept being used. At least that is how I remember it. 🥴

Hmm, right, an “Abort” button. That could be useful. In my tests, the scans always finished so quickly that I didn’t even think about this … 😅
@lyse Ah, thanks for letting me know about the typo. 😅

“PM” stands for “Presentation Manager” and is/was common prefix for graphical OS/2 programs. The PM actually got replaced by the “Workplace Shell” in version 2.0, but somehow the PM prefix kept being used. At least that is how I remember it. 🥴

Hmm, right, an “Abort” button. That could be useful. In my tests, the scans always finished so quickly that I didn’t even think about this … 😅
@lyse Ah, thanks for letting me know about the typo. 😅

“PM” stands for “Presentation Manager” and is/was common prefix for graphical OS/2 programs. The PM actually got replaced by the “Workplace Shell” in version 2.0, but somehow the PM prefix kept being used. At least that is how I remember it. 🥴

Hmm, right, an “Abort” button. That could be useful. In my tests, the scans always finished so quickly that I didn’t even think about this … 😅
As for aborting: Just closing the window works. 🤔 The main thread receives the message from the windowing system and ends the entire process. Still, it might be worth investigating this further, because it could teach me some more about communication between threads. 🤔 (For this case, I could just set a flag in a volatile int. But maybe there’s something more interesting available! 🥁)
As for aborting: Just closing the window works. 🤔 The main thread receives the message from the windowing system and ends the entire process. Still, it might be worth investigating this further, because it could teach me some more about communication between threads. 🤔 (For this case, I could just set a flag in a volatile int. But maybe there’s something more interesting available! 🥁)
As for aborting: Just closing the window works. 🤔 The main thread receives the message from the windowing system and ends the entire process. Still, it might be worth investigating this further, because it could teach me some more about communication between threads. 🤔 (For this case, I could just set a flag in a volatile int. But maybe there’s something more interesting available! 🥁)
Looks like there’s not a lot of fancy magical stuff:

- https://komh.github.io/os2books/progfaq/112_L2_Whatisthebestwaytoco.html
- https://komh.github.io/os2books/progfaq/111_L2_Whatisthebestwaytoco.html

There is, however, a DosKillThread() function, which, as far as I know, does not exist on POSIX. 🤔 You can only send a signal to a POSIX thread and then it’ll hopefully end some day, right?

Killing threads is probably a bad idea, though. Who knows which state it’ll leave behind. It’s not like a process which will be properly cleaned up by the OS.

I think I’ll leave it as is. 🙂
Looks like there’s not a lot of fancy magical stuff:

- https://komh.github.io/os2books/progfaq/112_L2_Whatisthebestwaytoco.html
- https://komh.github.io/os2books/progfaq/111_L2_Whatisthebestwaytoco.html

There is, however, a DosKillThread() function, which, as far as I know, does not exist on POSIX. 🤔 You can only send a signal to a POSIX thread and then it’ll hopefully end some day, right?

Killing threads is probably a bad idea, though. Who knows which state it’ll leave behind. It’s not like a process which will be properly cleaned up by the OS.

I think I’ll leave it as is. 🙂
Looks like there’s not a lot of fancy magical stuff:

- https://komh.github.io/os2books/progfaq/112_L2_Whatisthebestwaytoco.html
- https://komh.github.io/os2books/progfaq/111_L2_Whatisthebestwaytoco.html

There is, however, a DosKillThread() function, which, as far as I know, does not exist on POSIX. 🤔 You can only send a signal to a POSIX thread and then it’ll hopefully end some day, right?

Killing threads is probably a bad idea, though. Who knows which state it’ll leave behind. It’s not like a process which will be properly cleaned up by the OS.

I think I’ll leave it as is. 🙂