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 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 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 I’ve changed it from # url = https://eapl.mx/twtxt.txt to # url = //eapl.mx/twtxt.txt… Let’s see what happens

@eaplmx@twtxt.net 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 I agree… It has little activity, but I’ll do it for science!

@eaplmx@twtxt.net 👌