FOLLOW: @xuu@txt.sour.is from @meff@yarn.meff.me using yarnd/0.7.2@a4ee171
FOLLOW: @xuu@txt.sour.is from @darch2@yarn.algorave.dk using yarnd/0.6.2@86938ca
@prologic@twtxt.net
Thank you, that’s the correct one.
Still I have this in my logs (first access of “eleven” by yarnd):
ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “GET /eleven.txt HTTP/2.0” 200 344 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”
ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “HEAD /avatar.png HTTP/2.0” 200 0 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”
And I guess without avatar.png sitting there I would have seen even more requests like /eleven.txt/avatar.png.
I’ve copied stackeffect.png to avatar.png to make yarnd happy when accessing stackeffect.txt.
So in this setup yarnd fetched eleven.txt along with avatar.png which belongs to another twtxt. This feels buggy.
FOLLOW: @xuu@txt.sour.is from @fastidious@arrakis.netbros.com using yarnd/0.1.0@b88b11b
@prologic@twtxt.net finally updated yarnd.. FORK!? Awesome!
FOLLOW: @xuu@txt.sour.is from @adi@f.adi.onl using yarnd/0.1.0@c6fd1c8
FOLLOW: @xuu@txt.sour.is from @laz@tt.vltra.plus using yarnd/master@1dcc5aed
FOLLOW: @xuu@txt.sour.is from @eldersnake@yarn.andrewjvpowell.com using yarnd/0.1.0@e335324
FOLLOW: @xuu@txt.sour.is from @lohn@tw.lohn.in using yarnd/0.0.0@HEAD