# 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 15507
# self = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=14206
# next = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=14306
# prev = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=14106
@kat Well, consider me jealous. 😅
So, is that a standard lubuntu or a special version for that laptop? Any driver issues so far?
The most valuable resource is Table B-13 at the end of Volume 2D of the Intel docs. It’s a very long but easy to understand table of instruction encodings – assuming you already know how that ModR/M stuff works.
The most valuable resource is Table B-13 at the end of Volume 2D of the Intel docs. It’s a very long but easy to understand table of instruction encodings – assuming you already know how that ModR/M stuff works.
The most valuable resource is Table B-13 at the end of Volume 2D of the Intel docs. It’s a very long but easy to understand table of instruction encodings – assuming you already know how that ModR/M stuff works.
The most valuable resource is Table B-13 at the end of Volume 2D of the Intel docs. It’s a very long but easy to understand table of instruction encodings – assuming you already know how that ModR/M stuff works.
@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.
@lyse I read it in the news, lots of ice in your area. 🫤 (There’s nothing going on over here.)
@lyse I read it in the news, lots of ice in your area. 🫤 (There’s nothing going on over here.)
@lyse I read it in the news, lots of ice in your area. 🫤 (There’s nothing going on over here.)
@lyse I read it in the news, lots of ice in your area. 🫤 (There’s nothing going on over here.)
Alright, I have a little 8086 assembler for my toy OS going now – or rather a proof-of-concept thereof. It only supports a tiny fraction of the instruction set. It was an interesting learning experience, but I don’t think trying to “complete” this program is worth my time.
The whole thing is just a learning project, I don’t want to actually make a usable OS. There are a few more things I want to have a look at and then I’ll eventually move on to 386/amd64 later this year (hopefully).
https://movq.de/v/d8f30cbe75/vid3.mp4
Alright, I have a little 8086 assembler for my toy OS going now – or rather a proof-of-concept thereof. It only supports a tiny fraction of the instruction set. It was an interesting learning experience, but I don’t think trying to “complete” this program is worth my time.
The whole thing is just a learning project, I don’t want to actually make a usable OS. There are a few more things I want to have a look at and then I’ll eventually move on to 386/amd64 later this year (hopefully).
https://movq.de/v/d8f30cbe75/vid3.mp4
Alright, I have a little 8086 assembler for my toy OS going now – or rather a proof-of-concept thereof. It only supports a tiny fraction of the instruction set. It was an interesting learning experience, but I don’t think trying to “complete” this program is worth my time.
The whole thing is just a learning project, I don’t want to actually make a usable OS. There are a few more things I want to have a look at and then I’ll eventually move on to 386/amd64 later this year (hopefully).
https://movq.de/v/d8f30cbe75/vid3.mp4
Alright, I have a little 8086 assembler for my toy OS going now – or rather a proof-of-concept thereof. It only supports a tiny fraction of the instruction set. It was an interesting learning experience, but I don’t think trying to “complete” this program is worth my time.
The whole thing is just a learning project, I don’t want to actually make a usable OS. There are a few more things I want to have a look at and then I’ll eventually move on to 386/amd64 later this year (hopefully).
https://movq.de/v/d8f30cbe75/vid3.mp4
@aelaraji Nice! 🥳
And thanks for the reminder! I forgot, of course. But I had a quick look now and got to see Saturn and its (currently very flat) rings. This never gets old, always blows my mind. Looks like a scifi movie. 😃
@aelaraji Nice! 🥳
And thanks for the reminder! I forgot, of course. But I had a quick look now and got to see Saturn and its (currently very flat) rings. This never gets old, always blows my mind. Looks like a scifi movie. 😃
@aelaraji Nice! 🥳
And thanks for the reminder! I forgot, of course. But I had a quick look now and got to see Saturn and its (currently very flat) rings. This never gets old, always blows my mind. Looks like a scifi movie. 😃
@aelaraji Nice! 🥳
And thanks for the reminder! I forgot, of course. But I had a quick look now and got to see Saturn and its (currently very flat) rings. This never gets old, always blows my mind. Looks like a scifi movie. 😃
@lyse That was great! 😃 Now I need to go back and watch the other videos by that guy. 😅
@lyse That was great! 😃 Now I need to go back and watch the other videos by that guy. 😅
@lyse That was great! 😃 Now I need to go back and watch the other videos by that guy. 😅
@lyse That was great! 😃 Now I need to go back and watch the other videos by that guy. 😅
@lyse Hmm, their illustration looks pretty optimistic. 🤔 When I look at it in Stellarium, the cluster around Saturn is pretty close to the Sun. Not sure you can see them. 🤔 Saturn is even closer to the Sun than Mercury – and Mercury is notoriously hard to observe.
But I hope I’m wrong!
January looks pretty interesting, too, btw.
@lyse Hmm, their illustration looks pretty optimistic. 🤔 When I look at it in Stellarium, the cluster around Saturn is pretty close to the Sun. Not sure you can see them. 🤔 Saturn is even closer to the Sun than Mercury – and Mercury is notoriously hard to observe.
But I hope I’m wrong!
January looks pretty interesting, too, btw.
@lyse Hmm, their illustration looks pretty optimistic. 🤔 When I look at it in Stellarium, the cluster around Saturn is pretty close to the Sun. Not sure you can see them. 🤔 Saturn is even closer to the Sun than Mercury – and Mercury is notoriously hard to observe.
But I hope I’m wrong!
January looks pretty interesting, too, btw.
@lyse Hmm, their illustration looks pretty optimistic. 🤔 When I look at it in Stellarium, the cluster around Saturn is pretty close to the Sun. Not sure you can see them. 🤔 Saturn is even closer to the Sun than Mercury – and Mercury is notoriously hard to observe.
But I hope I’m wrong!
January looks pretty interesting, too, btw.
The editor can launch a new shell now:
https://movq.de/v/6ec68b50dd/los86-edit-shell.mp4
Trivial to implement but super useful. It allows for simple but meaningful dev cycles: Edit source code, run/test it, back to editor. That’s what I do in the video.
(The Brainfuck program is silly, but I got nothing else at the moment.)
The I/O cache is also getting better. All that back and forth doesn’t hit the disk at all, once cached.
This whole thing is much more fun and interesting when you run it from a real floppy disk. It’s a 5.25" floppy in the video (so it’s *actually* _floppy_ 😅). Disk seek times can be *catastrophic* and you don’t notice any of this on modern disks.
The editor can launch a new shell now:
https://movq.de/v/6ec68b50dd/los86-edit-shell.mp4
Trivial to implement but super useful. It allows for simple but meaningful dev cycles: Edit source code, run/test it, back to editor. That’s what I do in the video.
(The Brainfuck program is silly, but I got nothing else at the moment.)
The I/O cache is also getting better. All that back and forth doesn’t hit the disk at all, once cached.
This whole thing is much more fun and interesting when you run it from a real floppy disk. It’s a 5.25" floppy in the video (so it’s *actually* _floppy_ 😅). Disk seek times can be *catastrophic* and you don’t notice any of this on modern disks.
The editor can launch a new shell now:
https://movq.de/v/6ec68b50dd/los86-edit-shell.mp4
Trivial to implement but super useful. It allows for simple but meaningful dev cycles: Edit source code, run/test it, back to editor. That’s what I do in the video.
(The Brainfuck program is silly, but I got nothing else at the moment.)
The I/O cache is also getting better. All that back and forth doesn’t hit the disk at all, once cached.
This whole thing is much more fun and interesting when you run it from a real floppy disk. It’s a 5.25" floppy in the video (so it’s *actually* _floppy_ 😅). Disk seek times can be *catastrophic* and you don’t notice any of this on modern disks.
The editor can launch a new shell now:
https://movq.de/v/6ec68b50dd/los86-edit-shell.mp4
Trivial to implement but super useful. It allows for simple but meaningful dev cycles: Edit source code, run/test it, back to editor. That’s what I do in the video.
(The Brainfuck program is silly, but I got nothing else at the moment.)
The I/O cache is also getting better. All that back and forth doesn’t hit the disk at all, once cached.
This whole thing is much more fun and interesting when you run it from a real floppy disk. It’s a 5.25" floppy in the video (so it’s *actually* _floppy_ 😅). Disk seek times can be *catastrophic* and you don’t notice any of this on modern disks.
@andros Being able to render user avatars is certainly nice. 😃 I’m always happy to see more twtxt/Yarn clients!
@andros Being able to render user avatars is certainly nice. 😃 I’m always happy to see more twtxt/Yarn clients!
@andros Being able to render user avatars is certainly nice. 😃 I’m always happy to see more twtxt/Yarn clients!
@andros Being able to render user avatars is certainly nice. 😃 I’m always happy to see more twtxt/Yarn clients!
@arne Ach wie schön. :-) BF1942 hab’ ich schon ewig nicht mehr gesehen. Meine mich zu erinnern, dass das im Multiplayer ein bisschen wonky war, kam nicht an Größen wie UT oder Q3 ran. Aber es war lustig mit all den Fahrzeugen, Flugzeugen, Schiffen. 😅
@arne Ach wie schön. :-) BF1942 hab’ ich schon ewig nicht mehr gesehen. Meine mich zu erinnern, dass das im Multiplayer ein bisschen wonky war, kam nicht an Größen wie UT oder Q3 ran. Aber es war lustig mit all den Fahrzeugen, Flugzeugen, Schiffen. 😅
@arne Ach wie schön. :-) BF1942 hab’ ich schon ewig nicht mehr gesehen. Meine mich zu erinnern, dass das im Multiplayer ein bisschen wonky war, kam nicht an Größen wie UT oder Q3 ran. Aber es war lustig mit all den Fahrzeugen, Flugzeugen, Schiffen. 😅
@arne Ach wie schön. :-) BF1942 hab’ ich schon ewig nicht mehr gesehen. Meine mich zu erinnern, dass das im Multiplayer ein bisschen wonky war, kam nicht an Größen wie UT oder Q3 ran. Aber es war lustig mit all den Fahrzeugen, Flugzeugen, Schiffen. 😅
@doesnmppsflt Hmmm, the only time jenny requests something from twtxt.net is when you use the fetch context feature. jenny doesn’t interpret those long IDs as valid twt hashes, though, and won’t try to fetch them from Yarn. 🤔
Can you still reproduce this bug?
@doesnmppsflt Hmmm, the only time jenny requests something from twtxt.net is when you use the fetch context feature. jenny doesn’t interpret those long IDs as valid twt hashes, though, and won’t try to fetch them from Yarn. 🤔
Can you still reproduce this bug?
@doesnmppsflt Hmmm, the only time jenny requests something from twtxt.net is when you use the fetch context feature. jenny doesn’t interpret those long IDs as valid twt hashes, though, and won’t try to fetch them from Yarn. 🤔
Can you still reproduce this bug?
@doesnmppsflt Hmmm, the only time jenny requests something from twtxt.net is when you use the fetch context feature. jenny doesn’t interpret those long IDs as valid twt hashes, though, and won’t try to fetch them from Yarn. 🤔
Can you still reproduce this bug?
@kat Oh, nice. I didn’t get the chance yet to actually see and use one of those in real life, but they look *very* interesting. If my current laptop ever breaks down, I hope that framework will still be around. 😅
@kat Oh, nice. I didn’t get the chance yet to actually see and use one of those in real life, but they look *very* interesting. If my current laptop ever breaks down, I hope that framework will still be around. 😅
@kat Oh, nice. I didn’t get the chance yet to actually see and use one of those in real life, but they look *very* interesting. If my current laptop ever breaks down, I hope that framework will still be around. 😅
@kat Oh, nice. I didn’t get the chance yet to actually see and use one of those in real life, but they look *very* interesting. If my current laptop ever breaks down, I hope that framework will still be around. 😅
@arne Meine letzte LAN ist deutlich über 15 Jahre her. Die letzte *richtige* mit vielen Leuten und so tollen Sachen wie „wir schleppen mal Tower-PC und Röhrenmonitor im Zug quer durch Deutschland“ ist sicher 20 Jahre her. 😂
@arne Meine letzte LAN ist deutlich über 15 Jahre her. Die letzte *richtige* mit vielen Leuten und so tollen Sachen wie „wir schleppen mal Tower-PC und Röhrenmonitor im Zug quer durch Deutschland“ ist sicher 20 Jahre her. 😂
@arne Meine letzte LAN ist deutlich über 15 Jahre her. Die letzte *richtige* mit vielen Leuten und so tollen Sachen wie „wir schleppen mal Tower-PC und Röhrenmonitor im Zug quer durch Deutschland“ ist sicher 20 Jahre her. 😂
@arne Meine letzte LAN ist deutlich über 15 Jahre her. Die letzte *richtige* mit vielen Leuten und so tollen Sachen wie „wir schleppen mal Tower-PC und Röhrenmonitor im Zug quer durch Deutschland“ ist sicher 20 Jahre her. 😂
@lyse I’ve never written any substantial Brainfuck code myself. It’s super fascinating, though. The programs from https://brainfuck.org/ are very short and yet they do a lot. I don’t know how long numwarp.b would be if I wrote it in Python. 🤯
@lyse I’ve never written any substantial Brainfuck code myself. It’s super fascinating, though. The programs from https://brainfuck.org/ are very short and yet they do a lot. I don’t know how long numwarp.b would be if I wrote it in Python. 🤯
@lyse I’ve never written any substantial Brainfuck code myself. It’s super fascinating, though. The programs from https://brainfuck.org/ are very short and yet they do a lot. I don’t know how long numwarp.b would be if I wrote it in Python. 🤯
@lyse I’ve never written any substantial Brainfuck code myself. It’s super fascinating, though. The programs from https://brainfuck.org/ are very short and yet they do a lot. I don’t know how long numwarp.b would be if I wrote it in Python. 🤯
@doesnmppsflt Not sure which bug you’re referring to. 🤔 (Did I forget?)
Those long IDs like (#113797927355322708) are simply part of that feed. Looks like the author just dumps ActivityPub IDs into twtxt. I think this used to work in the past, but the corresponding spec (https://twtxt.dev/exts/hash-tag.html) has been deprecated and jenny doesn’t support – actually, jenny never supported that.
jenny can only group threads by exactly one criterium (because it writes a Message-ID into the mail file) and that’s the regular twt hash. So, anything else, like people doing “#CoolTopic”, isn’t possible.
@doesnmppsflt Not sure which bug you’re referring to. 🤔 (Did I forget?)
Those long IDs like (#113797927355322708) are simply part of that feed. Looks like the author just dumps ActivityPub IDs into twtxt. I think this used to work in the past, but the corresponding spec (https://twtxt.dev/exts/hash-tag.html) has been deprecated and jenny doesn’t support – actually, jenny never supported that.
jenny can only group threads by exactly one criterium (because it writes a Message-ID into the mail file) and that’s the regular twt hash. So, anything else, like people doing “#CoolTopic”, isn’t possible.
@doesnmppsflt Not sure which bug you’re referring to. 🤔 (Did I forget?)
Those long IDs like (#113797927355322708) are simply part of that feed. Looks like the author just dumps ActivityPub IDs into twtxt. I think this used to work in the past, but the corresponding spec (https://twtxt.dev/exts/hash-tag.html) has been deprecated and jenny doesn’t support – actually, jenny never supported that.
jenny can only group threads by exactly one criterium (because it writes a Message-ID into the mail file) and that’s the regular twt hash. So, anything else, like people doing “#CoolTopic”, isn’t possible.
@doesnmppsflt Not sure which bug you’re referring to. 🤔 (Did I forget?)
Those long IDs like (#113797927355322708) are simply part of that feed. Looks like the author just dumps ActivityPub IDs into twtxt. I think this used to work in the past, but the corresponding spec (https://twtxt.dev/exts/hash-tag.html) has been deprecated and jenny doesn’t support – actually, jenny never supported that.
jenny can only group threads by exactly one criterium (because it writes a Message-ID into the mail file) and that’s the regular twt hash. So, anything else, like people doing “#CoolTopic”, isn’t possible.
@prologic Fine by me. I don’t see/remember a valid reason for just doing @. Was there ever a reason to do that? 🤔
@prologic Fine by me. I don’t see/remember a valid reason for just doing @. Was there ever a reason to do that? 🤔
@prologic Fine by me. I don’t see/remember a valid reason for just doing @. Was there ever a reason to do that? 🤔
@prologic Fine by me. I don’t see/remember a valid reason for just doing @. Was there ever a reason to do that? 🤔
Not a witch, I’m just programmed that way. 😂
Not a witch, I’m just programmed that way. 😂
Not a witch, I’m just programmed that way. 😂
Not a witch, I’m just programmed that way. 😂
I just used screego to help a family member with their Windows PC. Flawless experience! 💚
I just used screego to help a family member with their Windows PC. Flawless experience! 💚
I just used screego to help a family member with their Windows PC. Flawless experience! 💚
I just used screego to help a family member with their Windows PC. Flawless experience! 💚
@lyse You would love the recent changes in Google Chat. Emojis are animated now. 🥴
@lyse You would love the recent changes in Google Chat. Emojis are animated now. 🥴
@lyse You would love the recent changes in Google Chat. Emojis are animated now. 🥴
@lyse You would love the recent changes in Google Chat. Emojis are animated now. 🥴
@lyse Not bad, I got over 1000. (And I expected more as well.) It felt great to just create a folder called “vacation2024” and move them all in there, done. 😏
@lyse Not bad, I got over 1000. (And I expected more as well.) It felt great to just create a folder called “vacation2024” and move them all in there, done. 😏
@lyse Not bad, I got over 1000. (And I expected more as well.) It felt great to just create a folder called “vacation2024” and move them all in there, done. 😏
@lyse Not bad, I got over 1000. (And I expected more as well.) It felt great to just create a folder called “vacation2024” and move them all in there, done. 😏
@lyse Earplugs are great, too! Feels like they block out more noise than NC headphones.
I automatically take off the headphones when I’m half asleep. I don’t even notice it. 😂
@lyse Earplugs are great, too! Feels like they block out more noise than NC headphones.
I automatically take off the headphones when I’m half asleep. I don’t even notice it. 😂
@lyse Earplugs are great, too! Feels like they block out more noise than NC headphones.
I automatically take off the headphones when I’m half asleep. I don’t even notice it. 😂
