# 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 238023
# self = https://watcher.sour.is?offset=227236
# next = https://watcher.sour.is?offset=227336
# prev = https://watcher.sour.is?offset=227136
been having fun updating my dotfiles repo as if i have anything notable to put in there
customized the shit out of my desktop with catppuccin themes earlier today. mostly out of boredom. but it's really cute i love catppuccin
customized the shit out of my desktop with catppuccin themes earlier today. mostly out of boredom. but it's really cute i love catppuccin
@prologic this is so fucking real i'm so sick of AI/LLM crap
@prologic this is so fucking real i'm so sick of AI/LLM crap
happy new year to anyone who sees this <3
happy new year to anyone who sees this <3
2024 was okay for me, but 2025 is gonna be real shit. 😂 So much annoying stuff coming up. Gotta enjoy the moment, who knows how long it will last. 😅

Happy new year, you guys. 🥳
2024 was okay for me, but 2025 is gonna be real shit. 😂 So much annoying stuff coming up. Gotta enjoy the moment, who knows how long it will last. 😅

Happy new year, you guys. 🥳
2024 was okay for me, but 2025 is gonna be real shit. 😂 So much annoying stuff coming up. Gotta enjoy the moment, who knows how long it will last. 😅

Happy new year, you guys. 🥳
2024 was okay for me, but 2025 is gonna be real shit. 😂 So much annoying stuff coming up. Gotta enjoy the moment, who knows how long it will last. 😅

Happy new year, you guys. 🥳
@prologic Yes, it’s all written from scratch, *but* most of it is written in C (not Assembler) and having a C standard library available helps a lot. It’s not that different from writing a program for DOS, just the syscalls are different. 😅

@lyse Scrolling the viewport was the most annoying part. 🥴 The code also assumes that it is running on a “fast” PC. There are no “elaborate” data structures like a gap buffer. (But it does use dynamic arrays, which Wikipedia lists as a special case of a gap buffer. 🤔)

