Endpoint discoverability

Currently the client has a file config.json which stores the authority and the endpoints used e.g.

// config.json

{
    "xmpp":"https://jabber.happy-dev.fr/http-bind/",
    "authority":"https://localhost:8443/",
    "get": { "circles":"https://localhost:8443/circles/", ... },
    "post": { "circles":"https://localhost:8443/circles/", ... },
    ...
}

The endpoints are thus hardcoded, and the knowledge I have of what the circles endpoint is, is implicit

How should it work?

This seems like a reasonably-sized topic

• Automatic WebFinger. My instinct is no
• OpenID Connect Provider Configuration returns a list of supported endpoints and where to find them. I was looking into using an approach like that on Multi User Domain, returning RDF instead of plain JSON
• ActivityPub/Mastodon send everything to an actor's inbox, which exists as a property on the actor's profile
• Linked Data Notifications is similar but has an inbox discovery mechanism (#233 )

A dynamic/universal approach was proposed by Ruben Verborgh using Shapes (#368 )

We could leave this to be a the client application's problem and I think that would be reasonable, which makes this a feature request