agevault uses age, allegedly very secure (aiming to replace pgp/gpg). Comparing it with gocryptfs, from the user perspective, agevault seems simpler, though CLI *exclusive*. As the repository states, "Like age, it features no config options, allowing for a straightforward secure flow". It would also run in all major OS platforms out of the box.But
agevault is also very new. Though age has been around for a while now, I don't see an "audited" link (neither on agevault, nor age).
agevault uses age, allegedly very secure (aiming to replace pgp/gpg). Comparing it with gocryptfs, from the user perspective, agevault seems simpler, though CLI *exclusive*. As the repository states, "Like age, it features no config options, allowing for a straightforward secure flow". It would also run in all major OS platforms out of the box.But
agevault is also very new. Though age has been around for a while now, I don't see an "audited" link (neither on agevault, nor age).
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. 🤔
> “The main question is, does it disappear during this re-entry?” says Löhle. “Is everything evaporating, or are there pieces that eventually impact on the ground?”
>
> He expects some parts, such as the satellite’s fuel tanks, to survive. “You could learn from the re-entry that if you build a fuel tank differently, it can break up,” he says.
Archived article at: https://archive.ph/WdUvx
> “The main question is, does it disappear during this re-entry?” says Löhle. “Is everything evaporating, or are there pieces that eventually impact on the ground?”
>
> He expects some parts, such as the satellite’s fuel tanks, to survive. “You could learn from the re-entry that if you build a fuel tank differently, it can break up,” he says.
Archived article at: https://archive.ph/WdUvx
(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'm also ready absolutely ready for winter.
jenny --fetch-context 😁
jenny --fetch-context 😁
jenny --fetch-context 😁
> 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 😅
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_22929-08-2024_09-07-23.jpg) #catsoftwtxt
$ curl 'https://twtxt.net/external?uri=https://google.com&nick=lovetocode999'
Feed Not Found
After nuking that from my cache. I forgot to nuke my own cache myself because it's quite destructive and takes a few mins to rebuild on my pod 🤣 There's a tool in
tools for deleting a specific feed from the cache that I've been using.
$ curl 'https://twtxt.net/external?uri=https://google.com&nick=lovetocode999'
Feed Not Found
After nuking that from my cache. I forgot to nuke my own cache myself because it's quite destructive and takes a few mins to rebuild on my pod 🤣 There's a tool in
tools for deleting a specific feed from the cache that I've been using.
README!
README!
main. 👌
main. 👌
main. 👌
main. 👌
fetch-context branch? It works great!
fetch-context branch? It works great!