yarnd peers with each pod in its own network to do exactly that. Maybe we could open up the protocol and you could potentially pee with other pods?
yarnd peers with each pod in its own network to do exactly that. Maybe we could open up the protocol and you could potentially pee with other pods?
yarnd has for "peering" between pods for this reason. It's quite simple really and its _actually_ open publicly, so you can just use the scripts I wrote.One thing to bare in mind is that Twtxt (_the original spec_) is largely dead, this included the registry. The registry in practise was never really widely used, and suffers from "centralization" -- Which registry do you use? Its for this reason we built a search engine/crawler to help with searching and discovery. Anyway I digress... LMK if you want to go down this path, happy to document it beyond the scripts I wrote.
yarnd has for "peering" between pods for this reason. It's quite simple really and its _actually_ open publicly, so you can just use the scripts I wrote.One thing to bare in mind is that Twtxt (_the original spec_) is largely dead, this included the registry. The registry in practise was never really widely used, and suffers from "centralization" -- Which registry do you use? Its for this reason we built a search engine/crawler to help with searching and discovery. Anyway I digress... LMK if you want to go down this path, happy to document it beyond the scripts I wrote.
(#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. š¤
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. š¤
fetch-context branch. This integrates the whole thing into mutt/jenny.You will want to configure a new mutt hotkey, similar to the āreplyā hotkey:
macro index,pager
"Try to fetch context of current twt, like a missing root twt"
This pipes the mail to
jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If thereās no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)The whole thing looks like this:
https://movq.de/v/0d0e76a180/jenny.mp4
In other words, when thereās a missing root twt, you press a hotkey to fetch it, done.
I think I like this version better. š¤
(This needs a lot of testing. š)
fetch-context branch. This integrates the whole thing into mutt/jenny.You will want to configure a new mutt hotkey, similar to the āreplyā hotkey:
macro index,pager
"Try to fetch context of current twt, like a missing root twt"
This pipes the mail to
jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If thereās no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)The whole thing looks like this:
https://movq.de/v/0d0e76a180/jenny.mp4
In other words, when thereās a missing root twt, you press a hotkey to fetch it, done.
I think I like this version better. š¤
(This needs a lot of testing. š)
fetch-context branch. This integrates the whole thing into mutt/jenny.You will want to configure a new mutt hotkey, similar to the āreplyā hotkey:
macro index,pager
"Try to fetch context of current twt, like a missing root twt"
This pipes the mail to
jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If thereās no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)The whole thing looks like this:
https://movq.de/v/0d0e76a180/jenny.mp4
In other words, when thereās a missing root twt, you press a hotkey to fetch it, done.
I think I like this version better. š¤
(This needs a lot of testing. š)
fetch-context branch. This integrates the whole thing into mutt/jenny.You will want to configure a new mutt hotkey, similar to the āreplyā hotkey:
macro index,pager
"Try to fetch context of current twt, like a missing root twt"
This pipes the mail to
jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If thereās no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)The whole thing looks like this:
https://movq.de/v/0d0e76a180/jenny.mp4
In other words, when thereās a missing root twt, you press a hotkey to fetch it, done.
I think I like this version better. š¤
(This needs a lot of testing. š)
Say I see a twt beginning (#hash) and I want to look up the start of the thread. Is the idea that if that twt is hosted by a a yarn.social pod, it is likely to know the thread start, so I should query that particular pod for the hash? But what if no yarn.social pods are involved?
The community seems small enough that a registry server should be able to keep up, and I can have a couple of others as backups. Or I could crawl the list of feeds followed by whoever emitted the twt that prompted my query.
I have successfully used registry servers a little bit, e.g. to find a feed that mentioned a tag I was interested in. Was even thinking of making my own, if I get bored of my too many other projects :-)
On registries however, I think a registry is the wrong approach. I see far greater value in feed crawlers and search engines like the (_half baked one_) I built over at https://search.twtxt.net/
On registries however, I think a registry is the wrong approach. I see far greater value in feed crawlers and search engines like the (_half baked one_) I built over at https://search.twtxt.net/
(I also noticed that https://twtxt.readthedocs.io/en/latest/user/registry.html recommends "The registries should sync each others user list by using the users endpoint". If I understood that right, registering with one should be enough to appear on others, even if they don't crawl.)
Does yarnd provide an API for finding twts? Is it similar?
> Does yarnd provide an API for finding twts? Is it similar?
No, it doesn't. But
yarns (_the search engine/crawler wrote_) seems more fitting here. It's been discussed before, the possibility of building a "Twtxt Register v1" compatible API for yarns. I _think_ a search engine + crawler + registry (_especially ones that can form a bit of a "distributed network_) are far more useful I _think_ in order to support the _actual_ decentralised Twtxt / Yarn ecosystem (_which is how I prefer to describe it_).
> Does yarnd provide an API for finding twts? Is it similar?
No, it doesn't. But
yarns (_the search engine/crawler wrote_) seems more fitting here. It's been discussed before, the possibility of building a "Twtxt Register v1" compatible API for yarns. I _think_ a search engine + crawler + registry (_especially ones that can form a bit of a "distributed network_) are far more useful I _think_ in order to support the _actual_ decentralised Twtxt / Yarn ecosystem (_which is how I prefer to describe it_).