# 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 10
# self = https://watcher.sour.is/conv/kkeojlq
@lyse Yeah, what else does one need? šŸ˜…

I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:



That is pretty cool. šŸ˜Ž

Itā€™s still a ā€œnaiveā€ assembler. There are zero optimizations and it canā€™t do macros (so I had to resort to using cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. šŸ„“ I avoided that for now by removing some cosmetic output from the bootloader.
@lyse Yeah, what else does one need? šŸ˜…

I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:



That is pretty cool. šŸ˜Ž

Itā€™s still a ā€œnaiveā€ assembler. There are zero optimizations and it canā€™t do macros (so I had to resort to using cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. šŸ„“ I avoided that for now by removing some cosmetic output from the bootloader.
@lyse Yeah, what else does one need? šŸ˜…

I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:



That is pretty cool. šŸ˜Ž

Itā€™s still a ā€œnaiveā€ assembler. There are zero optimizations and it canā€™t do macros (so I had to resort to using cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. šŸ„“ I avoided that for now by removing some cosmetic output from the bootloader.
@lyse Yeah, what else does one need? šŸ˜…

I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:



That is pretty cool. šŸ˜Ž

Itā€™s still a ā€œnaiveā€ assembler. There are zero optimizations and it canā€™t do macros (so I had to resort to using cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. šŸ„“ I avoided that for now by removing some cosmetic output from the bootloader.
@movq my friend, I'm curious what is that interface? It's like WindowMaker meets dwm, meets...? :D
@eldersnake Pretty much. šŸ˜‚ Itā€™s all the stuff tagged as ā€œDesktopEnvā€ here: https://www.uninformativ.de/git/ The WM was written from scratch as a learning project, although it feels very similar to dwm, yes.
@eldersnake Pretty much. šŸ˜‚ Itā€™s all the stuff tagged as ā€œDesktopEnvā€ here: https://www.uninformativ.de/git/ The WM was written from scratch as a learning project, although it feels very similar to dwm, yes.
@eldersnake Pretty much. šŸ˜‚ Itā€™s all the stuff tagged as ā€œDesktopEnvā€ here: https://www.uninformativ.de/git/ The WM was written from scratch as a learning project, although it feels very similar to dwm, yes.
@eldersnake Pretty much. šŸ˜‚ Itā€™s all the stuff tagged as ā€œDesktopEnvā€ here: https://www.uninformativ.de/git/ The WM was written from scratch as a learning project, although it feels very similar to dwm, yes.
@movq ha, very cool!