-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
1.7.0 Nvidia Deprecation Notices #673
Comments
I removed Nvidia from my store list because they are sending their stock to Best Buy. If you check the Nvidia website, you can see that they are showing what other retailers you can buy their cards at. |
Didn't the official communication from Nvidia state that they are "working to improve the experience"? I took that as a temporary measure. Additionally, they also say "In Europe, we will restart fulfilment of Founders Edition products in the coming days and plan to expand our country coverage in due course" - since nvidia-snatcher supports many countries wouldn't this create an issue if you are trying to shop Nvidia exclusively for a FE card? For example, I have changed my country selection to Canada as a test and it still uses the deprecation notice even though the FE card can't be purchased by Best Buy Canada. Would like to confirm if all of the above is working as intended. |
Good question! This deprecation notice is only a notice, it won't stop the functionality. And for future reference, when usually you see 'deprecated` functionality, it just means that it's there, but may not be working or perhaps no longer updated. In this case, it works, but do not know of the outcome. That being said...
I should update the notice only for US stores. Thank you! |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
warn :: nvidia is deprecated in favor of bestbuy
If I receive this new notice does this mean it is no longer checking nvidia and is instead only checking bestbuy?
The text was updated successfully, but these errors were encountered: