Consider a .well-known/polymath

[dalmaer]

For sharing information such as the endpoint name, directory, etc.

https://en.wikipedia.org/wiki/Well-known_URI

[jkomoros]

I was thinking about this, the fact that endpoint is now just one endpoint will be limiting to us. In the future you might want to have multiple things. Just thinking off the top of my head:

1) query (good ole' query) 2) info - The information covered in this item. It might include things like the embedding_model in use, the version of the endpoint, whether or not it gives more results with an access_token, 3) directory - for endpoints that also want to host a public directory (ala #111 )

Likely more, my point is more that a single actual endpoint + a .well_known won't be sufficient for the expected future behaviors we'll likely want

[dalmaer]

What are query, info, directory in this? I was assuming .well-known would be the trusted pointer to all the things. And <link rel=""> and the equiv header can also be a pointer, etc etc.

[PaulKinlan]

I like the idea of a ./well-known/polymath.json. It's worth looking at other well-known well-known files.

ActivityPub uses webfinger: e.g https://paul.kinlan.me/.well-known/webfinger - which points to a list of Activity Pub endpoints amongst other things. (Dion, this could be augmented to point to a list of polymath endpoints - just have an application/json+polymath content-type).

Change-password: https://github.com/.well-known/change-password just redirects to the users change-password page (great for integration in the browser) - might be interesting to explore.