# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 196269
# self = https://watcher.sour.is?offset=169456
# next = https://watcher.sour.is?offset=169556
# prev = https://watcher.sour.is?offset=169356
Pinellas Trail Challenge: 36.30 miles, 00:14:47 average pace, 08:56:28 duration
DNF'd, but had a great time! i could have walked it out the last ten miles and still made the cut-off but after doing the math i would not have been done until about 1900 and we had guests visiting from out of town and i did not want to be even more of a wreck while entertaining. met a lot of great people and happy for the challenge.
#running #race
[47°09′30″S, 126°43′29″W] Dosimeter malfunction
[47°09′27″S, 126°43′12″W] Reading: 0.80000 PPM
@prologic errors are made everyday. Also, many developers try to get around the rules, and they get caught. Nothing to see here, moving on. 🤭
@slashdot IMO the problem isn't "Apple"™ the company, per se, it's the complexity and size of the organization. It's large, it's complex, you will have large sets of "people" that follow the "rules" as written without any leeway whatsoever or ability to apply "intent".
@slashdot IMO the problem isn't "Apple"™ the company, per se, it's the complexity and size of the organization. It's large, it's complex, you will have large sets of "people" that follow the "rules" as written without any leeway whatsoever or ability to apply "intent".
🧮 USERS:1 FEEDS:2 TWTS:1078 ARCHIVED:78117 CACHE:2455 FOLLOWERS:17 FOLLOWING:14
@quark probably not with the OpenSSH tools themselves but perhaps with the OpenSSL tools using the same key.
@quark probably not with the OpenSSH tools themselves but perhaps with the OpenSSL tools using the same key.
@off_grid_living This is so true! Grandpa used to say this all the time too. Especially about tomatoes 🤣
@off_grid_living This is so true! Grandpa used to say this all the time too. Especially about tomatoes 🤣
Further thinking on it, this might not be possible at all.
Further thinking on it, this might not be possible at all.
@bender Nope, still don't have a mobile one. Works extremely well for me. :-)
Does anyone knows how to clear sign a file with an SSH key? Clear sign, not a detached signature.
Does anyone knows how to clear sign a file with an SSH key? Clear sign, not a detached signature.
[47°09′32″S, 126°43′34″W] Transfer aborted
@movq LOL, well, great things come out of that worry, I can tell that much. Keep being you! :-)
@movq LOL, well, great things come out of that worry, I can tell that much. Keep being you! :-)
@lyse not even your phone? I can't go anywhere without mine, but wouldn't be surprised if not everybody did the same.
@quark
> I think you are worrying about a non-issue.
That’s what I do best. 😏
@quark
> I think you are worrying about a non-issue.
That’s what I do best. 😏
@quark
> I think you are worrying about a non-issue.
That’s what I do best. 😏
@quark
> I think you are worrying about a non-issue.
That’s what I do best. 😏
@movq @bender Haha, great! :-)
Just returned from an evening walk. We met a young slow worm, a bunch of small frogs, about the width of a pointing finger and a bucket load of sweat. It's bloody hot and humid. Also, heaps of ripped trash bags in the forest and lake. :-( No photos, it was too exhausting to even carry my pocket camera.
moving to a new town is lonely, i think i'm lonely. maybe that's why things have been so hard..
@movq I think you are worrying about a non-issue. I see nothing to do on your example twt, because there is no context. Furthermore, if I wanted to follow the feed, everything I need is already on that twt example. :-)
@movq I think you are worrying about a non-issue. I see nothing to do on your example twt, because there is no context. Furthermore, if I wanted to follow the feed, everything I need is already on that twt example. :-)
@mckinley 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).
@mckinley 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).
@aelaraji @quark Yep, I like it as well. 😅
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. 🤔
@aelaraji @quark Yep, I like it as well. 😅
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. 🤔
@aelaraji @quark Yep, I like it as well. 😅
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. 🤔
@aelaraji @quark Yep, I like it as well. 😅
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. 🤔
@aelaraji @quark Yep, I like it as well. 😅
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. 🤔
@abucci their main question is worrisome:
> “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
@abucci their main question is worrisome:
> “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
[47°09′03″S, 126°43′54″W] Transfer 25% complete...
@aelaraji so lovely, ain't it? A simple keystroke, and your "mystery" is solved. :-)
@aelaraji so lovely, ain't it? A simple keystroke, and your "mystery" is solved. :-)
@movq Yeah we're about 3,054.26km from the equator but clearly that's not far enough 🤣
@movq Yeah we're about 3,054.26km from the equator but clearly that's not far enough 🤣
@prologic The equator is your enemy. Stay away from it, as far as you can! 😱
(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. 😅)
@prologic The equator is your enemy. Stay away from it, as far as you can! 😱
(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. 😅)
@prologic The equator is your enemy. Stay away from it, as far as you can! 😱
(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. 😅)
@prologic The equator is your enemy. Stay away from it, as far as you can! 😱
(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. 😅)
@bender Yeah just in spring right now and it's already disgustingly hot 🥵
@bender Yeah just in spring right now and it's already disgustingly hot 🥵
@lyse I love it! I love German! 😊
@prologic consider yourself lucky it is "winter" now, right? LOL. On a more serious note, it is upsetting that the smartest animals on the planet are at fault, and there is very little being done about it.
[47°09′26″S, 126°43′14″W] Waiting for carrier
[47°09′52″S, 126°43′04″W] Transponder still failing -- switching to analog communication
[47°09′56″S, 126°43′08″W] Transponder malfunction
Uggh it's 33C right now and 60% humidity 🥵
Uggh it's 33C right now and 60% humidity 🥵
🧮 USERS:1 FEEDS:2 TWTS:1077 ARCHIVED:78103 CACHE:2449 FOLLOWERS:17 FOLLOWING:14
[47°09′12″S, 126°43′25″W] Not enough data -- sampling finished
@lyse Oh my goodness...! 🤣
@lyse Oh my goodness...! 🤣
@lyse Oh my goodness...! 🤣
@lyse Oh my goodness...! 🤣
@movq Lol, someone just showed me this brilliant German (Saxon, actually) song. The title Hitzetodcheck translates to "heat death check". Sorry to all non-German speakers. https://www.youtube.com/watch?v=1qHH3RO_X34
I'm also ready absolutely ready for winter.
@quark 😆 I'm trying so hard to overcome the temptations.
@quark 😆 I'm trying so hard to overcome the temptations.
@quark 😆 I'm trying so hard to overcome the temptations.
I'm SO enjoying the new jenny --fetch-context 😁
I'm SO enjoying the new jenny --fetch-context 😁
I'm SO enjoying the new jenny --fetch-context 😁
@aelaraji hehehehe. Enjoy, but careful with sugary stuff! :-)
@aelaraji hehehehe. Enjoy, but careful with sugary stuff! :-)
[47°09′05″S, 126°43′23″W] Re-taking samples
@prologic what made you make such "financially sound" recommendation? Have you switched jobs, and are now a Financial Advisor? :-P
@prologic what made you make such "financially sound" recommendation? Have you switched jobs, and are now a Financial Advisor? :-P
@quark Oh dear, 87% humidity probably don’t feel great, either. 🥴 That’s what I have in the bathroom after leaving the shower. 😂
> I am ready for our winter too, you know, that whole week
lol 😅
@quark Oh dear, 87% humidity probably don’t feel great, either. 🥴 That’s what I have in the bathroom after leaving the shower. 😂
> I am ready for our winter too, you know, that whole week
lol 😅
@quark Oh dear, 87% humidity probably don’t feel great, either. 🥴 That’s what I have in the bathroom after leaving the shower. 😂
> I am ready for our winter too, you know, that whole week
lol 😅
@quark Oh dear, 87% humidity probably don’t feel great, either. 🥴 That’s what I have in the bathroom after leaving the shower. 😂
> I am ready for our winter too, you know, that whole week
lol 😅
@movq wow! We are "lucky" today, only 27°C here, 87% humidity, overcast, and raining sporadically. Thanks to the rain our temperatures aren't high, but muggy nevertheless. I am ready for our winter too, you know, that whole week. LOL.
@movq wow! We are "lucky" today, only 27°C here, 87% humidity, overcast, and raining sporadically. Thanks to the rain our temperatures aren't high, but muggy nevertheless. I am ready for our winter too, you know, that whole week. LOL.
35°C and rising … can haz winter?
35°C and rising … can haz winter?
35°C and rising … can haz winter?
35°C and rising … can haz winter?
[47°09′00″S, 126°43′19″W] Taking samples
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_22929-08-2024_09-07-23.jpg) #catsoftwtxt