parsonjack

Yes but on most browsers it's not simple to remove specific cookies....most have the option to individually remove Cache, Cookies, Browsing History, or all of them with tick boxes, but not cookies for individual sites etc without digging into deeper options.

No probs with deleting all cache and cookies ahead of the sale. You may just need to ok the prompt to accept cookies when you next first open the Seetickets page....and possibly the same on other websites you use. You might also get logged out of some sites, including this one, and just need to log back in again. All best done in advance of 0900 tomorrow obvs.

Yes....clearing all cache and cookies ahead of the sale is a precautionary 'must do'.

Yes.....now I could be wrong but I think this is because See have switched their system back over to the servers in use before the Coach sale. Pre-Coach sale See were advertising a single IP address via DNS, then on Thursday they switched and started advertising 5 x IP addresses (same as for 20222 sale....)....they've now today switched back to the single IP so it could be that this is a different version of the 'busy' page than on the 5 x IP servers.

You just need to stop it manually before you start entering your reg details. If it fires once or twice before you can you'll still get the booking page back so no great panic.

No. It's the same page...so nothing to distinguish, but see previous post regarding how you *could* check and why you probably wouldn't want to.

Yes....this is what everyone needs to understand....the page you get when you refresh too quickly is the same page as the genuine 20 second 'hold' page that we all see. If you interrogate the browser activity when you refresh too fast there is a redirect to that page when you issue 'too many requests', but given that checking for this every time you get the hold page is somewhat time-consuming in the process it's best to place all efforts into staying within the limit instead.

Yes. But if the 'fake' hold page looks the same as the 'real' hold page then unless you're very careful with your F5 rate you won't know which you've been given. It seems to only let you back in once your F5 rate falls below 60/minute but, again, unless you know your rate is within the limit you may be stuck with it for the whole sale.

Recent thoughts are that See can differentiate between devices on a shared IP by reading the connection port that each outgoing connection is randomly assigned by the router.

Same here in Frome...where are you?

So the big question is did you tell him?

It's not known for definite but it's a reasonable certainty that each device will be seen by See as distinct even where they may be sharing the same IP. To minimise any risk try to split connections between WiFi and 4/5G as much as you can do.

Go back, then resubmit the page.

Interesting theory but countered somewhat by the existence of any 'queue' in See's system being likely fictitious. Load-balancing distributes requests across an unknown number of mid-tier application layer servers, each set up to serve a pre-determined number of concurrent sessions. Once the session limit is reached a redirect presents the 'queue' page which as we know automatically retries a connection after 20 seconds or when manually F5'd. No real 'queuing' at any stage therefore. The other point is that if there was such a redirect when just multiple hits were detected we'd all be seeing the busy page on ticket day and no-one would be getting through. As for your success at a 0.5 second refresh rateI I can't exactly explain why this didn't present an issue, although it is possible that on a massively congested system a number of your requests don't get through, therefore keeping you under or around the 1/second rate as a result.

The limit is less about resources and more about spotting potential 'bots' that would limit the opportunities for others to buy tickets.

Yes good point..... probably pre-70's then, possible early 60's when he would have been early 20's. I'll ask him.

I wish $$$$

My Uncle was issued "JOE 1" on a Hillman Imp back in the 70's. There was no value or trade in such things then so as his name is Colin he let it go with the car when he sold it. I shudder think of current value .... 😬

Because for the right plate they are actually a better investment right now than watches, jewellery or classic cars. Returns over just 12 months can be way in excess of most financial investments apparently.

MyHab were the company that went bust in 2011. Anne Goode's fields were rented out to Tangerine Fields who still use them. I've no knowledge of the Goode family being involved with it other than making a few quid from TF....

Not podpads.....it was MyHab. We were booked in for 2011 when they went bust just 2 days before the festival. Michael bought in The Green Tent Company at short notice. That's what then became Worthy View.

I can't find the recent post right now (so apologies to the author...) but the best theory at present is that See use the Port number assigned to each data connection using a shared Public IP address to differentiate between devices using that Public IP address. The port number is assigned to each outgoing connection by the router, and is included within the data that See receive, and they can therefore differentiate accordingly. The port number then allows the router to pass returning traffic to the correct Private IP address.

Stick with See....they might be a sh*tshow but at least we're reasonably clued up as to how the system works and how to game it.. even if only a tiny bit.

Reasonable evidence to suggest it's per device....so if there's 2 of you with 2 windows open each you could refresh each window at 30/min. Yes that would equate to 120/min overall on same IP if you're on a shared wifi connection but it's reasonably certain See differentiate between devices on that similar IP so you should be ok. If in doubt then have one device on WiFi and the second on a 4/5G hotspot so you definitely then have 2 distinct IP's.

I use Chrome for all of them. You'll see folks suggesting why splitting across different browsers could give you an edge as they *could* be seen by See as separate sessions and therefore allow you a greater F5 rate but it's mostly anecdotal.