# 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 20
# self = https://watcher.sour.is/conv/zaqyjia
prologic
twtxt.net
View Thread
So I discovered (get it? 🤣) that there is a Twtxt feed out there that is otherwise identical but are served as two different feeds with a different # url = field for some strange reason, even though the content is literally identical 😅

You can see what I mean by poking around these two twts: #jbsw56q and #bekvqja

Basically if you're going to serve your feed over different protocols or a different URL on the same protocol/scheme, you _really_ should use the same # url = (Hashing URI as per the spec) 🤗
prologic
twtxt.net
View Thread
So I discovered (get it? 🤣) that there is a Twtxt feed out there that is otherwise identical but are served as two different feeds with a different # url = field for some strange reason, even though the content is literally identical 😅

You can see what I mean by poking around these two twts: #jbsw56q and #bekvqja

Basically if you're going to serve your feed over different protocols or a different URL on the same protocol/scheme, you _really_ should use the same # url = (Hashing URI as per the spec) 🤗
prologic
twtxt.net
View Thread
So I discovered (get it? 🤣) that there is a Twtxt feed out there that is otherwise identical but are served as two different feeds with a different # url = field for some strange reason, even though the content is literally identical 😅

You can see what I mean by poking around these two twts: #jbsw56q and #bekvqja

Basically if you're going to serve your feed over different protocols or a different URL on the same protocol/scheme, you _really_ should use the same # url = (Hashing URI as per the spec) 🤗
prologic
twtxt.net
View Thread
So I discovered (get it? 🤣) that there is a Twtxt feed out there that is otherwise identical but are served as two different feeds with a different # url = field for some strange reason, even though the content is literally identical 😅

You can see what I mean by poking around these two twts: #jbsw56q and #bekvqja

Basically if you're going to serve your feed over different protocols or a different URL on the same protocol/scheme, you _really_ should use the same # url = (Hashing URI as per the spec) 🤗
eaplmx
twtxt.net
View Thread
@prologic hmm... For instance, I have the same file served on

https://eapl.mx/twtxt.txt

and

gemini://eapl.mx/twtxt.txt


And it's the same with my blog https://text.eapl.mx and gemini://text.eapl.mx

So the _trick_ I've used is linking to //text.eapl.mx

Do you think this would work?
# url = //eapl.mx/twtxt.txt
eaplmx
twtxt.net
View Thread
@prologic hmm... For instance, I have the same file served on

https://eapl.mx/twtxt.txt

and

gemini://eapl.mx/twtxt.txt


And it's the same with my blog https://text.eapl.mx and gemini://text.eapl.mx

So the trick I've used this _trick_ is linking to //text.eapl.mx

Do you think this would work?
# url = //eapl.mx/twtxt.txt
prologic
twtxt.net
View Thread
@eaplmx I'm _actually_ not sure if that'll work. Can you test it and let us know, then submit a PR to amend the spec if it does? 😅 It just affects the Twt Hash(es), and we take the first one as the "Hashing URI".
prologic
twtxt.net
View Thread
@eaplmx I'm _actually_ not sure if that'll work. Can you test it and let us know, then submit a PR to amend the spec if it does? 😅 It just affects the Twt Hash(es), and we take the first one as the "Hashing URI".
prologic
twtxt.net
View Thread
@eaplmx I'm _actually_ not sure if that'll work. Can you test it and let us know, then submit a PR to amend the spec if it does? 😅 It just affects the Twt Hash(es), and we take the first one as the "Hashing URI".
prologic
twtxt.net
View Thread
@eaplmx I'm _actually_ not sure if that'll work. Can you test it and let us know, then submit a PR to amend the spec if it does? 😅 It just affects the Twt Hash(es), and we take the first one as the "Hashing URI".
eaplmx
twtxt.net
View Thread
@prologic I've changed it from # url = https://eapl.mx/twtxt.txt to # url = //eapl.mx/twtxt.txt... Let's see what happens
prologic
twtxt.net
View Thread
@eaplmx What will happen now _I think_ is all your Twts will change their Hashes maybe 😅 Changing your feed's "Hashing URL" is not something you _really_ want to do too often I think 🤣 But let's see...
prologic
twtxt.net
View Thread
@eaplmx What will happen now _I think_ is all your Twts will change their Hashes maybe 😅 Changing your feed's "Hashing URL" is not something you _really_ want to do too often I think 🤣 But let's see...
prologic
twtxt.net
View Thread
@eaplmx What will happen now _I think_ is all your Twts will change their Hashes maybe 😅 Changing your feed's "Hashing URL" is not something you _really_ want to do too often I think 🤣 But let's see...
prologic
twtxt.net
View Thread
@eaplmx What will happen now _I think_ is all your Twts will change their Hashes maybe 😅 Changing your feed's "Hashing URL" is not something you _really_ want to do too often I think 🤣 But let's see...
eaplmx
twtxt.net
View Thread
@prologic I agree... It has little activity, but I'll do it for science!
prologic
twtxt.net
View Thread
@eaplmx 👌
prologic
twtxt.net
View Thread
@eaplmx 👌
prologic
twtxt.net
View Thread
@eaplmx 👌
prologic
twtxt.net
View Thread
@eaplmx 👌