# 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 196320
# self = https://watcher.sour.is?offset=155958
# next = https://watcher.sour.is?offset=156058
# prev = https://watcher.sour.is?offset=155858
@lyse Oh, wow, du hast’s sogar inhatlich gelesen. 😀 Danke für die Hinweise, wird korrigiert!
> Hurenkindalarm auf den Seiten 11 und 12. :-P
Jup, ganz fiese sogar. Wundert mich, dass LaTeX das nicht standardmäßig anders arrangiert, um das zu vermeiden. Muss ich nochmal nachschauen, so hübsch ist’s ja nun nicht. 😀
> Die Levelgenerierung finde ich ziemlich genial.
Zu der Idee mit der Musterersetzung bin ich über Advent of Code gekommen. Also nicht direkt über die Puzzles, aber auf Reddit wird manchmal diskutiert, wie denn wohl die Puzzle-Daten bei AoC erstellt werden – da gibt es nämlich auch ganz viele solcher „Labyrinthe“. Und da hat mal einer geschrieben: „Wahrscheinlich beginnt er mit einem Kreis und deformiert den dann so lange, bis $Bedingung erreicht ist.“
Auch die Darstellung der Strecken in der Textdatei ist ganz stark an AoC-Puzzles angelehnt.
Mich fasziniert ein bisschen, dass quasi nur eine Regel („da ist eine Gerade, mach’ mal einen Knick rein“) ausreicht, um so viel Variation zu erreichen. Also, das ist schon noch verbesserungsfähig, aber es funktioniert schon deutlich besser, als ich erwartet hatte.
Michigan Vs Washington tonight. Should be a great game!
@movq Sehr schön! Wahrscheinlich hätte ich mir zuvor die referenzierten Dokumente anschauen müssen, um Deinem Aufschrieb einfacher folgen zu können. Die Levelgenerierung finde ich ziemlich genial. Seite 17:
> Diese Ersetzungsregel existiert für alle Richtungen, nicht nur horizontal.
Müsse „vertikal“ statt „horizontal“ heißen, oder?
Mit Abbildung 13 hatte ich erst so meine Schwierigkeiten, die Erläuterung im Fließtext hat dann aber die Sache schließlich nach mehreren Runden aufgeklärt. Ein Hinweis auf die weißen Kästchen nach dem grünen Feld hätte mir vermutlich geholfen. Außerdem hab ich ne ganze Weile gebraucht, diese verbundene, lange Zelle in der Mitte zu verstehen. :-D
Hurenkindalarm auf den Seiten 11 und 12. :-P
Surprisingly, it took me only half a day to go through all the written communications.
[47°09′19″S, 126°43′38″W] Weather forecast alert -- storm from SW
[47°09′32″S, 126°43′43″W] Not enough data -- sampling finished
[47°09′50″S, 126°43′40″W] Taking samples
[47°09′39″S, 126°43′01″W] Transfer aborted
🧮 USERS:1 FEEDS:2 TWTS:839 ARCHIVED:69718 CACHE:2353 FOLLOWERS:14 FOLLOWING:14
just be bored. things will end up more fun.
[47°09′05″S, 126°43′35″W] Waiting for carrier
[47°09′31″S, 126°43′32″W] Transponder still failing -- switching to analog communication
Pinellas County - Long Run: 13.12 miles, 00:09:14 average pace, 02:01:03 duration
it was pouring with heavy winds when i woke up so i waited a bit for it to calm down before heading out. it was great until the rain stopped and the humidity came in which coincided with the ascent. overall it was a good session. beth's handheld water sucks.
#running
Pinellas County - Long Run: 13.12 miles, 00:09:14 average pace, 02:01:03 duration
it was pouring with heavy winds when i woke up so i waited a bit for it to calm down before heading out. it was great until the rain stopped and the humidity came in which coincided with the ascent. overall it was a good session. beth's handheld water sucks.
#running
Pinellas County - Long Run: 13.12 miles, 00:09:14 average pace, 02:01:03 duration
it was pouring with heavy winds when i woke up so i waited a bit for it to calm down before heading out. it was great until the rain stopped and the humidity came in which coincided with the ascent. overall it was a good session. beth's handheld water sucks.
#running
[47°09′06″S, 126°43′47″W] Transponder malfunction
@lyse It’s much more than I expected. In my experience, trying to use assembly to optimize C programs has hardly any effect these days. The C compilers have become really, really good. If anything, you’ll make it worse when you put your own assembly stuff in there. 😅 But apparently it’s a different story for Open Watcom / DOS / real mode … 🤔
@lyse It’s much more than I expected. In my experience, trying to use assembly to optimize C programs has hardly any effect these days. The C compilers have become really, really good. If anything, you’ll make it worse when you put your own assembly stuff in there. 😅 But apparently it’s a different story for Open Watcom / DOS / real mode … 🤔
@lyse It’s much more than I expected. In my experience, trying to use assembly to optimize C programs has hardly any effect these days. The C compilers have become really, really good. If anything, you’ll make it worse when you put your own assembly stuff in there. 😅 But apparently it’s a different story for Open Watcom / DOS / real mode … 🤔
@stigatle Someone on Mastodon mentioned that it might be worth using assembly instead of C. So I rewrote two hot code paths with inline assembly this morning. And, lo and behold, this got me from ~27.6 fps to ~38.5 fps. 🤯
@stigatle Someone on Mastodon mentioned that it might be worth using assembly instead of C. So I rewrote two hot code paths with inline assembly this morning. And, lo and behold, this got me from ~27.6 fps to ~38.5 fps. 🤯
@stigatle Someone on Mastodon mentioned that it might be worth using assembly instead of C. So I rewrote two hot code paths with inline assembly this morning. And, lo and behold, this got me from ~27.6 fps to ~38.5 fps. 🤯
@eapl.me Yeah, the good thing about racing games is that they’re so simple. 😅 No story needed, no complex game logic. It was perfect for this little toy project. (It’s not the actual Wolfenstein engine, though, it’s just the same method of rendering. 😅)
@eapl.me Yeah, the good thing about racing games is that they’re so simple. 😅 No story needed, no complex game logic. It was perfect for this little toy project. (It’s not the actual Wolfenstein engine, though, it’s just the same method of rendering. 😅)
@eapl.me Yeah, the good thing about racing games is that they’re so simple. 😅 No story needed, no complex game logic. It was perfect for this little toy project. (It’s not the actual Wolfenstein engine, though, it’s just the same method of rendering. 😅)
[47°09′00″S, 126°43′33″W] Raw reading: 0x659A5A01, offset +/-1
[47°09′05″S, 126°43′56″W] Storm recedes -- back to normal work
🧮 USERS:1 FEEDS:2 TWTS:838 ARCHIVED:69711 CACHE:2351 FOLLOWERS:14 FOLLOWING:14
@eapl.me Interesting 🤔 But the most interesting piece I noticed was this:
> Open source is broken and developers working full-time in the open have a hard time making ends meet compared to employed equivalents.
>
> Taking a step towards one possible solution for open source precarity, Rad Reader will be 100% open sourced on reaching 350 purchases.
@eapl.me Interesting 🤔 But the most interesting piece I noticed was this:
> Open source is broken and developers working full-time in the open have a hard time making ends meet compared to employed equivalents.
>
> Taking a step towards one possible solution for open source precarity, Rad Reader will be 100% open sourced on reaching 350 purchases.
@eapl.me Interesting 🤔 But the most interesting piece I noticed was this:
> Open source is broken and developers working full-time in the open have a hard time making ends meet compared to employed equivalents.
>
> Taking a step towards one possible solution for open source precarity, Rad Reader will be 100% open sourced on reaching 350 purchases.
logs/photojournal: final entries for 2023
[47°09′01″S, 126°43′29″W] Wind speed: 96kph -- batteries low
[47°09′12″S, 126°43′07″W] Wind speed: 107kph -- batteries low
#catsoftwtxt
#catsoftwtxt
@prologic @movq Well, there are a few things that might be important to me, but I would miss otherwise. I should maybe spend a bunch more time on creating filter rules for all that crap. Sort out mails from bots into the trash automatically and things like that. A lot of definitely important stuff is already handled. But the maybe pile is still quite large.
@stigatle Almost 100% C. A tiny little bit of inline assembly, but it’s just a few instructions.
I use Open Watcom V2 to cross-compile it directly from Linux, pretty handy.
@stigatle Almost 100% C. A tiny little bit of inline assembly, but it’s just a few instructions.
I use Open Watcom V2 to cross-compile it directly from Linux, pretty handy.
@stigatle Almost 100% C. A tiny little bit of inline assembly, but it’s just a few instructions.
I use Open Watcom V2 to cross-compile it directly from Linux, pretty handy.
@movq Very cool! what language is used for the coding?
Last week of my vacation. I made a little racing game for real-mode DOS that uses ray casting for rendering. There’s not a lot of game logic, except for lap timing and the tiles next to the walls have very high friction.
The tracks are procedurally generated. You can select one from the command line. (I love that concept very much.)
Getting the basic game done wasn’t too hard. I could reuse a lot of code from my little pool billiards game.
But … oh my goodness, the performance? The video was made on my Pentium 133, which is *very* powerful for the DOS era. And yet, it barely makes it above 25 FPS. I already used a couple of tricks (no floating point in some parts, try to keep an eye on cache locality, …) and I’ve passed on texturing the floor. The hot code paths are those that copy data in memory, like reading a pixel value for a texture and then copying it to the VGA buffer.
I’ve learned to appreciate games like Duke Nukem 3D a lot more now – how on earth can they be so fast? 🤯 I’ve got some homework to do …
https://movq.de/v/18f0d4be8d/MVI_6951.MOV.mp4
Last week of my vacation. I made a little racing game for real-mode DOS that uses ray casting for rendering. There’s not a lot of game logic, except for lap timing and the tiles next to the walls have very high friction.
The tracks are procedurally generated. You can select one from the command line. (I love that concept very much.)
Getting the basic game done wasn’t too hard. I could reuse a lot of code from my little pool billiards game.
But … oh my goodness, the performance? The video was made on my Pentium 133, which is *very* powerful for the DOS era. And yet, it barely makes it above 25 FPS. I already used a couple of tricks (no floating point in some parts, try to keep an eye on cache locality, …) and I’ve passed on texturing the floor. The hot code paths are those that copy data in memory, like reading a pixel value for a texture and then copying it to the VGA buffer.
I’ve learned to appreciate games like Duke Nukem 3D a lot more now – how on earth can they be so fast? 🤯 I’ve got some homework to do …
https://movq.de/v/18f0d4be8d/MVI_6951.MOV.mp4
Last week of my vacation. I made a little racing game for real-mode DOS that uses ray casting for rendering. There’s not a lot of game logic, except for lap timing and the tiles next to the walls have very high friction.
The tracks are procedurally generated. You can select one from the command line. (I love that concept very much.)
Getting the basic game done wasn’t too hard. I could reuse a lot of code from my little pool billiards game.
But … oh my goodness, the performance? The video was made on my Pentium 133, which is *very* powerful for the DOS era. And yet, it barely makes it above 25 FPS. I already used a couple of tricks (no floating point in some parts, try to keep an eye on cache locality, …) and I’ve passed on texturing the floor. The hot code paths are those that copy data in memory, like reading a pixel value for a texture and then copying it to the VGA buffer.
I’ve learned to appreciate games like Duke Nukem 3D a lot more now – how on earth can they be so fast? 🤯 I’ve got some homework to do …
https://movq.de/v/18f0d4be8d/MVI_6951.MOV.mp4
Desde hace unos días, tengo una cámara de vigilancia gatuna
#catsoftwtxt
Desde hace unos días, tengo una cámara de vigilancia gatuna
#catsoftwtxt
[47°09′48″S, 126°43′28″W] Wind speed: 43kph
@lyse
> going through gazillion of e-mails
I’m going to create a new IMAP folder called “Vacation 2023” and move all mail in there. I won’t read a single one of it until needed. 😅
@lyse
> going through gazillion of e-mails
I’m going to create a new IMAP folder called “Vacation 2023” and move all mail in there. I won’t read a single one of it until needed. 😅
@lyse
> going through gazillion of e-mails
I’m going to create a new IMAP folder called “Vacation 2023” and move all mail in there. I won’t read a single one of it until needed. 😅
@lyse It's time like this, every time I go on extended holidays, when I come back to work, I just declare "email/chat" bankruptcy 😅 🤣
@lyse It's time like this, every time I go on extended holidays, when I come back to work, I just declare "email/chat" bankruptcy 😅 🤣
@lyse It's time like this, every time I go on extended holidays, when I come back to work, I just declare "email/chat" bankruptcy 😅 🤣
@lyse So it's a "man-made" lake? 🤔
@lyse So it's a "man-made" lake? 🤔
@lyse So it's a "man-made" lake? 🤔
@prologic I hear you! I reckon Monday will be only going through gazillion of e-mails and following up different chats (of course there are different ones, why would you settle on one?).
[47°09′06″S, 126°43′54″W] Weather forecast alert -- storm from E
I saw a Cybertruck earlier. I'm no fan of Tesla, but that thing is pretty cool.
I _feel_ a little safer using the Web with Little Snitch installed on my personal Mac 😅 I've already blocked unwanted traffic from SyncThing as well as Brew. Syncthing wanted to talk to various pub sub services, which I said "fuck no", "isn't this thing meant to be local?!" And Brew (_shame on you_) wants to send analytics to influxdata.com 🤦♂️ C'mon Homebrew, run your own fucking Influx server 😅
I _feel_ a little safer using the Web with Little Snitch installed on my personal Mac 😅 I've already blocked unwanted traffic from SyncThing as well as Brew. Syncthing wanted to talk to various pub sub services, which I said "fuck no", "isn't this thing meant to be local?!" And Brew (_shame on you_) wants to send analytics to influxdata.com 🤦♂️ C'mon Homebrew, run your own fucking Influx server 😅
I _feel_ a little safer using the Web with Little Snitch installed on my personal Mac 😅 I've already blocked unwanted traffic from SyncThing as well as Brew. Syncthing wanted to talk to various pub sub services, which I said "fuck no", "isn't this thing meant to be local?!" And Brew (_shame on you_) wants to send analytics to influxdata.com 🤦♂️ C'mon Homebrew, run your own fucking Influx server 😅
[47°09′21″S, 126°43′11″W] Reading: 0.17000 PPM
🧮 USERS:1 FEEDS:2 TWTS:837 ARCHIVED:69697 CACHE:2349 FOLLOWERS:14 FOLLOWING:14
Recovery: 1.00 miles, 00:10:29 average pace, 00:10:29 duration
#running #treadmill
Recovery: 1.00 miles, 00:10:29 average pace, 00:10:29 duration
#running #treadmill
Recovery: 1.00 miles, 00:10:29 average pace, 00:10:29 duration
#running #treadmill
@lyse You said this was a lake?! 😱 Where? 🤔 Looks more like logging activity 😢
@lyse You said this was a lake?! 😱 Where? 🤔 Looks more like logging activity 😢
@lyse You said this was a lake?! 😱 Where? 🤔 Looks more like logging activity 😢
/https://duque-terron.cat/media/photos/photo_6006-01-2024_14-57-15.jpg) #catsoftwtxt
/https://duque-terron.cat/media/photos/photo_5906-01-2024_11-34-23.jpg) #catsoftwtxt