3 ms·
Cool. How about adding a way to automatically fire off a web hook after sniffing the information. As in: "Thanks for reporting the issue. Would you mind fol
by jasonkester 14y ago
Cool. How about adding a way to automatically fire off a web hook after sniffing the information. As in:
"Thanks for reporting the issue. Would you mind following this link so that we can get some information about your web browser? https://aboutmybrowser.com/?to=mysite.com/browserhook https://aboutmybrowser.com/?to=mysite.com/browserhook
Or better, let me sign up for an account and register a named webhook with you, as in, https://aboutmybrowser.com/mysite https://aboutmybrowser.com/mysite, that would automatically forward information from anybody hitting it to the webhook url I'd configured at mysite.com.
That would rock.
- prateekdayal 14y agoYep! That's the next step. We wanted to get the MVP out and get feedback from the community. Please follow us on Twitter to stay updated (again, no bullshit and just product announcements) - https://twitter.com/aboutmybrowser https://twitter.com/aboutmybrowser
- telecuda 14y agoYes, this. Even simpler (think phone support) would be to setup http://mysite.com/browser http://mysite.com/browser which points to https://aboutmybrowser.com/?to=mysite.com/browserhook https://aboutmybrowser.com/?to=mysite.com/browserhook and forwards the info to a support agent. The same idea works well for us with http://mysite.com/team http://mysite.com/team pointing to a TeamViewer session.