Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Live demo sandbox still points to [email protected] #69

Closed
TimvanScherpenzeel opened this issue Jun 13, 2021 · 7 comments
Closed

Live demo sandbox still points to [email protected] #69

TimvanScherpenzeel opened this issue Jun 13, 2021 · 7 comments

Comments

@TimvanScherpenzeel
Copy link
Collaborator

TimvanScherpenzeel commented Jun 13, 2021

Hi @drcmda, I've published NPM version 3.1.0 now that the test suite has been fixed.

Is it possible to update the dependency in the demo sandbox in-place (so that the link stays the same)?

Alternatively users could use https://pmndrs.github.io/detect-gpu/ for now (index.html in the repo).

@TimvanScherpenzeel
Copy link
Collaborator Author

Oh it appears to have upgraded automatically, please ignore

@drcmda
Copy link
Member

drcmda commented Jun 13, 2021

@TimvanScherpenzeel ive updated it :-D but change to any box or environment you like, i just threw the codesandbox in there because the original link went to a 404.

still getting tier 1 fallback for the m1, is this due to apple hiding the gpu? is there anything we can do to work around that?

@TimvanScherpenzeel
Copy link
Collaborator Author

Yes that is sadly the case.

Progress for deobfuscating Apple devices is being tracked here: #47 but came across some major roadblocks. Perhaps now that the project has more visibility another attempt can be made.

@TimvanScherpenzeel
Copy link
Collaborator Author

I've published a patch 3.1.1 which makes sure that if type: "FALLBACK" is rendered the GPU string (both parsed and unparsed) is returned. That way we can more easily catch edge cases.

@Gusted
Copy link
Contributor

Gusted commented Jun 14, 2021

To get an accurate estimate of which device is being used on a safari browser(ios & MacOS) someone should own a good amount of apple devices and test out the results of the floating precision.

What I'm saying - Unless some crazy person wants to sponsor such thing or some apple fanboy has for some reason a lot of apple devices under their bed, I don't see any time soon getting another solution to this problem of gpus being masked.

@TimvanScherpenzeel
Copy link
Collaborator Author

I agree, I have used Browserstack before (which I have access to through my job, on which you can test with physical devices). I can have a look at what I can do. iOS is significantly more doable to narrow down than desktop.

@Gusted
Copy link
Contributor

Gusted commented Jun 14, 2021

Another option is to make this use this precision float thingy a widespread thing as I recently noticed that Firefox will disable the vendor/gpu extension for webgl when you have privacy.resistFingerprinting enabled and thus will result in fallback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants