I might be spoiled and very privileged here. Even though my PC is almost 12 years old now, it *does* have an SSD and tons of RAM (i.e., lots of I/O cache), so starting mutt and opening the mailbox takes about 1-2 seconds here. I hardly even notice it. But I understand that not everybody has fast machines like that. 🫤
I might be spoiled and very privileged here. Even though my PC is almost 12 years old now, it *does* have an SSD and tons of RAM (i.e., lots of I/O cache), so starting mutt and opening the mailbox takes about 1-2 seconds here. I hardly even notice it. But I understand that not everybody has fast machines like that. 🫤
I might be spoiled and very privileged here. Even though my PC is almost 12 years old now, it *does* have an SSD and tons of RAM (i.e., lots of I/O cache), so starting mutt and opening the mailbox takes about 1-2 seconds here. I hardly even notice it. But I understand that not everybody has fast machines like that. 🫤
I might be spoiled and very privileged here. Even though my PC is almost 12 years old now, it *does* have an SSD and tons of RAM (i.e., lots of I/O cache), so starting mutt and opening the mailbox takes about 1-2 seconds here. I hardly even notice it. But I understand that not everybody has fast machines like that. 🫤
$HOME/.cache/mutt/twtxt/ directory for example and then add this set header_cache = $HOME/.cache/mutt/twtxt/ to your muttrc (the one you have set up for or use with jenny if you're using different ones). That's what helped me with that.Ref: http://www.mutt.org/doc/manual/#header-caching
$HOME/.cache/mutt/twtxt/ directory for example and then add this set header_cache = $HOME/.cache/mutt/twtxt/ to your muttrc (the one you have set up for or use with jenny if you're using different ones). That's what helped me with that.Ref: http://www.mutt.org/doc/manual/#header-caching
$HOME/.cache/mutt/twtxt/ directory for example and then add this set header_cache = $HOME/.cache/mutt/twtxt/ to your muttrc (the one you have set up for or use with jenny if you're using different ones). That's what helped me with that.Ref: http://www.mutt.org/doc/manual/#header-caching
@movq??
@movq??
yarnd pod here around ~2m on average to fetch, process and cache ~700 feeds.
yarnd pod here around ~2m on average to fetch, process and cache ~700 feeds.
@<bender bender@twtxt.net> is currently wrong. The 2nd part of a mention is currently required to be a full absolute URI.
@<bender bender@twtxt.net> is currently wrong. The 2nd part of a mention is currently required to be a full absolute URI.
$ bat https://twtxt.net/twt/dn2zlga | jq '.'
{
"twter": {
"nick": "Codebuzz",
"uri": "https://www.codebuzz.nl/twtxt.txt",
"avatar": "https://www.codebuzz.nl/twtxt-avatar-800.jpg"
},
"text": "(#q5rg3ea) Hey, @<bender bender@twtxt.net> I know. Just wondering the kind of apps or software and how you all stay up to date in conversations. Is it through webmentions?",
"created": "2024-10-30T22:12:24Z",
"markdownText": "(#q5rg3ea) Hey, @<bender bender@twtxt.net> I know. Just wondering the kind of apps or software and how you all stay up to date in conversations. Is it through webmentions?",
"hash": "dn2zlga",
"tags": [
"q5rg3ea"
],
"subject": "(#q5rg3ea)",
"mentions": [],
"links": []
}
$ bat https://twtxt.net/twt/dn2zlga | jq '.'
{
"twter": {
"nick": "Codebuzz",
"uri": "https://www.codebuzz.nl/twtxt.txt",
"avatar": "https://www.codebuzz.nl/twtxt-avatar-800.jpg"
},
"text": "(#q5rg3ea) Hey, @<bender bender@twtxt.net> I know. Just wondering the kind of apps or software and how you all stay up to date in conversations. Is it through webmentions?",
"created": "2024-10-30T22:12:24Z",
"markdownText": "(#q5rg3ea) Hey, @<bender bender@twtxt.net> I know. Just wondering the kind of apps or software and how you all stay up to date in conversations. Is it through webmentions?",
"hash": "dn2zlga",
"tags": [
"q5rg3ea"
],
"subject": "(#q5rg3ea)",
"mentions": [],
"links": []
}
@<bender bender@twtxt.net> on my side ...
@<bender bender@twtxt.net> on my side ...
@<bender bender@twtxt.net> on my side ...
There are no web mentions here, and no notifications. It isn’t Mastodon; if you want to see if someone wrote something new, or replied to you, you need to open your client.
> (#q5rg3ea) Some interesting responses, hearing some with (intentional) manual labour involved. I am modifying @sorenpeter Timeline. Still have things I want, and also pondering what would help others.
> I use Mastodon similarly. I write posts in Vim until I’m happy with them. Then copy-and-paste to the browser …
You could use toot, and bypass the browser altogether.
> […] and then manually push it to my web servers […]
Funny, I also push manually, kind of. My
publish_command includes a [Y/n] question and I very often hit n, so I can keep writing a thread until it’s finished. And sometimes I delete stuff again and never publish it. 😅I use Mastodon similarly. I write posts in Vim until I’m happy with them. Then copy-and-paste to the browser …
> […] and then manually push it to my web servers […]
Funny, I also push manually, kind of. My
publish_command includes a [Y/n] question and I very often hit n, so I can keep writing a thread until it’s finished. And sometimes I delete stuff again and never publish it. 😅I use Mastodon similarly. I write posts in Vim until I’m happy with them. Then copy-and-paste to the browser …
> \n and then manually push it to my web servers \n
Funny, I also push manually, kind of. My
publish_command includes a [Y/n] question and I very often hit n, so I can keep writing a thread until it’s finished. And sometimes I delete stuff again and never publish it. 😅I use Mastodon similarly. I write posts in Vim until I’m happy with them. Then copy-and-paste to the browser …
> […] and then manually push it to my web servers […]
Funny, I also push manually, kind of. My
publish_command includes a [Y/n] question and I very often hit n, so I can keep writing a thread until it’s finished. And sometimes I delete stuff again and never publish it. 😅I use Mastodon similarly. I write posts in Vim until I’m happy with them. Then copy-and-paste to the browser …
> […] and then manually push it to my web servers […]
Funny, I also push manually, kind of. My
publish_command includes a [Y/n] question and I very often hit n, so I can keep writing a thread until it’s finished. And sometimes I delete stuff again and never publish it. 😅I use Mastodon similarly. I write posts in Vim until I’m happy with them. Then copy-and-paste to the browser …
First line.
Second line.
Third line.
I believe this, on CSS, is causing it:
pre>code {
padding:0 .25rem;
}
nothing to note.
#running
nothing to note.
#running
nothing to note.
#running