# 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/2ch3g6q
@lyse

> Maybe with the very simplest of the easy ones it might be still reasonably straight forward

I did that and the compiled bootloader is now 439 bytes in size – the available space is 440 bytes. So, phew, it *just* fits now. 😂
@lyse

> Maybe with the very simplest of the easy ones it might be still reasonably straight forward

I did that and the compiled bootloader is now 439 bytes in size – the available space is 440 bytes. So, phew, it *just* fits now. 😂
@lyse

> Maybe with the very simplest of the easy ones it might be still reasonably straight forward

I did that and the compiled bootloader is now 439 bytes in size – the available space is 440 bytes. So, phew, it *just* fits now. 😂
@lyse

> Maybe with the very simplest of the easy ones it might be still reasonably straight forward

I did that and the compiled bootloader is now 439 bytes in size – the available space is 440 bytes. So, phew, it *just* fits now. 😂
(Those 440 bytes include the BIOS Parameter Block, which can’t be used for code. The available space for the code is just 378 bytes. There’s really not a lot going on here other than loading the kernel into memory, or some second stage of a bootloader, and then executing that.)
(Those 440 bytes include the BIOS Parameter Block, which can’t be used for code. The available space for the code is just 378 bytes. There’s really not a lot going on here other than loading the kernel into memory, or some second stage of a bootloader, and then executing that.)
(Those 440 bytes include the BIOS Parameter Block, which can’t be used for code. The available space for the code is just 378 bytes. There’s really not a lot going on here other than loading the kernel into memory, or some second stage of a bootloader, and then executing that.)
(Those 440 bytes include the BIOS Parameter Block, which can’t be used for code. The available space for the code is just 378 bytes. There’s really not a lot going on here other than loading the kernel into memory, or some second stage of a bootloader, and then executing that.)
@movq Yeah, that's not a lot.