"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?
I.e: How to deal with or reduce noise from legacy feeds.
I.e: How to deal with or reduce noise from legacy feeds.
I.e: How to deal with or reduce noise from legacy feeds.
But I broke something trying to get rid of the random characters showing on my twts as mentioned here #k7tcqwq.
I taught it was as easy as swapping the '\u2028' in jenny's new_twt_from_file function but there's a reason I'm not a developer (yet) ๐
It kinda got rid of them in a way but broke the new lines in the process. So I put things back the way the were till I figure out something else.
But I broke something trying to get rid of the random characters showing on my twts as mentioned here #k7tcqwq.
I taught it was as easy as swapping the '\\u2028' in jenny's new_twt_from_file function but there's a reason I'm not a developer (yet) ๐
It kinda got rid of them in a way but broke the new lines in the process. So I put things back the way the were till I figure out something else.
But I broke something trying to get rid of the random characters showing on my twts as mentioned here #k7tcqwq.
I taught it was as easy as swapping the '\u2028' in jenny's new_twt_from_file function but there's a reason I'm not a developer (yet) ๐
It kinda got rid of them in a way but broke the new lines in the process. So I put things back the way the were till I figure out something else.
> 2023-09-02T17:30:15Z\tHi! I'll be microblogging from ciberlandia.pt from now on. What does that mean? If you want to follow me via mastodon you can, at @marado , if you want to follow me via twtxt you can keep following me via at https://tilde.pt/~marado/twtxt.txt . See you on the "other side"!
> 2023-09-02T17:30:15Z Hi! I'll be microblogging from ciberlandia.pt from now on. What does that mean? If you want to follow me via mastodon you can, at @marado , if you want to follow me via twtxt you can keep following me via at https://tilde.pt/~marado/twtxt.txt . See you on the "other side"!
Let me know if y'all have any other candidates you'd like me to add to the blocked domain list?
Let me know if y'all have any other candidates you'd like me to add to the blocked domain list?
Let me know if y'all have any other candidates you'd like me to add to the blocked domain list?