indie-config is not supported

[valpackett]

Please implement indie-config. It's a bit strange that you have it on your website, but not in Quill ;-)

[voxpelli]

With indie-config you don't have to have the configuration at the same site as the tools. I would even say that one shouldn't as one might want to use one tool for some actions and some other for others.

It could be useful to have a simpler way of setting up an indie-config – I have some plans on such a tool myself. Something where you can link endpoints to activity types using localstorage.

Best way to host an indie-config will always be to do it at once own site though. Then the config will be shared between all browsers ine has set it up with.

[valpackett]

Not everyone wants to do such advanced configuration. There should be an option to register the tool right in the tool. Even if you so strongly believe that everyone should have it on their websites – consider how convenient this would be for testing client implementations! (I'm working on a vanilla-JS-WebComponent one now)

[aaronpk]

Thanks to @voxpelli's demo of indie-config during IndieWebCamp Nürnberg, I am planning on doing something similar that lets you register Quill as the handler for one or more types!