To display text on the screen, the editor writes directly to video memory (https://wiki.osdev.org/Printing_To_Screen). This is a blessing and much easier than fiddling with escape sequences. I wish you could do something like that on a Linux terminal.
@prologic Yes, it’s all written from scratch, *but* most of it is written in C (not Assembler) and having a C standard library available helps a lot. It’s not that different from writing a program for DOS, just the syscalls are different. 😅

@lyse Scrolling the viewport was the most annoying part. 🥴 The code also assumes that it is running on a “fast” PC. There are no “elaborate” data structures like a gap buffer. (But it does use dynamic arrays, which Wikipedia lists as a special case of a gap buffer. 🤔)

To display text on the screen, the editor writes directly to video memory (https://wiki.osdev.org/Printing_To_Screen). This is a blessing and much easier than fiddling with escape sequences. I wish you could do something like that on a Linux terminal.
@prologic Yes, it’s all written from scratch, *but* most of it is written in C (not Assembler) and having a C standard library available helps a lot. It’s not that different from writing a program for DOS, just the syscalls are different. 😅

@lyse Scrolling the viewport was the most annoying part. 🥴 The code also assumes that it is running on a “fast” PC. There are no “elaborate” data structures like a gap buffer. (But it does use dynamic arrays, which Wikipedia lists as a special case of a gap buffer. 🤔)

To display text on the screen, the editor writes directly to video memory (https://wiki.osdev.org/Printing_To_Screen). This is a blessing and much easier than fiddling with escape sequences. I wish you could do something like that on a Linux terminal.
@prologic Yes, it’s all written from scratch, *but* most of it is written in C (not Assembler) and having a C standard library available helps a lot. It’s not that different from writing a program for DOS, just the syscalls are different. 😅

@lyse Scrolling the viewport was the most annoying part. 🥴 The code also assumes that it is running on a “fast” PC. There are no “elaborate” data structures like a gap buffer. (But it does use dynamic arrays, which Wikipedia lists as a special case of a gap buffer. 🤔)

To display text on the screen, the editor writes directly to video memory (https://wiki.osdev.org/Printing_To_Screen). This is a blessing and much easier than fiddling with escape sequences. I wish you could do something like that on a Linux terminal.
@ oh shit that worked
@ oh shit that worked
image upload test. have a wonyoung
wonyoung icon
image upload test. have a wonyoung
wonyoung icon
wanna play with CLI stuff or host something new... maybe play with that charmbracelet git server but i don't need that lol
wanna play with CLI stuff or host something new... maybe play with that charmbracelet git server but i don't need that lol
@ this is lonely!
@ this is lonely!
well it's just me here. any friends wanna join
well it's just me here. any friends wanna join
another cli test for icons this time
another cli test for icons this time
STUPID ASS BASE URL STUFF FUCKED UP ICONS but we're good now yayyy
STUPID ASS BASE URL STUFF FUCKED UP ICONS but we're good now yayyy
@ god damn it
@ god damn it
pleaseeeeeeee work
pleaseeeeeeee work
cli test 3
cli test 3
@ god damn it why aren't icons working
@ god damn it why aren't icons working
cli test 2
cli test 2
cli test
cli test
@kat testttt
@kat testttt
testttt
testttt
[47°09′31″S, 126°43′58″W] Raw reading: 0x6774D9E1, offset +/-5
@aelaraji Happy New Year to you too! 🥳
@aelaraji Happy New Year to you too! 🥳
@news fuck
@news fuck
hm is this working
hm is this working
test
test
test
test
test test test
test test test
Ok, amma start twting from my timeline instance, let me know if I break something xD
Pretty much sums it up 🤦‍♂️ it's shit 💩
Pretty much sums it up 🤦‍♂️ it's shit 💩
Happy New-new year I guess 👋😁
"Plez give me all the compute, money, and copyright allowance and i give you shitty autocomplete for fee!" - Tech Bro.
"Plez give me all the compute, money, and copyright allowance and i give you shitty autocomplete for fee!" - Tech Bro.
@bender OP didn't explain it well enough? 🤔
@bender OP didn't explain it well enough? 🤔
Fuck me OpenAI sucks ass. ChatGPT has to be the most stupidest fucking thing ever invented. It is so bad it's not even funny.
Fuck me OpenAI sucks ass. ChatGPT has to be the most stupidest fucking thing ever invented. It is so bad it's not even funny.
@prologic what this refers about? What did you do?
Success! 🥳 https://prologic.dev/ is now off (_temporarily for now_) Clownflare! 🤣
Success! 🥳 https://prologic.dev/ is now off (_temporarily for now_) Clownflare! 🤣
Finally spending the time/effort today (_on my day off_) to see if I can get a working prototype and proof-of-concept self-hosted alternative to Clownflare going. Components I'm using so far are: Alpine Linux (_may swap this out for µLInux at some point_), Wireguard, Caddy.
Finally spending the time/effort today (_on my day off_) to see if I can get a working prototype and proof-of-concept self-hosted alternative to Clownflare going. Components I'm using so far are: Alpine Linux (_may swap this out for µLInux at some point_), Wireguard, Caddy.
🧮 USERS:1 FEEDS:2 TWTS:1201 ARCHIVED:83066 CACHE:2647 FOLLOWERS:17 FOLLOWING:14
Whoops, this of course should have read "other than _on_ the last three days". Yeah, people give a fuck, @movq. And police doesn't care either. https://de.wikipedia.org/wiki/Feuerwerk#Bundesrepublik_Deutschland_(Gegenwart)
@movq Wow, quite an elaborate editor you've programmed there!
Oh wow! 🤩 So many 'ol users have come out of the woodwork 🤣 Great to see you again @oevl and @ionores
Oh wow! 🤩 So many 'ol users have come out of the woodwork 🤣 Great to see you again @oevl and @ionores
@movq Holy moly! 😱 You've written all the userland tools for your Toy OS too right? 🤔
@movq Holy moly! 😱 You've written all the userland tools for your Toy OS too right? 🤔
Healthy new world war!
Whoohoo! 💪 Last night I added support for SSH Agent Forwarding to sshbox that now enables me to use it as an SSH Reverse Proxy to a private SSH service. I can now use this to front my Gitea's SSH service 👌 (_without exposing my infra behind the proxy or the IP addresses_).
Whoohoo! 💪 Last night I added support for SSH Agent Forwarding to sshbox that now enables me to use it as an SSH Reverse Proxy to a private SSH service. I can now use this to front my Gitea's SSH service 👌 (_without exposing my infra behind the proxy or the IP addresses_).
Bright New Year!
@movq the sound of the disk drive brought back so many memories! (second time I type this, first time the reply seemed to go through, just to find myself logged out 🤯).
@aelaraji I would agree 2024 wasn’t a good year for our family either. While I understand every year doesn’t need to positively excel, one can only hope, right? 2024 went out of the way to be bad.

I am truly happy to have met such amazing people through this “simple” medium. Thank you all for bearing with me, and my often outspoken, borderline “assholery”, attitude. I am working on it, be assured.

See you all next year!
Good riddance 2024...
2025, be good or else.

Happy new year Twtxt people. I'm grateful for getting to meet/talk to you all, It certainly was the best thing to have happened to me in this "2024" chapter of my life.
Good riddance 2024...
2025, be good or else.

Happy new year Twtxt people. I'm grateful for getting to meet/talk to you all, It certainly was the best thing to have happened to me in this "2024" chapter of my life.
Good riddance 2024...
2025, be good or else.

Happy new year Twtxt people. I'm grateful for getting to meet/talk to you all, It certainly was the best thing to have happened to me in this "2024" chapter of my life.
[47°09′57″S, 126°43′48″W] 4275 days without news from Herve
I think best browser for Gopher is Blue skies
A take on an Elton John classic https://youtube.com/watch?v=DB4g1qTuHq4&si=bJeipKJbAQGh-O9r
@prologic Happy New Year!
@andros Happy New Year! I am still 6 hours in the past
@prologic Happy new year! 😃
@prologic Happy new year! 😃
@prologic Happy new year! 😃
@prologic Happy new year! 😃
Okay, this is pretty cool. My 8086 toy OS running on my old Pentium from an actual floppy disk. 😍 I just love that sound and the *feeling* of using floppies. This brings back so many memories from my early DOS days.

The cp-unopt program copies a file and intentionally uses small unaligned reads/writes (hopefully triggers more bugs).

The I/O cache works “okay-ish”, I guess. When sha1 runs, it has to do a few reads for the first file and basically none for the second one. Both could have been served entirely from the cache, theoretically. (But even just having an I/O cache in the first place speeds up things dramatically.)

Notice how there’s an EA file. That’s a left-over from OS/2, because I copied some files to the floppy using OS/2. In other words, my FAT12 implementation survives OS/2 writing to it. 🥳 (But I guess it should show up as EA DATA.SF. My current code starts at the left and stops at the first space.)

https://movq.de/v/d4d50d3c74/los86-on-p133-from-floppy-small2.mp4
Okay, this is pretty cool. My 8086 toy OS running on my old Pentium from an actual floppy disk. 😍 I just love that sound and the *feeling* of using floppies. This brings back so many memories from my early DOS days.

The cp-unopt program copies a file and intentionally uses small unaligned reads/writes (hopefully triggers more bugs).

The I/O cache works “okay-ish”, I guess. When sha1 runs, it has to do a few reads for the first file and basically none for the second one. Both could have been served entirely from the cache, theoretically. (But even just having an I/O cache in the first place speeds up things dramatically.)

Notice how there’s an EA file. That’s a left-over from OS/2, because I copied some files to the floppy using OS/2. In other words, my FAT12 implementation survives OS/2 writing to it. 🥳 (But I guess it should show up as EA DATA.SF. My current code starts at the left and stops at the first space.)

https://movq.de/v/d4d50d3c74/los86-on-p133-from-floppy-small2.mp4