You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flagon.apache.org by GitBox <gi...@apache.org> on 2021/03/24 02:34:02 UTC
[GitHub] [incubator-flagon-useralejs] poorejc opened a new issue #71: Update detect-browser method for Browser Meta Data in Client Logs
poorejc opened a new issue #71:
URL: https://github.com/apache/incubator-flagon-useralejs/issues/71
current method is 'detect-browser'. Adds run-time dependencies (overhead).
explore more modern fingerprinting methods as alternative:
example of such a library:
fingerprintjs
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-flagon-useralejs] UncleGedd commented on issue #71: Update detect-browser method for Browser Meta Data in Client Logs
Posted by GitBox <gi...@apache.org>.
UncleGedd commented on issue #71:
URL: https://github.com/apache/incubator-flagon-useralejs/issues/71#issuecomment-811107178
The `detect-browser` library currently sits at [25 kb](https://www.npmjs.com/package/detect-browser), while `fingerprintjs` is [256 kb](https://www.npmjs.com/package/@fingerprintjs/fingerprintjs). Is the goal of this ticket to swap `detect-browser` with something more modern or to roll our own browser detection to remove our one and only runtime dependency?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-flagon-useralejs] UncleGedd commented on issue #71: Update detect-browser method for Browser Meta Data in Client Logs
Posted by GitBox <gi...@apache.org>.
UncleGedd commented on issue #71:
URL: https://github.com/apache/incubator-flagon-useralejs/issues/71#issuecomment-825092283
Trying a couple of things here:
1. Using a duck-typing feature detection method to detect the browser (see this [SO post](https://stackoverflow.com/questions/9847580/how-to-detect-safari-chrome-ie-firefox-and-opera-browser)). This is fancy and all but it's not accurate on my version of Chrome 90
2. Basically replicating what `detect-browser` is doing by looking at the user agent
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-flagon-useralejs] confusingstraw commented on issue #71: Update detect-browser method for Browser Meta Data in Client Logs
Posted by GitBox <gi...@apache.org>.
confusingstraw commented on issue #71:
URL: https://github.com/apache/incubator-flagon-useralejs/issues/71#issuecomment-811136456
i think they offer two different things. `detect-browser` tells us which browser we're running in (mostly via a set of User-Agent regexs), `fingerprintjs` tries to identify the _individual computer_ that is running the page. it does this by gathering a bunch of runtime info about the browser (which APIs/hardware are available, how do they look, etc.) and generating a fingerprint.
my suggestion before was that we could probably just do our own `detect-browser` work, and remain dependency-free. the `fingerprintjs` mention was a bit tangential, as user identification has been of interest to the project before.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org