ux2028 twice in my description. May lower it to once, but need some reference first. π
ux2028 twice in my description. May lower it to once, but need some reference first. π
metadata as described on the format documentation. That is, ux2028 is ignored when Yarn renders the description metadata.
metadata as described on the format documentation. That is, ux2028 is ignored when Yarn renders the description metadata.
description header. Or rather, how often it re-fetches it.
description header. Or rather, how often it re-fetches it.
Trying to fetch "#mowsvgq" from Yarn pod https://txt.sour.is ...
Trying to fetch "#mowsvgq" from Yarn pod https://twtxt.net ...
Twt could not be found
Yet, the twtxt is there: https://twtxt.net/twt/mowsvgq. Bug, or something else?
Trying to fetch "#mowsvgq" from Yarn pod https://txt.sour.is ...
Trying to fetch "#mowsvgq" from Yarn pod https://twtxt.net ...
Twt could not be found
Yet, the twtxt is there: https://twtxt.net/twt/mowsvgq. Bug, or something else?
42 75 69 6C 64 20 77 68 61 74 20 6D 61 6B 65 73 20 79 6F 75 20 68 61 70 70 79 2E 20 4C 65 74 20 6D 69 73 65 72 61 62 6C 65 20 70 65 6F 70 6C 65 20 62 75 69 6C 64 20 74 68 65 20 72 65 73 74 2E
42 75 69 6C 64 20 77 68 61 74 20 6D 61 6B 65 73 20 79 6F 75 20 68 61 70 70 79 2E 20 4C 65 74 20 6D 69 73 65 72 61 62 6C 65 20 70 65 6F 70 6C 65 20 62 75 69 6C 64 20 74 68 65 20 72 65 73 74 2E
"*If twtxt/Yarn was to grow bigger, then this would become a concern again. *But even Mastodon allows editing*, so how
+much of a problem can it really be? π
*"
"*If twtxt/Yarn was to grow bigger, then this would become a concern again. *But even Mastodon allows editing*, so how
+much of a problem can it really be? π
*"
I think keeping hashes is a must. If anything for that "feels good" feeling.*
I think keeping hashes is a must. If anything for that "feels good" feeling.*
jenny, a -v switch. That way when you twtxt "*Thatβs an older format that was used before jenny version v23.04*", I can go and run jenny -v, and "duh!" myself on the way to a git pull. :-D
jenny, a -v switch. That way when you twtxt "*Thatβs an older format that was used before jenny version v23.04*", I can go and run jenny -v, and "duh!" myself on the way to a git pull. :-D
commit 62a2b7735749f2ff3c9306dd984ad28f853595c5:> Crawl archived feeds in --fetch-context
Like, very much! :-)
commit 62a2b7735749f2ff3c9306dd984ad28f853595c5:> Crawl archived feeds in --fetch-context
Like, very much! :-)
zq4fgq.
zq4fgq.
jenny also does what I want, as of latest commit. Simply use jenny --debug-feed <feed url>, and it will do what I wanted too!
jenny also does what I want, as of latest commit. Simply use jenny --debug-feed <feed url>, and it will do what I wanted too!
* @prologic (and I assume any Yarn user)
2024-09-18T13:16:17Z* @lyse
2024-09-17T21:15:00+02:00* @aelaraji (and @movq, and me)
2024-09-18T05:43:13+00:00So, which is right, or best?*
* @prologic (and I assume any Yarn user)
2024-09-18T13:16:17Z* @lyse
2024-09-17T21:15:00+02:00* @aelaraji (and @movq, and me)
2024-09-18T05:43:13+00:00So, which is right, or best?*
debug command on my local yarnc. Are you talking about a potential future implementation here?
debug command on my local yarnc. Are you talking about a potential future implementation here?
yarnc, and it would work for a simple twtxt. Now, for a more convoluted one it truly becomes a nightmare using that tool for the job. I know there are talks about changing this hash, so this might be a moot point *right now*, but it would be nice to have a tool that:1. Would calculate the hash of a twtxt in a file.
2. Would calculate all hashes on a
twtxt.txt (local and remote).Again, something lovely to have after any looming changes occur.
yarnc, and it would work for a simple twtxt. Now, for a more convoluted one it truly becomes a nightmare using that tool for the job. I know there are talks about changing this hash, so this might be a moot point *right now*, but it would be nice to have a tool that:1. Would calculate the hash of a twtxt in a file.
2. Would calculate all hashes on a
twtxt.txt (local and remote).Again, something lovely to have after any looming changes occur.
Thank gods those posting their hideous squares have finally quieted down. LOL.
Thank gods those posting their hideous squares have finally quieted down. LOL.
jenny, nor yarnd supports it at all. This was treated as a thread because I picked one of @falsifian's twtxts (with the "old subject"), and replied to it (hence starting the thread).
jenny, nor yarnd supports it at all. This was treated as a thread because I picked one of @falsifian's twtxts (with the "old subject"), and replied to it (hence starting the thread).
publish_command:
#!/usr/bin/env bash
twtxt2html -t "Quark's twtxt feed" /var/www/sites/ferengi.one/twtxt.txt > /var/www/sites/ferengi.one/index.html
I named it
twtxtit. :-)
publish_command:
#!/usr/bin/env bash
twtxt2html -t "Quark's twtxt feed" /var/www/sites/ferengi.one/twtxt.txt > /var/www/sites/ferengi.one/index.html
I named it
twtxtit. :-)
> "yarnd
(_at least_) doesn't support creating such a custom TwtSubject, but it will reply and respect and thread one if one was constructed."
> "yarnd
(_at least_) doesn't support creating such a custom TwtSubject, but it will reply and respect and thread one if one was constructed."