curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq
This gets you a twt which, when hashed again *now* using all the information from that API reply, does not yield the hash
mowsvgq but bjs6aua.But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s
mowsvgq.So I would expect Yarn to *either* know about
mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) *or* about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅I don’t see how the second
# url = metadata field is relevant here. 🤔
curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq
This gets you a twt which, when hashed again *now* using all the information from that API reply, does not yield the hash
mowsvgq but bjs6aua.But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s
mowsvgq.So I would expect Yarn to *either* know about
mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) *or* about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅I don’t see how the second
# url = metadata field is relevant here. 🤔
curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq
This gets you a twt which, when hashed again *now* using all the information from that API reply, does not yield the hash
mowsvgq but bjs6aua.But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s
mowsvgq.So I would expect Yarn to *either* know about
mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) *or* about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅I don’t see how the second
# url = metadata field is relevant here. 🤔
curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq
This gets you a twt which, when hashed again *now* using all the information from that API reply, does not yield the hash
mowsvgq but bjs6aua.But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s
mowsvgq.So I would expect Yarn to *either* know about
mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) *or* about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅I don’t see how the second
# url = metadata field is relevant here. 🤔
uri field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅
uri field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅
uri field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅
uri field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅
Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash
bjs6aua instead of mowsvgq. That’s not the correct hash, so jenny says the twt could not be found.Inspecting the feed using
jenny -D … yields the correct hash. When looking at the raw feed, we can see:
# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025
So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.
Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash
bjs6aua instead of mowsvgq. That’s not the correct hash, so jenny says the twt could not be found.Inspecting the feed using
jenny -D … yields the correct hash. When looking at the raw feed, we can see:
# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025
So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.
Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash
bjs6aua instead of mowsvgq. That’s not the correct hash, so jenny says the twt could not be found.Inspecting the feed using
jenny -D … yields the correct hash. When looking at the raw feed, we can see:
# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025
So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.
Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash
bjs6aua instead of mowsvgq. That’s not the correct hash, so jenny says the twt could not be found.Inspecting the feed using
jenny -D … yields the correct hash. When looking at the raw feed, we can see:
# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025
So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.
avatar field has a #20240102 at the end: To trick yarnd into reloading it.
avatar field has a #20240102 at the end: To trick yarnd into reloading it.
avatar field has a #20240102 at the end: To trick yarnd into reloading it.
avatar field has a #20240102 at the end: To trick yarnd into reloading it.
https://www.youtube.com/watch?v=PeuH0YmWkI4
💛
https://www.youtube.com/watch?v=PeuH0YmWkI4
💛
https://www.youtube.com/watch?v=PeuH0YmWkI4
💛
https://www.youtube.com/watch?v=PeuH0YmWkI4
💛
https://rachelbythebay.com/w/2018/03/15/core/
It’s just that this also happens locally nowadays and, thus, much easier and more often (I bet few people run programs via NFS these days). 🫤
Not a fan of this. (Time will tell if I have the energy to discuss this on the Linux kernel mailing list.)
https://rachelbythebay.com/w/2018/03/15/core/
It’s just that this also happens locally nowadays and, thus, much easier and more often (I bet few people run programs via NFS these days). 🫤
Not a fan of this. (Time will tell if I have the energy to discuss this on the Linux kernel mailing list.)
https://rachelbythebay.com/w/2018/03/15/core/
It’s just that this also happens locally nowadays and, thus, much easier and more often (I bet few people run programs via NFS these days). 🫤
Not a fan of this. (Time will tell if I have the energy to discuss this on the Linux kernel mailing list.)
https://rachelbythebay.com/w/2018/03/15/core/
It’s just that this also happens locally nowadays and, thus, much easier and more often (I bet few people run programs via NFS these days). 🫤
Not a fan of this. (Time will tell if I have the energy to discuss this on the Linux kernel mailing list.)