# 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 238061
# self = https://watcher.sour.is?offset=226736
# next = https://watcher.sour.is?offset=226836
# prev = https://watcher.sour.is?offset=226636
#musiquinta de #FimDoMundo para a última quinta do ano:

https://youtu.be/FhMOAydy7EY

(Sim, mais Marilyn Manson: The Last Day On Earth)
#musiquinta de #FimDoMundo para a última quinta do ano:

https://youtu.be/FhMOAydy7EY

(Sim, mais Marilyn Manson: The Last Day On Earth)
[47°09′22″S, 126°43′48″W] Re-taking samples
Recientemente me topé con el contenido de https://text.eapl.mx/, compartió un buen libro que también les comparto aquí https://t.ly/OfQZ3
@lyse Haha 🤣
@lyse Haha 🤣
@doesnm Haha 🤣
@doesnm Haha 🤣
ROFL
@bender @prologic Reminds me of: https://img.ifunny.co/images/d07b9a2014e3b3901abe5f4ab22cc2b89a0308de8a21d868d2022dac7bb0280d_1.jpg :-D
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
python cgi script which handles micropub and writes content to twtxt file. I was want micropub+microsub for twtverse but seems i burned (due choice wrong stack?): https://privatebin.net/?0b598b91ac186855#BfRKjLUQz5KUFJNekJBb5V2qvtEe8xQN8nenYbkez2XR
[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 😅
@prologic “therealprologic”? Really? 🤦‍♂️😅
i always thought that i needed geodns to make a multi-region setup work at all, but it turns out all we really need is one rfc https://datatracker.ietf.org/doc/html/rfc8305 and its not even rare to see implemented on clients
@aelaraji domains/subdomains I _think_ are much harder to "standardize" hmmm 🤔
@aelaraji domains/subdomains I _think_ are much harder to "standardize" hmmm 🤔
@sorenpeter Here are two more cases:
- nick = subdomain: https://aelaraji.com/timeline/profile?url=https://lyse.isobeef.org/twtxt.txt -> lyse.isobeef.org
- nick = second level domain: https://aelaraji.com/timeline/profile?url=https://aelaraji.com/twtxt.txt -> aelaraji.com
@sorenpeter Here are two more cases:
- nick = subdomain: https://aelaraji.com/timeline/profile?url=https://lyse.isobeef.org/twtxt.txt -> lyse.isobeef.org
- nick = second level domain: https://aelaraji.com/timeline/profile?url=https://aelaraji.com/twtxt.txt -> aelaraji.com
@sorenpeter Here are two more cases:
- nick = subdomain: https://aelaraji.com/timeline/profile?url=https://lyse.isobeef.org/twtxt.txt -> lyse.isobeef.org
- nick = second level domain: https://aelaraji.com/timeline/profile?url=https://aelaraji.com/twtxt.txt -> aelaraji.com
🧮 USERS:1 FEEDS:2 TWTS:1195 ARCHIVED:82947 CACHE:2593 FOLLOWERS:17 FOLLOWING:14
@bender Hahaha Hahaha 🤣 I've had this one for a while actually as well as https://prologic.blob (_which I'm thinking of taking back from micro.blog and just using my own tools, namely zs_) 😅
@bender Hahaha Hahaha 🤣 I've had this one for a while actually as well as https://prologic.blob (_which I'm thinking of taking back from micro.blog and just using my own tools, namely zs_) 😅
@prologic we have been all guilty, at some point or another, of spending too much money on domains we don’t need. Pax vobiscum! 😂😂😂
What do we think? > https://prologic.dev/
What do we think? > https://prologic.dev/
@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.
Unmasking the hidden gems of Void Linux https://animeshz.github.io/site/blogs/void-linux.html
Unmasking the hidden gems of Void Linux https://animeshz.github.io/site/blogs/void-linux.html
@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?
hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt
hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt
hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt
hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt
[47°09′48″S, 126°43′58″W] Storm recedes -- back to normal work
Happy Christmas!
Happy Christmas!
@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
Merry Christmas ! 🎅🎄
I've implemented Use only nick as handle if nick and domain is the same · sorenpeter/timeline@8c12444

See it live at:
- nick = domain: https://darch.dk/timeline/profile?url=https://eapl.me/tw.txt
- nick ≠ domain: https://darch.dk/timeline/profile?url=https://twtxt.net/user/prologic/twtxt.txt
- no nick, use domain: https://darch.dk/timeline/profile?url=https://akkartik.name/twtxt.txt

