/https://duque-terron.cat/media/photos/photo_11001-04-2024_15-48-42.jpg) #catsoftwtxt
/https://duque-terron.cat/media/photos/photo_11001-04-2024_15-48-42.jpg) #catsoftwtxt
My client does not make use of the hash, so it’s fine for me. Other clients might, though, and I wonder how they’ll react to a “fictional” hash. 🤔 Maybe @lyse or @prologic have an opinion here. 😃
Oh, I forgot to mention: The URL should be relative to the fields location, so it should be
prev = archive twtxt-archive.txt. (This is to allow for multi-protocol feeds.)
My client does not make use of the hash, so it’s fine for me. Other clients might, though, and I wonder how they’ll react to a “fictional” hash. 🤔 Maybe @lyse or @prologic have an opinion here. 😃
Oh, I forgot to mention: The URL should be relative to the fields location, so it should be
prev = archive twtxt-archive.txt. (This is to allow for multi-protocol feeds.)
My client does not make use of the hash, so it’s fine for me. Other clients might, though, and I wonder how they’ll react to a “fictional” hash. 🤔 Maybe @lyse or @prologic have an opinion here. 😃
Oh, I forgot to mention: The URL should be relative to the fields location, so it should be
prev = archive twtxt-archive.txt. (This is to allow for multi-protocol feeds.)
I have put in a psudo twthash since I did not archive from a specific date/post, but just what I did not find relevant to keep in my main feed.
I have put in a psudo twthash since I did not archive from a specific date/post, but just what I did not find relevant to keep in my main feed.
I have put in a psudo twthash since I did not archive from a specific date/post, but just what I did not find relevant to keep in my main feed.
I have put in a psudo twthash since I did not archive from a specific date/post, but just what I did not find relevant to keep in my main feed.
prev field in your feed’s headers is invalid. 😅First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The
prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.For reference, the
prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html
prev field in your feed’s headers is invalid. 😅First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The
prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.For reference, the
prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html
prev field in your feed’s headers is invalid. 😅First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The
prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.For reference, the
prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html
Quod Libet usually just plays the whole collection from top to bottom and I manually skip every now and then. Sometimes even entire bands.
I've got all sorts of file types in ~/music. Usually each artist gets their own directory, depending on how many stuff I've got, there's usually a directory for the album and then come the tracks. Filenames are all over the place, for new stuff I use lowercase only and no spaces but dashes. I make use of common meta data such as artist, title, genre, often also year, album and track number. These days I get a lot of new music from YouTube and cut the start and end off with Audacity. The last three fields are only filled when I can be bothered to look them up.
Currently playing: https://www.youtube.com/watch?v=LS0hYhD-U0A~
OS/2 2.1 and 3.0 just won’t boot from a CF disk, they’re stuck at (or before?) the boot loader, completely silent, nothing happens, nothing on screen. MS-DOS 5.0 on the same CF disk boots just fine, though, as does the exact same OS/2 2.1 installation from a hard drive.
Hm. 🤔
OS/2 2.1 and 3.0 just won’t boot from a CF disk, they’re stuck at (or before?) the boot loader, completely silent, nothing happens, nothing on screen. MS-DOS 5.0 on the same CF disk boots just fine, though, as does the exact same OS/2 2.1 installation from a hard drive.
Hm. 🤔
OS/2 2.1 and 3.0 just won’t boot from a CF disk, they’re stuck at (or before?) the boot loader, completely silent, nothing happens, nothing on screen. MS-DOS 5.0 on the same CF disk boots just fine, though, as does the exact same OS/2 2.1 installation from a hard drive.
Hm. 🤔
belegtzeichen.wav
belegtzeichen.wav
belegtzeichen.wav
It was indeed pretty hard to capture today’s sky with a camera. This comes somewhat close:
https://movq.de/v/3fc94ed911/a.jpg
It was indeed pretty hard to capture today’s sky with a camera. This comes somewhat close:
https://movq.de/v/3fc94ed911/a.jpg
It was indeed pretty hard to capture today’s sky with a camera. This comes somewhat close:
https://movq.de/v/3fc94ed911/a.jpg
[](https://movq.de/v/d4be7212d2/dusage%2Dboth.png)
This compatibility layer only applies to 16 bit OS/2 1.x programs:
https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#OS/2_environment_subsystem
32 bit OS/2 2.x programs don’t run:
[](https://movq.de/v/d4be7212d2/dusage%2Dos2v2%2Don%2D2k.png)
I wonder how many text mode 16 bit OS/2 programs still existed when Windows 2000 came out. 🤔 Was it really worth keeping this subsystem around for so long?
[](https://movq.de/v/d4be7212d2/dusage%2Dboth.png)
This compatibility layer only applies to 16 bit OS/2 1.x programs:
https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#OS/2_environment_subsystem
32 bit OS/2 2.x programs don’t run:
[](https://movq.de/v/d4be7212d2/dusage%2Dos2v2%2Don%2D2k.png)
I wonder how many text mode 16 bit OS/2 programs still existed when Windows 2000 came out. 🤔 Was it really worth keeping this subsystem around for so long?
[](https://movq.de/v/d4be7212d2/dusage%2Dboth.png)
This compatibility layer only applies to 16 bit OS/2 1.x programs:
https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#OS/2_environment_subsystem
32 bit OS/2 2.x programs don’t run:
[](https://movq.de/v/d4be7212d2/dusage%2Dos2v2%2Don%2D2k.png)
I wonder how many text mode 16 bit OS/2 programs still existed when Windows 2000 came out. 🤔 Was it really worth keeping this subsystem around for so long?
Another weird thing: I realized that I kept pressing the strings *waaaaay* too hard to that guitar. This screws up the intonation completely (notes getting higher). I almost thought the instrument was broken. 😅
Guitars are super delicate things …
Another weird thing: I realized that I kept pressing the strings *waaaaay* too hard to that guitar. This screws up the intonation completely (notes getting higher). I almost thought the instrument was broken. 😅
Guitars are super delicate things …
Another weird thing: I realized that I kept pressing the strings *waaaaay* too hard to that guitar. This screws up the intonation completely (notes getting higher). I almost thought the instrument was broken. 😅
Guitars are super delicate things …
#running
#running
#running
#running
#SemanaSanta ⌘ Read more****