Unknown browser API

[Robert Labrie]

Maybe there are good reasons against this, but what about setting up an endpoint in the cloud somewhere for apps which use browscap data to submit unknown browsers. Might help speed along adding new strings. Let me know.

Cheers,
Rob

[James Titcumb]

Hi Rob,

I have no strong feelings against this really, but how much difference would there be in the current process? There is a caveat at the moment which requires reporters to have GitHub accouts to report issues, but I feel that most developers these days will have a GitHub account, and it's not difficult to sign up for free.

The current process tends to be people report UA strings, and then we have to figure out exactly what they mean by researching them. Sometimes it's obvious, sometimes not quite. I just don't know how having a custom place to report, rather than using an existing, familiar issue reporting system, would benefit?

If I've missed something, please do point it out though, I'm always open to suggestions!

Thanks
James

[Robert Labrie]

I think probably unknown browsers are going unreported. I'm planning to put something together in node.js to support my app, just to see what shakes out.