# 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 196266
# self = https://watcher.sour.is?offset=178540
# next = https://watcher.sour.is?offset=178640
# prev = https://watcher.sour.is?offset=178440
[47°09′22″S, 126°43′57″W] Transfer completed
Anyone using microMDM to enroll their family's iOS and macOS devices to help centrally manage them? 🤔 #Apple #MDM
Anyone using microMDM to enroll their family's iOS and macOS devices to help centrally manage them? 🤔 #Apple #MDM
[47°09′55″S, 126°43′33″W] Transfer 75% complete...
I thought you were talking about a TV series 🤣
I thought you were talking about a TV series 🤣
An entire year waiting for this season, yet, it comes and goes so soon. I am going to squeeze the most of what’s left until it’s over.
🧮 USERS:1 FEEDS:2 TWTS:1196 ARCHIVED:82957 CACHE:2587 FOLLOWERS:17 FOLLOWING:14
I finally watched "C++17: I See a Monad in Your Future" and it was rather nice (at least in 1.8 times speed): https://www.youtube.com/watch?v=BFnhhPehpKw I finally also learned why the auto syntax exists (to allow specifying a return type that depends on the argument).
I loved to watch the “Curiosity Show” when I was a kid (the German version, of course – to this day, nothing in German television is in English, it’s *all* dubbed horribly). And it’s on YouTube now! 🥳 https://www.youtube.com/@CuriosityShow/videos
I loved to watch the “Curiosity Show” when I was a kid (the German version, of course – to this day, nothing in German television is in English, it’s *all* dubbed horribly). And it’s on YouTube now! 🥳 https://www.youtube.com/@CuriosityShow/videos
I loved to watch the “Curiosity Show” when I was a kid (the German version, of course – to this day, nothing in German television is in English, it’s *all* dubbed horribly). And it’s on YouTube now! 🥳 https://www.youtube.com/@CuriosityShow/videos
I loved to watch the “Curiosity Show” when I was a kid (the German version, of course – to this day, nothing in German television is in English, it’s *all* dubbed horribly). And it’s on YouTube now! 🥳 https://www.youtube.com/@CuriosityShow/videos
[47°09′42″S, 126°43′44″W] Transfer 50% complete...
@prologic No I'm not trying to standardize the domains themselves xD I was just hinting at filtering cases where nick is identical to a level of a domain; in order to show shorter format nicks within clients, i.e: @nick.domain.ltd or @nick.ltd instead of a @nick@nick.domain.ltd or @nick@nick.ltd. Just like what @sorenpeter already did with the nick = domain case. _(unless I'm missing the point)_
@prologic No I'm not trying to standardize the domains themselves xD I was just hinting at filtering cases where nick is identical to a level of a domain; in order to show shorter format nicks within clients, i.e: @nick.domain.ltd or @nick.ltd instead of a @nick@nick.domain.ltd or @nick@nick.ltd. Just like what @sorenpeter already did with the nick = domain case. _(unless I'm missing the point)_
@prologic No I'm not trying to standardize the domains themselves xD I was just hinting at filtering cases where nick is identical to a level of a domain; in order to show shorter format nicks within clients, i.e: @nick.domain.ltd or @nick.ltd instead of a @nick@nick.domain.ltd or @nick@nick.ltd. Just like what @sorenpeter already did with the nick = domain case. _(unless I'm missing the point)_
[47°09′56″S, 126°43′02″W] Sample analyzing complete -- starting transfer
[47°09′22″S, 126°43′48″W] Re-taking samples
Your nick is normal. After i delete gh account with nick doesnm i can't reuse them. And my next nick is... doesnmisclown xD (without a)
we talk about programming like it is about writing code, but the code ends up being less important than the architecture, and the architecture ends up being less important than social issues. The success and failure of Ninja (2020) | Hacker News
[47°09′37″S, 126°43′13″W] Taking samples
[47°09′43″S, 126°43′30″W] --bad checksum--
@bender Bahahaha in hindsight I got rid of that 🤣 Just silly nonsense, just one of those things when you create an account on yet-another silly centralized platform(s) and go "fuck" someone's already taken the username I want 😅
@bender Bahahaha in hindsight I got rid of that 🤣 Just silly nonsense, just one of those things when you create an account on yet-another silly centralized platform(s) and go "fuck" someone's already taken the username I want 😅
@aelaraji domains/subdomains I _think_ are much harder to "standardize" hmmm 🤔
@aelaraji domains/subdomains I _think_ are much harder to "standardize" hmmm 🤔
🧮 USERS:1 FEEDS:2 TWTS:1195 ARCHIVED:82947 CACHE:2593 FOLLOWERS:17 FOLLOWING:14
@prologic we have been all guilty, at some point or another, of spending too much money on domains we don’t need. Pax vobiscum! 😂😂😂
@sorenpeter @bender @prologic Right. Also, generally speaking, if you come across a new feed URL, it's probably either via some mention in another feed or the User-Agent in your access log. Both cases typically advertise also a display name. So, you just reuse whatever you've seen there.
@sorenpeter I think the use of ~ is so commonly used as a <username> that we should just suppose that out of the box by all clients for display purposes.
@sorenpeter I think the use of ~ is so commonly used as a <username> that we should just suppose that out of the box by all clients for display purposes.
@soren you reach out and tell them to set a nick? Or parse the URL, and use the word right after the tilde as the nick?
[47°09′48″S, 126°43′58″W] Storm recedes -- back to normal work
@doesnm How did you post from IndiePass? Did you add support for twtxt or use some kind of bridge?
@doesnm How did you post from IndiePass? Did you add support for twtxt or use some kind of bridge?
@doesnm How did you post from IndiePass? Did you add support for twtxt or use some kind of bridge?
@doesnm How did you post from IndiePass? Did you add support for twtxt or use some kind of bridge?
I saw a paraglider after sunset. Must have been super cold up there in the sky, we just had 1-2°C on the ground. And I passed a heron at just 5-6 meters distance. I think that's a new record low. The sunset itself wasn't all that shabby either. Hence, a very good stroll.
[47°09′34″S, 126°43′42″W] Weather forecast alert -- storm from S
You are right: no advantage. Also your method can make backward compatible to feeds which doesn't implement metadata extension
@sorenpeter No I agree. I think if the feed doesn't hint at a nick, just default to displaying the bare domain. These sorts of things btw need to go into a Client recommendations / guidelines. If someone wants to start drafting up such I doc I will fully support this and help shape it 👌
@sorenpeter No I agree. I think if the feed doesn't hint at a nick, just default to displaying the bare domain. These sorts of things btw need to go into a Client recommendations / guidelines. If someone wants to start drafting up such I doc I will fully support this and help shape it 👌
What should the advantage be to nick = _compared to just not defining a nick and let the client use the domain as the handle?
What is not intuitive is that you put something in the nick field that is not to be taken literary. The special meaning of _ is only clean if you read the documentation, compared to having something in nick that makes sense in the current context of the twtxt.txt.
What should the advantage be to nick = _compared to just not defining a nick and let the client use the domain as the handle?
What is not intuitive is that you put something in the nick field that is not to be taken literary. The special meaning of _ is only clean if you read the documentation, compared to having something in nick that makes sense in the current context of the twtxt.txt.
What should the advantage be to nick = _compared to just not defining a nick and let the client use the domain as the handle?
What is not intuitive is that you put something in the nick field that is not to be taken literary. The special meaning of _ is only clean if you read the documentation, compared to having something in nick that makes sense in the current context of the twtxt.txt.
What should the advantage be to nick = _compared to just not defining a nick and let the client use the domain as the handle?
What is not intuitive is that you put something in the nick field that is not to be taken literary. The special meaning of _ is only clean if you read the documentation, compared to having something in nick that makes sense in the current context of the twtxt.txt.
[47°09′50″S, 126°43′39″W] Transfer aborted
@doesnm That can be done fairly easily I think/
@doesnm That can be done fairly easily I think/
No te quito el ojo
#catsoftwtxt
/https://baldo.cat/media/photos/IMG_3128.jpeg) #catsoftwtxt