.poorly-known

Unfortunately. It's a great solution to a problem lots of tools face. A pity that people trying to establish new standards aren't aware of it aparently.

I'm a little disappointed there's no standard for /.well-known/list that points to things made available under /.well-known/ on that domain.

Doesn't need to be everything, just ones you want discoverable. Only other way to do it is trying every one you know.

Good idea actually. You could just make /.well-known an index page

Ah, just like AT Proto when it was released, introducing compatibility hazards and security vulnerabilities by putting stuff in the root rather than in .well-known. Sigh.

Did we?

Yes: https://news.ycombinator.com/item?id=35820368.

Ah, that's right. Forgot about that one.

No. That is for the host/domain entirely not a specific stream.

I might want several directories in the future, and even if I don't, I might want it separate from my .well-known robots.txt. Many, many reasons I can think of not to blend these.

Bad idea.

The current design has the same limitation of applying to the domain as a whole, but has potential name clashes that .wellknown would avoid.