OK folks, rebuilding/restarting yarnd hang in there.
Upgrading yarnd to latest and rebooting the virtual machine running it. See you on the other side.
And we’re back, now on yarnd 0.15.1.
We are now running yarnd 0.15.0! 🎉
OK, we are attempting an upgrade from yarnd 0.14.0 to yarnd 0.15.0. See you on the other side. 🤞
**
FOLLOW: @venjiang from @watcher@txt.sour.is using yarnd/0.13.0@0ada09a
**
FOLLOW: @venjiang from @watcher @txt.sour.is using yarnd/0.13.0@0ada09a ⌘ Read more
**
FOLLOW: @venjiang from @ullarah@txt.quisquiliae.com using yarnd/edge@4e6a3819
**
FOLLOW: @venjiang from @ullarah @txt.quisquiliae.com using yarnd/edge@4e6a3819 ⌘ Read more
**
FOLLOW: @venjiang from @watcher@txt.sour.is using yarnd/0.13.0@0db6025fae34e328119d2f031ec8384ee47f3d1f
**
FOLLOW: @venjiang from @watcher @txt.sour.is using yarnd/0.13.0@0db6025fae34e32 … ⌘ Read more
**
FOLLOW: @venjiang from @ullarah@txt.quisquiliae.com using yarnd/0.13.0@72b3ed56
**
FOLLOW: @venjiang from @ullarah @txt.quisquiliae.com using yarnd/0.13.0@72b3ed56 ⌘ Read more
yarnd v0.13 - Aluminium Amarok
Today we announced release v0.13.0 of the Yarn.social backend yarnd that now powers a network of 15 pods around the globe.
You can find the release here:
Yarn/Twtxt (Yarn.social is based on Twtxt) continues to grow steadily every day, and every month or so we see a new independent Pod (what we call in … ⌘ Read more
**
FOLLOW: @venjiang from @ullarah@txt.quisquiliae.com using yarnd/0.11.0@5319fbb
**
FOLLOW: @venjiang from @ullarah @txt.quisquiliae.com using yarnd/0.11.0@5319fbb ⌘ Read more
**
FOLLOW: @venjiang from @watcher@txt.sour.is using yarnd/0.8.0@b2ce19a
**
FOLLOW: @venjiang from @watcher @txt.sour.is using yarnd/0.8.0@b2ce19a ⌘ Read more
@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.
@prologic@twtxt.net finally updated yarnd.. FORK!? Awesome!