It is kind of a hassle to keep things in sync and NOT eff up.
It happened to me before but I was lucky enough to have backups elsewhere.
But, now I kind of have a workflow to avoid data loss while benefiting from both tools.
P.S: my bad, I meant Syncthing earlier on my original replay instead of Rsync. 🫠
It is kind of a hassle to keep things in sync and NOT eff up.
It happened to me before but I was lucky enough to have backups elsewhere.
But, now I kind of have a workflow to avoid data loss while benefiting from both tools.
P.S: my bad, I meant Syncthing earlier on my original replay instead of Rsync. 🫠
at about mile 3 i switched to 4 minutes on 1 minute off. this was because my left knee started to act up. kept this up pretty well until a weird sharp pain at about 7 and a half miles. walked it off for a bit and tried again but called it when things didn't feel right. don't want to regress.
#running #injury
“PM” stands for “Presentation Manager” and is/was common prefix for graphical OS/2 programs. The PM actually got replaced by the “Workplace Shell” in version 2.0, but somehow the
PM prefix kept being used. At least that is how I remember it. 🥴Hmm, right, an “Abort” button. That could be useful. In my tests, the scans always finished so quickly that I didn’t even think about this … 😅
“PM” stands for “Presentation Manager” and is/was common prefix for graphical OS/2 programs. The PM actually got replaced by the “Workplace Shell” in version 2.0, but somehow the
PM prefix kept being used. At least that is how I remember it. 🥴Hmm, right, an “Abort” button. That could be useful. In my tests, the scans always finished so quickly that I didn’t even think about this … 😅
“PM” stands for “Presentation Manager” and is/was common prefix for graphical OS/2 programs. The PM actually got replaced by the “Workplace Shell” in version 2.0, but somehow the
PM prefix kept being used. At least that is how I remember it. 🥴Hmm, right, an “Abort” button. That could be useful. In my tests, the scans always finished so quickly that I didn’t even think about this … 😅
at about mile 3 i switched to 4' on 1' off. this was because my left knee started to act up. kept this up pretty well until a weird sharp pain at about 7.5 miles. walked it off a bit and tried again but called it when things did not feel right.
#running
at about mile 3 i switched to 4' on 1' off. this was because my left knee started to act up. kept this up pretty well until a weird sharp pain at about 7.5 miles. walked it off a bit and tried again but called it when things did not feel right.
#running
at about mile 3 i switched to 4' on 1' off. this was because my left knee started to act up. kept this up pretty well until a weird sharp pain at about 7.5 miles. walked it off a bit and tried again but called it when things did not feel right.
#running
Always great to see that bugs are quickly fixed.
There's a tiny typo in the second to last paragraph: "Windows NT is something that I _had_ no contact with…"
Content-Type: text/plain; charset=utf-8 did the trick. Something in the twtxt client must have incorrectly guessed ISO-8859-1 or something along those lines when there was no charset advertised in the response header.
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
I agree that it good to clean up the Mastodon re-feeds, but it should also be okay for anyone to spin up a twtxt.txt just for syndicating they stuff from blog or what ever.
The "not receiving replies" could partly be fixed by implementing a working webmentions for twtxt.txt
see it depending on how you open the file, but it's there. Here's a
screenshot with: "bat" vs "cat" vs "twtxt view {link}" :
image
"GET /2024-04-21_01-37-08_931x123.png HTTP/1.1" 200 27569 "-" "Google-Cloud-ML-Vision"
differ... Nope! Still got the new line. 🫠
up and ready! ✅at the same time I'll try and some filler text using a
different terminal. You never know...
Also, you can check the charset again, I did set it up even tho I do observe the problem in my twtxt.txt file on my local machine way before doing scp to the remote one. They show up when I use bat but not when I cat the file nor on neomut.
Also, you can check the charset again, I did set it up even tho I do observe the problem in my twtxt.txt file on my local machine way before doing scp to the remote one. They show up when I use bat but not when I cat the file nor on neomut.
[prologic/go-htmx-demo: A simple Web App written in Go using htmx on the frontend to drive a single-page-app (SPA) experience. - go-htmx-demo - Mills](https://git.mills.io/prologic/go-htmx-demo)
[prologic/go-htmx-demo: A simple Web App written in Go using htmx on the frontend to drive a single-page-app (SPA) experience. - go-htmx-demo - Mills](https://git.mills.io/prologic/go-htmx-demo)
[prologic/go-htmx-demo: A simple Web App written in Go using htmx on the frontend to drive a single-page-app (SPA) experience. - go-htmx-demo - Mills](https://git.mills.io/prologic/go-htmx-demo)
charset. e.g:
$ curl -v -o /dev/null https://twtxt.net/~prologic/twtxt.txt 2>&1 | grep 'content-type'
< content-type: text/plain; charset=utf-8
charset. e.g:
$ curl -v -o /dev/null https://twtxt.net/~prologic/twtxt.txt 2>&1 | grep 'content-type'
< content-type: text/plain; charset=utf-8
charset. e.g:
$ curl -v -o /dev/null https://twtxt.net/~prologic/twtxt.txt 2>&1 | grep 'content-type'
< content-type: text/plain; charset=utf-8
you! and here's a twt with the said random characters, since I've been
cleaning them up manually, earlier before scp-ing my twtxt.txt file. And
maybe a screenshot of how things look in my editor?
screenshot of neovimThose new lines are added automatically as I type (except for the ones
after the screenshot.
you! and here's a twt with the said random characters, since I've been
cleaning them up manually, earlier before scp-ing my twtxt.txt file. And
maybe a screenshot of how things look in my editor?
screenshot of neovimThose new lines are added automatically as I type (except for the ones
after the screenshot.
Checked my locale and it spits out:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
🤷🏽 ... and that only happens when vi, vim or nvim are launched by Jenny to compose a twt.
Checked my locale and it spits out:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
🤷🏽 ... and that only happens when vi, vim or nvim are launched by Jenny to compose a twt.
> WARNING:
>
> You are about to follow a legacy feed, which may not have any kind of engagement. Do you want to continue?