# 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 238500
# self = https://watcher.sour.is?offset=227069
# next = https://watcher.sour.is?offset=227169
# prev = https://watcher.sour.is?offset=226969
@movq pretty neat! Keep going, keep going!
Well, they could render inline. Will still need some authorisation from the pod operator.
@ if you use markdown when posting the cat images, they will render inline on any Yarn pod.
Made a little text editor for my 8086 toy operating system today. It can’t do much, but it allows for some basic editing. 💾
That was probably the last “big” thing I did for that OS in the near future. Vacation is coming to an end.
https://movq.de/v/bb8c2b62a5/edit.mp4
Made a little text editor for my 8086 toy operating system today. It can’t do much, but it allows for some basic editing. 💾
That was probably the last “big” thing I did for that OS in the near future. Vacation is coming to an end.
https://movq.de/v/bb8c2b62a5/edit.mp4
Made a little text editor for my 8086 toy operating system today. It can’t do much, but it allows for some basic editing. 💾
That was probably the last “big” thing I did for that OS in the near future. Vacation is coming to an end.
https://movq.de/v/bb8c2b62a5/edit.mp4
Made a little text editor for my 8086 toy operating system today. It can’t do much, but it allows for some basic editing. 💾
That was probably the last “big” thing I did for that OS in the near future. Vacation is coming to an end.
https://movq.de/v/bb8c2b62a5/edit.mp4
[47°09′29″S, 126°43′03″W] Wind speed: 65kph
Are there any good Registry? I like to check the mentions.
Are there any good Registry? I like to check the mentions.
Are there any good Registry? I like to check the mentions.
My cat, @terron has his own twtxt account. Would you follow him? #catsoftwtxt
My cat, @terron has his own twtxt account. Would you follow him? #catsoftwtxt
My cat, @terron has his own twtxt account. Would you follow him? #catsoftwtxt
Durmiendo con mi primate favorito
#catsoftwtxt
Durmiendo con mi primate favorito
#catsoftwtxt
[47°09′40″S, 126°43′13″W] Wind speed: 73kph -- batteries low
@movq Beautiful! Well, today is also a rather foggy gray soup here.
@movq No, that was a wide open field, absolutely nowhere to hide. I reckon it was just a very brave individual. We somehow managed to radiate a sense of calm. :-) It might have been the same heron I saw the other days a few hundred meters west.
[47°09′30″S, 126°43′18″W] Working impossible due to heavy rain
Fucking hell I hate this said ZScaler shit! 💩
Fucking hell I hate this said ZScaler shit! 💩
[47°09′27″S, 126°43′42″W] Working impossible due to blizzard
I really don't get it tbh 🤔
I really don't get it tbh 🤔
Had to turn my freeBSD pet computer off in hopes of saving a couple of pennies off of the power bill. 🥲 And having had a blast spending time living in tty earlier this year, I thinking about daily driving the RPi4B for a while and let the main beast hibernate as well 🧘
Had to turn my freeBSD pet computer off in hopes of saving a couple of pennies off of the power bill. 🥲 And having had a blast spending time living in tty earlier this year, I thinking about daily driving the RPi4B for a while and let the main beast hibernate as well 🧘
Had to turn my freeBSD pet computer off in hopes of saving a couple of pennies off of the power bill. 🥲 And having had a blast spending time living in tty earlier this year, I thinking about daily driving the RPi4B for a while and let the main beast hibernate as well 🧘
🧮 USERS:1 FEEDS:2 TWTS:1199 ARCHIVED:83034 CACHE:2626 FOLLOWERS:17 FOLLOWING:14
@prologic it offends someone with a diff
erent opinion? 🤣
No, seriously... :diffoff
is used to disable vim's diff mode that's usually started running vim -d someFile someOtherFile
or by having both files on a split window and applying :diffthis
on both panes. (just learned this this morning)
@prologic it offends someone with a diff
erent opinion? 🤣
No, seriously... :diffoff
is used to disable vim's diff mode that's usually started running vim -d someFile someOtherFile
or by having both files on a split window and applying :diffthis
on both panes. (just learned this this morning)
@prologic it offends someone with a diff
erent opinion? 🤣
No, seriously... :diffoff
is used to disable vim's diff mode that's usually started running vim -d someFile someOtherFile
or by having both files on a split window and applying :diffthis
on both panes. (just learned this this morning)
[47°09′58″S, 126°43′03″W] Wind speed: N/A -- Cannot comunicate
@ LOL. Crypto rubbish backed? 🤦♂️
[47°09′11″S, 126°43′46″W] Automatic systems disengaged due to heavy rain
@prologic Indeed, I’ve gained a lot more respect for Linux/BSD and DOS. 😃
@prologic Indeed, I’ve gained a lot more respect for Linux/BSD and DOS. 😃
@prologic Indeed, I’ve gained a lot more respect for Linux/BSD and DOS. 😃
@prologic Indeed, I’ve gained a lot more respect for Linux/BSD and DOS. 😃
Documental low-cost
#catsoftwtxt
Documental low-cost
#catsoftwtxt
@movq Yeah I have to admit I don't know nearly enough about how the Linux Kernel works™ much here. I'm quite sure there's a lot under the covers that we just don't really fully appreciate 🤣
@movq Yeah I have to admit I don't know nearly enough about how the Linux Kernel works™ much here. I'm quite sure there's a lot under the covers that we just don't really fully appreciate 🤣
@lyse Oh, ah, that’s quite a lot of zoom. Still, 4m feels really close. Were you behind a bush? 😃
@lyse Oh, ah, that’s quite a lot of zoom. Still, 4m feels really close. Were you behind a bush? 😃
@lyse Oh, ah, that’s quite a lot of zoom. Still, 4m feels really close. Were you behind a bush? 😃
@lyse Oh, ah, that’s quite a lot of zoom. Still, 4m feels really close. Were you behind a bush? 😃
@prologic Something along those lines, yeah. And/or some generic cache for disk sectors.
@prologic Something along those lines, yeah. And/or some generic cache for disk sectors.
@prologic Something along those lines, yeah. And/or some generic cache for disk sectors.
@prologic Something along those lines, yeah. And/or some generic cache for disk sectors.
@movq Ahh so you lack some kind of an open()
syscall to hold some state for the open file, i.e: a "file descriptor"? 🤔
@movq Ahh so you lack some kind of an open()
syscall to hold some state for the open file, i.e: a "file descriptor"? 🤔
I from Windows 3.11 who need screen? :)
@prologic Lots, I guess. 😅 The kernel keeps almost no state between syscalls, so when you want to read the next byte from a file, it has to do all the work from scratch: Locate the file in the directory and traverse the cluster chain until you’ve reached the next byte. It’s easier to code this way, but obviously much slower. And the userspace program cp
could read/write in multiples of 512 – it currently does not do that, intentionally, because if everything is a multiple of 512, you’re less likely to discover bugs. 😅
@prologic Lots, I guess. 😅 The kernel keeps almost no state between syscalls, so when you want to read the next byte from a file, it has to do all the work from scratch: Locate the file in the directory and traverse the cluster chain until you’ve reached the next byte. It’s easier to code this way, but obviously much slower. And the userspace program cp
could read/write in multiples of 512 – it currently does not do that, intentionally, because if everything is a multiple of 512, you’re less likely to discover bugs. 😅
@prologic Lots, I guess. 😅 The kernel keeps almost no state between syscalls, so when you want to read the next byte from a file, it has to do all the work from scratch: Locate the file in the directory and traverse the cluster chain until you’ve reached the next byte. It’s easier to code this way, but obviously much slower. And the userspace program cp
could read/write in multiples of 512 – it currently does not do that, intentionally, because if everything is a multiple of 512, you’re less likely to discover bugs. 😅
@prologic Lots, I guess. 😅 The kernel keeps almost no state between syscalls, so when you want to read the next byte from a file, it has to do all the work from scratch: Locate the file in the directory and traverse the cluster chain until you’ve reached the next byte. It’s easier to code this way, but obviously much slower. And the userspace program cp
could read/write in multiples of 512 – it currently does not do that, intentionally, because if everything is a multiple of 512, you’re less likely to discover bugs. 😅
Es hört sich an wie Frühling und fühlt sich an wie Herbst: Es muss wohl Winter sein.
@movq Ahh (_sorry ignore my previous Twt_); Any way to optimize the no. of BIOS calls? 🤔
@movq Ahh (_sorry ignore my previous Twt_); Any way to optimize the no. of BIOS calls? 🤔
@movq Why is the implementation so slow? 🤔
@movq Why is the implementation so slow? 🤔