I'm not sure I like the leading @ thou...=
I've implemented Use only nick as handle if nick and domain is the same · sorenpeter/timeline@8c12444

See it live at:
- nick = domain: https://darch.dk/timeline/profile?url=https://eapl.me/tw.txt
- nick ≠ domain: https://darch.dk/timeline/profile?url=https://twtxt.net/user/prologic/twtxt.txt
- no nick, use domain: https://darch.dk/timeline/profile?url=https://akkartik.name/twtxt.txt

I'm not sure I like the leading @ thou...=
I've implemented Use only nick as handle if nick and domain is the same · sorenpeter/timeline@8c12444

See it live at:
- nick = domain: https://darch.dk/timeline/profile?url=https://eapl.me/tw.txt
- nick ≠ domain: https://darch.dk/timeline/profile?url=https://twtxt.net/user/prologic/twtxt.txt
- no nick, use domain: https://darch.dk/timeline/profile?url=https://akkartik.name/twtxt.txt

I'm not sure I like the leading @ thou...=
I've implemented Use only nick as handle if nick and domain is the same · sorenpeter/timeline@8c12444

See it live at:
- nick = domain: https://darch.dk/timeline/profile?url=https://eapl.me/tw.txt
- nick ≠ domain: https://darch.dk/timeline/profile?url=https://twtxt.net/user/prologic/twtxt.txt
- no nick, use domain: https://darch.dk/timeline/profile?url=https://akkartik.name/twtxt.txt

I'm not sure I like the leading @ thou...=
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
No te quito el ojo
/https://baldo.cat/media/photos/IMG_3128.jpeg) #catsoftwtxt
No te quito el ojo
#catsoftwtxt
No, i mean just _. If my nick = _ and my twtxt is located at https://doesnm.cc/twtxt.txt then just display me as doesnm.cc. Why it's not intuitive?=
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as @domain.tld instead of @domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as @domain.tld
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as domain.tld instead of domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as domain.tld
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as @domain.tld instead of @domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as @domain.tld
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as @domain.tld instead of @domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as @domain.tld
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as domain.tld instead of domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as domain.tld
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as @domain.tld instead of @domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as @domain.tld
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as domain.tld instead of domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as domain.tld
@doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as domain.tld instead of domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as domain.tld
Why not nostr way? https://github.com/nostr-protocol/nips/blob/master/05.md#showing-just-the-domain-as-an-identifier
[47°09′57″S, 126°43′39″W] Bad satellite signal -- switching to analog communication
Merry Christmas!
[47°09′29″S, 126°43′56″W] Saalmi, retransmit, please
Se acerca la medianoche, vamos a ver que nos trae el niño dios jaja
@aelaraji I am sure it will run fine. I mean, mine is on a VPS, with 1GB RAM, 1vCPU, and shares it with Conduwit (Matrix), a few websites, Headscale, etc. 😂
🦌🦌🦌🛷🎅 <(Ho-Ho-Hooo!)✨
@bender Le Me is _very_ tempted to spin up my own but not sure my pet computer(/server wannabe) and stone age bandwidth can withstand the Fedi-load 😅
@bender Le Me is _very_ tempted to spin up my own but not sure my pet computer(/server wannabe) and stone age bandwidth can withstand the Fedi-load 😅
@bender Le Me is _very_ tempted to spin up my own but not sure my pet computer(/server wannabe) and stone age bandwidth can withstand the Fedi-load 😅
Merry Xmas everyone! have a blessed and happy day! 🎉
Merry Xmas everyone! have a blessed and happy day! 🎉
Merry Xmas everyone! have a blessed and happy day! 🎉
Que divertido es esto, nunca usé twitter, y ahora uso twtxt \o/
🧮 USERS:1 FEEDS:2 TWTS:1194 ARCHIVED:82940 CACHE:2600 FOLLOWERS:17 FOLLOWING:14
Hola mundo!
zenblade no.9 | https://nilfm.cc/rollerblading.html
Merry Christmas! Cute canine, as always! 🥰
Merry blessed Christmas to all gopherites.
Merry Christmas, everyone!
Merry Christmas 🥳
Merry Christmas 🥳
Merry Christmas 🥳
Merry Christmas 🥳