Hmm. I'd
personally like to see all the "elite" members that garnered that status via forum
spamming participation revoked, and the old rules regarding that status reinstated(I've been buying EVGA since 2008, and was quite miffed by that change). I'd like to see the server capacity adequately addressed on new SKU launch dates during peak hours(so, 6-12 PST), even if that involves leasing extra processing time as well as a bandwidth multiplier service or some sort of reverse proxy on those days to handle the extra load. And lastly, on a technical note, a rework to the code that handles ticketing and queuing.
(Fair warning, this likely wont make sense to anyone who hasn't peeked at the page source for the store and product pages, and it is still rather technical as makes some assumptions about you already understanding the systems at play)
As it stands, the current system loads the notify page into a floating JS element that's effectively 'part of' the current page, so when the server times out trying to process your submission or load the element in the first place(assuming you even managed to get
that far), even if you had a valid token issued from the server, you're now stuck trying to reload the entire store page, which regenerates your tokens for any products visible on said page(whether you're on the main store/category or directly on the page for a given SKU). Someone with experience in such things can easily pick out the URL for the queue registration page that gets loaded into the floating element and manually find their freshly generated token from the page source and then feed it in to the appropriate page to bypass all this and allow them to keep attempting to load the submission page directly, rather than having to load the product page, get a new token(this is all hidden and the average user doesn't even know about it), hit the auto notify button, wait for the floating element containing the queue page to (try to) pop up, put in their info, and then hope that none of those operations timed out or they're gonna be starting over from square one. It took me over 2 hours 45 minutes to get in queue for a 3080 ti because of this(the queue entry page would come up, if I was lucky, I'd try and submit, and it would time out and I'd have to start from scratch rather than just resubmitting, as there was no way to refresh or nav backwards since its not even using a frame to hold the content), before I dug into the page to see about potential workarounds for future drops. Using that knowledge, it only took 12 minutes to get in for the 3070 ti once those came out after I deduced how the system worked - that's a ludicrous advantage for someone with any modicum of background in web technology simply because the site is poorly designed(Put it in a frame at a minimum, or better yet, redirect the user wholesale when they click the notify button and navigate to the notification input page directly. That way it stops regenerating their token(and invalidating the old one) every time a page load/submission times out, breaking the process and forcing them to start over, rather than just letting them attempt to resubmit whichever step timed out). Was there at 6 am for both launches. Not to mention I don't think most people know that, as an example, refreshing the category for a card you're looking at, watching/waiting for a second SKU to drop will generate new tokens and kill your old ones for anything visible on that page, if say, you have the direct product page for one of those SKUs open simultaneously and are trying to queue for it as well. Maybe take the queue button off of the main category page because of this, so people can still watch for secondary drops(the XC3s, for instance), without killing their tokens for anything else they're presently trying to get in line for(at least it throws an error about it that clued
me in, but I'm not so sure that your average Joe would make the connection). I mean, you could use a private browser tab to view the store category while not logged in, so it doesn't kill any tokens you're trying to actively use, but most folk aren't even going to know/think to do that in the first place. I'm assuming the tokening system was put in place in order to stop bots from dumping in queues right at 6 on the dot, hammering the servers, by at least requiring
some user interaction in the way of clicking a button - but with the way its presently designed its actually
hindering said users instead. Not to mention if someone like me could figure it out in about 2 minutes of looking at your unobfuscated client side code and simply poking around until I got it working, you can bet the scummy folks writing bots so they can scalp the things and head straight over to ebay already had it down pat before the cards even went up for sale. It's hurting real humans while probably not even
inconveniencing botters, scalpers, and the rest of the undesirables; put some band-aids on it.
On a slight tangent, whats the deal with the LHR re-release cards and the 3070 ti's getting the KL treatment? I've bought 10 year warranties for every previous GPU I own of yours, and was quite irritated when I realized that wasn't going to be an option for me on the 3070 ti. At least the 3080 ti's are still KR(for now). I'm genuinely considering upgrading to a 3080 ti(queue permitting) and just selling the 3070 ti to a friend simply due to the 3 year warranty issue alone(anyone else remember the good old days when EVGA cards came with a lifetime warranty just for registering within 30 days of purchase?).