This works for any Yarn.social pod as well as the feeds.twtxt.net service. It can also work for any other Twtxt user as well by just simply adding the following to the root/index page of your domain:

<meta name="yarn-uri" context="/path/to/your/twtxt.txt" />

@~duriny@envs.net In the case of multi-user community-based hosting services such as envs.net and tilda.chat and others… Why can’t I work with the operators of those services to add support for this? 🤔 Seems like a “people” problem rather than a “technical” one…

In your specific case (_assuming we went with the <meta ...> approach would look something like:

<meta name="twtxt" content="/~:nick/twtxt.txt" />

In fact envs.sh already has a lookup service we can actually use here. We just need to know about it “somehow” – But honestly if they’re already providing this kind of JSON endpoint, I don’t see why they couldn’t also provide something more generalised and specific to Twtxt/Yarn in addition.

I wouldn’t be surprised to learn that other such similar community-based hosting services offer similar “directories”and “lookup” mechanisms. I would if I offered such a service (oh wait 🤦‍♂️)

@lyse@lyse.isobeef.org I don’t really like the approach approach you describe because the only reason that works at all is because my pod happens to have 1,090 feeds cached on it at any given point. 😳 – I’d like for us to come to a consensus (if we can) if we can about how we describe the location of feeds without either a) typing >50 characters or b) having to explain to someone something they have no clue about.

I believe this can be done. Think of it this way, @xuu@txt.sour.is mentions the use of DNS – Well DNS is what make the “Web” work really…

Without DNS you’d have to remember IPv4 addresses (or wose IPv6 address) and it would be rather tedious rather quickly. Why can’t we come up with something convenient and similar? 🤔 If Twtxt/Yarn is to continue to grow, I don’t see how we do that with exceedingly long and hard to get-rid/remember URIs.

And frankly, why can’t hosts like envs.net behave more like multi-user pods anyway, even if they don’t use the same software? I mean when you think about it, yarnd is nothing more than an implementation of the specs we’re documented with a Web UI. Yes it also has some infra-pods features that “distribute” Twts amongst peers and other such distributes feature. – But if I were an operator of such a “community host” why can’t there be hooks and lookups in place and “automation” that “just works”™?

@lyse@lyse.isobeef.org You’re right I’m sorry I apologize 🤗 I’ve been burning too many hours lately and lacking sleep and courtesy 🤦‍♂️

The point I was (very badly) trying to make was about a canonical way of both saying how one can find your feed and resolve it.