# 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 196240
# self = https://watcher.sour.is?offset=173385
# next = https://watcher.sour.is?offset=173485
# prev = https://watcher.sour.is?offset=173285
[47°09′22″S, 126°43′49″W] Reading: 1.40 Sv
@doesnm Much appreciated!! 🙏 I'll go through the files and see if I can understand any of it. I might learn a thing or two along the way.
@doesnm Much appreciated!! 🙏 I'll go through the files and see if I can understand any of it. I might learn a thing or two along the way.
@doesnm Much appreciated!! 🙏 I'll go through the files and see if I can understand any of it. I might learn a thing or two along the way.
thank you gemini for continuing to inspire me to think smol
[47°09′15″S, 126°43′12″W] Transfer aborted
****
Me estaba comiendo una sopa y ¡zas!, ahí estaba, Rafa Nadal. ⌘ Read more****
@movq Yeah this is why thin @anth is that and that any v2 spec we get around to _actually_ publishing with far better quality than the bullshit half-baked attempt I tried to 🤣; should just _mandate_ utf-8 period. Just assume it to be true, there is no other content encoding we should ever support 😅
@movq Yeah this is why thin @anth is that and that any v2 spec we get around to _actually_ publishing with far better quality than the bullshit half-baked attempt I tried to 🤣; should just _mandate_ utf-8 period. Just assume it to be true, there is no other content encoding we should ever support 😅
@lyse Ahh, I see. So it’s not really a drama. 😅
(When the spec says “content is UTF-8”, then it kind of follows for me that I should set Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)
@lyse Ahh, I see. So it’s not really a drama. 😅
(When the spec says “content is UTF-8”, then it kind of follows for me that I should set Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)
@lyse Ahh, I see. So it’s not really a drama. 😅
(When the spec says “content is UTF-8”, then it kind of follows for me that I should set Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)
@lyse Ahh, I see. So it’s not really a drama. 😅
(When the spec says “content is UTF-8”, then it kind of follows for me that I should set Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)
[47°09′10″S, 126°43′55″W] Transfer 75% complete...
@doesnm Nice 👌 I'll send you a message later 😅
@doesnm Nice 👌 I'll send you a message later 😅
Im also have running saltyd at doesnm.cc (delegated to salty-doesnm.p.projectsegfau.lt) but maybe i do something wrong
[47°09′30″S, 126°43′02″W] Transfer 50% complete...
Anyone has saltyd actually up and running? my deployment was a mess ... will tell you all about it when I wake up 😅
Anyone has saltyd actually up and running? my deployment was a mess ... will tell you all about it when I wake up 😅
Anyone has saltyd actually up and running? my deployment was a mess ... will tell you all about it when I wake up 😅
[47°09′39″S, 126°43′14″W] Transfer 25% complete...
🧮 USERS:1 FEEDS:2 TWTS:1119 ARCHIVED:79896 CACHE:2501 FOLLOWERS:17 FOLLOWING:14
Just to be clear, I'm 100% for mandating UTF-8 and only UTF-8. Nothing else. Exactly how it has always been.
I just like to send a proper Content-Type stating the right encoding to be a good web citizen. That's all. :-)
Righto @anth, v2 is up again for me:
> Clients (and human readers) just assume a flat threading
> structure by default, read things in order […]
I might misunderstand this, but I slightly disagree. Personally, I like to look at the tree structure and my client also does present me the conversation tree as an actual tree, not a flat list. Yes, this gets messy when there are a lot of branches and long messages, but I managed to live with that. Doesn't happen very often. Anyway, just a personal preference. Nothing to really worry.
> The v2 spec requires each reply to re-calculate the hash
> of the specific entry I’m replying to […]
Hmmmm, where do you read that the client has to re-calculate the hash on reply? (Sorry, I'm probably just not getting your point here in the entire paragraph.)
> Clients should not be expected to track conversations back
> across forking points […]
I agree. It totally depends on the client.
Righto @anth, v2 is up again for me:
> Clients (and human readers) just assume a flat threading
> structure by default, read things in order \n
I might misunderstand this, but I slightly disagree. Personally, I like to look at the tree structure and my client also does present me the conversation tree as an actual tree, not a flat list. Yes, this gets messy when there are a lot of branches and long messages, but I managed to live with that. Doesn't happen very often. Anyway, just a personal preference. Nothing to really worry.
> The v2 spec requires each reply to re-calculate the hash
> of the specific entry I’m replying to \n
Hmmmm, where do you read that the client has to re-calculate the hash on reply? (Sorry, I'm probably just not getting your point here in the entire paragraph.)
> Clients should not be expected to track conversations back
> across forking points \n
I agree. It totally depends on the client.
@movq If my memory serves me right, I think v2 doesn't mention UTF-8 at all. Then I came along and noted that the Content-Type: text/plain might be not enough, as the HTTP spec defaults to Latin1 or whatever, not UTF-8. So there is a gap or room for incorrect interpretation. I could be wrong, but I understand @anth's comment that he doesn't want to even have a Content-Type header in the first place.
I reckon it should be optional, but when deciding to sending one, it should be Content-Type: text/plain; charset=utf-8. That also helps browsers pick up the right encoding right away without guessing wrong (basically always happens with Firefox here). That aids people who read raw feeds in browsers for debugging or what not. (I sometimes do that to decide if there is enough interesting content to follow the feed at hand.)
Merci, @movq! Back to gray this afternoon again, mostly dry, though.
[47°09′20″S, 126°43′05″W] Waiting for carrier
@anth (I’m also a bit confused by the UTF-8 topic. I thought that the original twtxt spec has *always* mandated UTF-8 for the content. Why’s that an issue now? 😅 Granted, my client also got this wrong in the past, but it has been fixed ~3 years ago.)~
@anth (I’m also a bit confused by the UTF-8 topic. I thought that the original twtxt spec has *always* mandated UTF-8 for the content. Why’s that an issue now? 😅 Granted, my client also got this wrong in the past, but it has been fixed ~3 years ago.)~
@anth (I’m also a bit confused by the UTF-8 topic. I thought that the original twtxt spec has *always* mandated UTF-8 for the content. Why’s that an issue now? 😅 Granted, my client also got this wrong in the past, but it has been fixed ~3 years ago.)~
@anth (I’m also a bit confused by the UTF-8 topic. I thought that the original twtxt spec has *always* mandated UTF-8 for the content. Why’s that an issue now? 😅 Granted, my client also got this wrong in the past, but it has been fixed ~3 years ago.)~
@lyse That looks like lovely weather. We had nothing but rain. 🥴
@lyse That looks like lovely weather. We had nothing but rain. 🥴
@lyse That looks like lovely weather. We had nothing but rain. 🥴
@lyse That looks like lovely weather. We had nothing but rain. 🥴
Cool, @anth, thanks for the followup! I have to reread the original v2 in order to really follow your explanation, but that document seems to be offline at the moment. I'll try again later. :-)
Oh no, @xuu. :-( Speedy recovery and I hope you still miss out on long-covid.
#catsoftwtxt
#catsoftwtxt
[47°09′35″S, 126°43′06″W] Transponder still failing -- switching to analog communication
i might take the plunge and rebuild my server this weekend
What is #foo ? How to cook #foo ? How to eat #foo ?
[47°09′06″S, 126°43′49″W] Transponder jammed
[47°09′24″S, 126°43′46″W] Transponder still failing
@lyse Oh wow that photo looks sick 🤣
@lyse Oh wow that photo looks sick 🤣
[47°09′25″S, 126°43′07″W] Transponder malfunction
🧮 USERS:1 FEEDS:2 TWTS:1118 ARCHIVED:79884 CACHE:2512 FOLLOWERS:17 FOLLOWING:14
Ugh! May the afflicted get well soon!
[47°09′16″S, 126°43′59″W] Reading: 0.70 Sv
Well poop. Covid coming to visit for a second time.
Well poop. Covid coming to visit for a second time.
[47°09′23″S, 126°43′20″W] Dosimeter fixed
> There is a pressing need to hold Israel accountable, not only for its longstanding violations of international law, but specifically for its longstanding refusal to abide by its Charter obligations. In the face of this recalcitrance, the UN must move towards expelling Israel from the organization, not only because the UN exists to uphold international law, but also to maintain the UN’s integrity as an organization. The persistent, open violations by Israel of binding UNSC resolutions cannot go unpunished. The current situation, where Israel openly accuses the UN of bias, refuses to cooperate with the organization on multitude levels, defies binding orders of the ICJ, physically attacks UN premises and staff, and even moves towards designating a UN agency as a terrorist organization, is a clear threat to the authority of the UN – an issue which the UNSC raised explicitly in the case of South Africa. To allow the situation to continue would show that international legal norms, and rules of the UN binding member states, are applied on the basis of double standards: specifically, that states allied to powerful Western countries are afforded impunity. https://opiniojuris.org/2024/10/09/israel-must-be-expelled-from-the-united-nations/
[47°09′05″S, 126°43′11″W] Dosimeter still failing
I know no client support it (yet) - but it could be the future 😅
I know no client support it (yet) - but it could be the future 😅
I know no client support it (yet) - but it could be the future 😅
I know no client support it (yet) - but it could be the future 😅
this looks strange in twet xD: blue highlight of 2024-10-09T08:11:00Z(prologic)
@sorenpeterdarch.dk It doesn't work🤣 No other clients
Support this 😅
@sorenpeterdarch.dk It doesn't work🤣 No other clients
Support this 😅
@2024-10-09T08:11:00Z It an easy way of twt-adressing by using the timestamp instead of a nick, which is arbitrary anyhow. Just my suggestion for a new reply-model ;)
@2024-10-09T08:11:00Z It an easy way of twt-adressing by using the timestamp instead of a nick, which is arbitrary anyhow. Just my suggestion for a new reply-model ;)
@2024-10-09T08:11:00Z It an easy way of twt-adressing by using the timestamp instead of a nick, which is arbitrary anyhow. Just my suggestion for a new reply-model ;)
@2024-10-09T08:11:00Z It an easy way of twt-adressing by using the timestamp instead of a nick, which is arbitrary anyhow. Just my suggestion for a new reply-model ;)
¡El gato valenciano y orgulloso de serlo!
#catsoftwtxt
¡El gato valenciano y orgulloso de serlo!
#catsoftwtxt
@sorenpeter curious why you at mentioned a timestamp? 🤔
@sorenpeter curious why you at mentioned a timestamp? 🤔
@2024-10-08T19:36:38-07:00 Thanks for the followup. I agrees with most of it - especially:
> Please nobody suggest sticking the content type in more metadata. 🙄
Yes, URL can be considered ugly, but they work and are understandable by both humans and machines. And its trivial for any client to hide the URLs used as reference in replies/treading.
Webfinger can be an add-on to help lookup people, and it can be made independent of the nick by just serving the same json regardless of the nick as people do with static sites and a as I implemented it on darch.dk (wf endpoint). Try RANDOMSTRING@darch.dk on http://darch.dk/wf-lookup.php (wf lookup) or RANDOMSTRING@garrido.io on https://webfinger.net
@2024-10-08T19:36:38-07:00 Thanks for the followup. I agrees with most of it - especially:
> Please nobody suggest sticking the content type in more metadata. 🙄
Yes, URL can be considered ugly, but they work and are understandable by both humans and machines. And its trivial for any client to hide the URLs used as reference in replies/treading.
Webfinger can be an add-on to help lookup people, and it can be made independent of the nick by just serving the same json regardless of the nick as people do with static sites and a as I implemented it on darch.dk (wf endpoint). Try RANDOMSTRING@darch.dk on http://darch.dk/wf-lookup.php (wf lookup) or RANDOMSTRING@garrido.io on https://webfinger.net
/https://baldo.cat/media/photos/IMG_2310.jpeg) #catsoftwtxt
Bee hives in the evening shade
/https://baldo.cat/media/photos/IMG_2297.jpeg) #catsoftwtxt