Why? Because I often exchange data via HTTP with old systems and my tooling automatically invokes that indexer/thumbnailer script. 🥴 It’s really annoying when I just see garbage in Netscape 2 or IE5.
Screenshots and videos: https://movq.de/v/348819c482
Why? Because I often exchange data via HTTP with old systems and my tooling automatically invokes that indexer/thumbnailer script. 🥴 It’s really annoying when I just see garbage in Netscape 2 or IE5.
Screenshots and videos: https://movq.de/v/348819c482
Why? Because I often exchange data via HTTP with old systems and my tooling automatically invokes that indexer/thumbnailer script. 🥴 It’s really annoying when I just see garbage in Netscape 2 or IE5.
Screenshots and videos: https://movq.de/v/348819c482
Why? Because I often exchange data via HTTP with old systems and my tooling automatically invokes that indexer/thumbnailer script. 🥴 It’s really annoying when I just see garbage in Netscape 2 or IE5.
Screenshots and videos: https://movq.de/v/348819c482
> These images are not for use with the Microsoft Windows environment. Using these patterns in a Windows environment consitutes a copyright violation.
Someone clearly didn’t like Windows.
> These images are not for use with the Microsoft Windows environment. Using these patterns in a Windows environment consitutes a copyright violation.
Someone clearly didn’t like Windows.
> These images are not for use with the Microsoft Windows environment. Using these patterns in a Windows environment consitutes a copyright violation.
Someone clearly didn’t like Windows.
> These images are not for use with the Microsoft Windows environment. Using these patterns in a Windows environment consitutes a copyright violation.
Someone clearly didn’t like Windows.
> I think you are worrying about a non-issue.
That’s what I do best. 😏
> I think you are worrying about a non-issue.
That’s what I do best. 😏
> I think you are worrying about a non-issue.
That’s what I do best. 😏
> I think you are worrying about a non-issue.
That’s what I do best. 😏
There’s another situation that I’m not quite happy with.
Suppose there’s a twt like this:
2024-08-28T19:57:58Z @person_a @person_b Hey! 👋
There’s no hash, so
--fetch-context won’t do anything at the moment.*Option A*: jenny asks interactively to fetch those feeds *once*.
No thread hash found
Do you want to fetch the entire feed https://foo.example.com/tw.txt? \n y
Do you want to fetch the entire feed gemini://a.b.c/tw.txt? \n n
(Bonus points for skipping feeds that you already follow.)
*Option B*: There could be an external/third-party tool that scans a twt for all mentions and asks the user if they want to *follow* them (permanently). Why an external tool? The thing is, the
follow file has been completely user-managed so far and I kind of want to keep it that way. And if this is an external tool, then users can do all kinds of fancy stuff, like using fzf or whatever. Or it could allow the user to *preview* the feed before following it. I don’t want to have stuff like that in the core program, it depends too much on users’ preferences.To “implement” option B, I’d only add some hints to the docs, maybe an example.
I think I’m leaning towards option B at the moment. 🤔
There’s another situation that I’m not quite happy with.
Suppose there’s a twt like this:
2024-08-28T19:57:58Z @person_a @person_b Hey! 👋
There’s no hash, so
--fetch-context won’t do anything at the moment.*Option A*: jenny asks interactively to fetch those feeds *once*.
No thread hash found
Do you want to fetch the entire feed https://foo.example.com/tw.txt? [Y/n] y
Do you want to fetch the entire feed gemini://a.b.c/tw.txt? [Y/n] n
(Bonus points for skipping feeds that you already follow.)
*Option B*: There could be an external/third-party tool that scans a twt for all mentions and asks the user if they want to *follow* them (permanently). Why an external tool? The thing is, the
follow file has been completely user-managed so far and I kind of want to keep it that way. And if this is an external tool, then users can do all kinds of fancy stuff, like using fzf or whatever. Or it could allow the user to *preview* the feed before following it. I don’t want to have stuff like that in the core program, it depends too much on users’ preferences.To “implement” option B, I’d only add some hints to the docs, maybe an example.
I think I’m leaning towards option B at the moment. 🤔
There’s another situation that I’m not quite happy with.
Suppose there’s a twt like this:
2024-08-28T19:57:58Z @person_a @person_b Hey! 👋
There’s no hash, so
--fetch-context won’t do anything at the moment.*Option A*: jenny asks interactively to fetch those feeds *once*.
No thread hash found
Do you want to fetch the entire feed https://foo.example.com/tw.txt? [Y/n] y
Do you want to fetch the entire feed gemini://a.b.c/tw.txt? [Y/n] n
(Bonus points for skipping feeds that you already follow.)
*Option B*: There could be an external/third-party tool that scans a twt for all mentions and asks the user if they want to *follow* them (permanently). Why an external tool? The thing is, the
follow file has been completely user-managed so far and I kind of want to keep it that way. And if this is an external tool, then users can do all kinds of fancy stuff, like using fzf or whatever. Or it could allow the user to *preview* the feed before following it. I don’t want to have stuff like that in the core program, it depends too much on users’ preferences.To “implement” option B, I’d only add some hints to the docs, maybe an example.
I think I’m leaning towards option B at the moment. 🤔
There’s another situation that I’m not quite happy with.
Suppose there’s a twt like this:
2024-08-28T19:57:58Z @person_a @person_b Hey! 👋
There’s no hash, so
--fetch-context won’t do anything at the moment.*Option A*: jenny asks interactively to fetch those feeds *once*.
No thread hash found
Do you want to fetch the entire feed https://foo.example.com/tw.txt? [Y/n] y
Do you want to fetch the entire feed gemini://a.b.c/tw.txt? [Y/n] n
(Bonus points for skipping feeds that you already follow.)
*Option B*: There could be an external/third-party tool that scans a twt for all mentions and asks the user if they want to *follow* them (permanently). Why an external tool? The thing is, the
follow file has been completely user-managed so far and I kind of want to keep it that way. And if this is an external tool, then users can do all kinds of fancy stuff, like using fzf or whatever. Or it could allow the user to *preview* the feed before following it. I don’t want to have stuff like that in the core program, it depends too much on users’ preferences.To “implement” option B, I’d only add some hints to the docs, maybe an example.
I think I’m leaning towards option B at the moment. 🤔
There’s another situation that I’m not quite happy with.
Suppose there’s a twt like this:
2024-08-28T19:57:58Z @person_a @person_b Hey! 👋
There’s no hash, so
--fetch-context won’t do anything at the moment.*Option A*: jenny asks interactively to fetch those feeds *once*.
No thread hash found
Do you want to fetch the entire feed https://foo.example.com/tw.txt? [Y/n] y
Do you want to fetch the entire feed gemini://a.b.c/tw.txt? [Y/n] n
(Bonus points for skipping feeds that you already follow.)
*Option B*: There could be an external/third-party tool that scans a twt for all mentions and asks the user if they want to *follow* them (permanently). Why an external tool? The thing is, the
follow file has been completely user-managed so far and I kind of want to keep it that way. And if this is an external tool, then users can do all kinds of fancy stuff, like using fzf or whatever. Or it could allow the user to *preview* the feed before following it. I don’t want to have stuff like that in the core program, it depends too much on users’ preferences.To “implement” option B, I’d only add some hints to the docs, maybe an example.
I think I’m leaning towards option B at the moment. 🤔
(I just looked it up, your “winter” is barely cooler than our “summer”, according to those fancy climate diagrams and my rough understanding of them. 😅)
(I just looked it up, your “winter” is barely cooler than our “summer”, according to those fancy climate diagrams and my rough understanding of them. 😅)
(I just looked it up, your “winter” is barely cooler than our “summer”, according to those fancy climate diagrams and my rough understanding of them. 😅)
(I just looked it up, your “winter” is barely cooler than our “summer”, according to those fancy climate diagrams and my rough understanding of them. 😅)
> I am ready for our winter too, you know, that whole week
lol 😅
> I am ready for our winter too, you know, that whole week
lol 😅
> I am ready for our winter too, you know, that whole week
lol 😅
> I am ready for our winter too, you know, that whole week
lol 😅
main. 👌
main. 👌
main. 👌
main. 👌
Maybe that’s a mutt vs. neomutt thing?
Maybe that’s a mutt vs. neomutt thing?
Maybe that’s a mutt vs. neomutt thing?
Maybe that’s a mutt vs. neomutt thing?
startinsert, didn’t even know that existed, tbh. 😅It doesn’t work because the editor command is currently not run through
sh -c ..., i.e. it is supposed to be just a path like /usr/bin/vim. I was just stumped by this myself and I think I’ll soon push a patch to allow setting something like vim -c foo.In the meantime, your best option is probably putting this in your
.vimrc:au BufRead,BufNewFile jenny-posting.eml normal $
(I use something similar to disable hard text wrapping after 72 chars for twtxt postings.)
startinsert, didn’t even know that existed, tbh. 😅It doesn’t work because the editor command is currently not run through
sh -c ..., i.e. it is supposed to be just a path like /usr/bin/vim. I was just stumped by this myself and I think I’ll soon push a patch to allow setting something like vim -c foo.In the meantime, your best option is probably putting this in your
.vimrc:au BufRead,BufNewFile jenny-posting.eml normal $
(I use something similar to disable hard text wrapping after 72 chars for twtxt postings.)
startinsert, didn’t even know that existed, tbh. 😅It doesn’t work because the editor command is currently not run through
sh -c ..., i.e. it is supposed to be just a path like /usr/bin/vim. I was just stumped by this myself and I think I’ll soon push a patch to allow setting something like vim -c foo.In the meantime, your best option is probably putting this in your
.vimrc:au BufRead,BufNewFile jenny-posting.eml normal $
(I use something similar to disable hard text wrapping after 72 chars for twtxt postings.)
startinsert, didn’t even know that existed, tbh. 😅It doesn’t work because the editor command is currently not run through
sh -c ..., i.e. it is supposed to be just a path like /usr/bin/vim. I was just stumped by this myself and I think I’ll soon push a patch to allow setting something like vim -c foo.In the meantime, your best option is probably putting this in your
.vimrc:au BufRead,BufNewFile jenny-posting.eml normal $
(I use something similar to disable hard text wrapping after 72 chars for twtxt postings.)
VISUAL environment variable). It probably should. I’ll fix it.What’s the goal, though? I usually hit
Shift-A in Vim to append text to the end of the line. Is that what you want? 😅
VISUAL environment variable). It probably should. I’ll fix it.What’s the goal, though? I usually hit
Shift-A in Vim to append text to the end of the line. Is that what you want? 😅
VISUAL environment variable). It probably should. I’ll fix it.What’s the goal, though? I usually hit
Shift-A in Vim to append text to the end of the line. Is that what you want? 😅
VISUAL environment variable). It probably should. I’ll fix it.What’s the goal, though? I usually hit
Shift-A in Vim to append text to the end of the line. Is that what you want? 😅
#tsvhqdq
I don’t see them being used in the wild anymore. But if you happen to fetch really old feeds (or some archived feeds), things might break a little.
#tsvhqdq
I don’t see them being used in the wild anymore. But if you happen to fetch really old feeds (or some archived feeds), things might break a little.
#tsvhqdq
I don’t see them being used in the wild anymore. But if you happen to fetch really old feeds (or some archived feeds), things might break a little.
#tsvhqdq
I don’t see them being used in the wild anymore. But if you happen to fetch really old feeds (or some archived feeds), things might break a little.
I’m so glad the temperatures were down a bit. Went on a long walk as well, first time in weeks. And there were so few cars yesterday! It was surprisingly quiet.
I’m so glad the temperatures were down a bit. Went on a long walk as well, first time in weeks. And there were so few cars yesterday! It was surprisingly quiet.
I’m so glad the temperatures were down a bit. Went on a long walk as well, first time in weeks. And there were so few cars yesterday! It was surprisingly quiet.
I’m so glad the temperatures were down a bit. Went on a long walk as well, first time in weeks. And there were so few cars yesterday! It was surprisingly quiet.
fetch-context branch. This integrates the whole thing into mutt/jenny.You will want to configure a new mutt hotkey, similar to the “reply” hotkey:
macro index,pager
"Try to fetch context of current twt, like a missing root twt"
This pipes the mail to
jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If there’s no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)The whole thing looks like this:
https://movq.de/v/0d0e76a180/jenny.mp4
In other words, when there’s a missing root twt, you press a hotkey to fetch it, done.
I think I like this version better. 🤔
(This needs a lot of testing. 😆)
fetch-context branch. This integrates the whole thing into mutt/jenny.You will want to configure a new mutt hotkey, similar to the “reply” hotkey:
macro index,pager
"Try to fetch context of current twt, like a missing root twt"
This pipes the mail to
jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If there’s no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)The whole thing looks like this:
https://movq.de/v/0d0e76a180/jenny.mp4
In other words, when there’s a missing root twt, you press a hotkey to fetch it, done.
I think I like this version better. 🤔
(This needs a lot of testing. 😆)
fetch-context branch. This integrates the whole thing into mutt/jenny.You will want to configure a new mutt hotkey, similar to the “reply” hotkey:
macro index,pager
"Try to fetch context of current twt, like a missing root twt"
This pipes the mail to
jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If there’s no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)The whole thing looks like this:
https://movq.de/v/0d0e76a180/jenny.mp4
In other words, when there’s a missing root twt, you press a hotkey to fetch it, done.
I think I like this version better. 🤔
(This needs a lot of testing. 😆)
fetch-context branch. This integrates the whole thing into mutt/jenny.You will want to configure a new mutt hotkey, similar to the “reply” hotkey:
macro index,pager
"Try to fetch context of current twt, like a missing root twt"
This pipes the mail to
jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If there’s no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)The whole thing looks like this:
https://movq.de/v/0d0e76a180/jenny.mp4
In other words, when there’s a missing root twt, you press a hotkey to fetch it, done.
I think I like this version better. 🤔
(This needs a lot of testing. 😆)