You can now do a “oneshot fetch” for a URL:
jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest
This fetches the entire feed, which might be too much. So there’s also this, which only fetches a single twt:
jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest --only-twt-hash r6rbinq
Let me know what you think. 🤔
You can now do a “oneshot fetch” for a URL:
jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest
This fetches the entire feed, which might be too much. So there’s also this, which only fetches a single twt:
jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest --only-twt-hash r6rbinq
Let me know what you think. 🤔
You can now do a “oneshot fetch” for a URL:
jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest
This fetches the entire feed, which might be too much. So there’s also this, which only fetches a single twt:
jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest --only-twt-hash r6rbinq
Let me know what you think. 🤔
You can now do a “oneshot fetch” for a URL:
jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest
This fetches the entire feed, which might be too much. So there’s also this, which only fetches a single twt:
jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest --only-twt-hash r6rbinq
Let me know what you think. 🤔
GET /twt/<HASH> with Accept: application/json:
$ curl -sH 'Accept: application/json' https://twtxt.net/twt/fgthxaq | jq
{
"twter": {
"nick": "prologic",
"uri": "https://twtxt.net/user/prologic/twtxt.txt",
"avatar": "https://twtxt.net/user/prologic/avatar#gdoicerjkh3nynyxnxawwwkearr4qllkoevtwb3req4hojx5z43q"
},
"text": "(#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt> @<movq https://www.uninformativ.de/twtxt.txt> You actually only really want the missing root Twt. You could just fetch this from any Yarn pod. There are scripts I built way back when yo do this 😅",
"created": "2024-08-23T00:54:04Z",
"markdownText": "(#tkjafka) [@falsifian](https://www.falsifian.org/twtxt.txt#falsifian) [@movq](https://www.uninformativ.de/twtxt.txt#movq) You actually only really want the missing root Twt. You could just fetch this from any Yarn pod. There are scripts I built way back when yo do this 😅",
"hash": "fgthxaq",
"tags": [
"tkjafka"
],
"subject": "(#tkjafka)",
"mentions": [
"@<falsifian https://www.falsifian.org/twtxt.txt>",
"@<movq https://www.uninformativ.de/twtxt.txt>"
],
"links": []
}
@<quark …) should still be visible in full?
@<quark …) should still be visible in full?
@<quark …) should still be visible in full?
@<quark …) should still be visible in full?
> […] Putting mentions before the hash is still supported but discouraged. […]
> \n Putting mentions before the hash is still supported but discouraged. \n
It can be
(#hash) @
or
@
The latter is from an earlier convention/spec. How about deprecating or even removing this?
https://dev.twtxt.net/doc/twtsubjectextension.html
It can be
(#hash) @
or
@
The latter is from an earlier convention/spec. How about deprecating or even removing this?
https://dev.twtxt.net/doc/twtsubjectextension.html
It can be
(#hash) @
or
@
The latter is from an earlier convention/spec. How about deprecating or even removing this?
https://dev.twtxt.net/doc/twtsubjectextension.html
It can be
(#hash) @
or
@
The latter is from an earlier convention/spec. How about deprecating or even removing this?
https://dev.twtxt.net/doc/twtsubjectextension.html
(#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔It won’t always work. There’s no guarantee that
tkjafka will be present in the given URL.Hmm. 🤔
(#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔It won’t always work. There’s no guarantee that
tkjafka will be present in the given URL.Hmm. 🤔
(#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔It won’t always work. There’s no guarantee that
tkjafka will be present in the given URL.Hmm. 🤔
(#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔It won’t always work. There’s no guarantee that
tkjafka will be present in the given URL.Hmm. 🤔