Report

Because there's many many more people who claim it worked for them. 54 people on one spreadsheet got tickets from 2 session tokens. There were countless other examples out there after this morning.  It was suggested long ago that it was going to work, when the CDN was analyzed before the sale, due to the way it works. Instead of completely killing the session upon a succesful sale, it relied solely on a timer (which seemingly didn't work perfectly either!)   Don't know why it didn't work for you, did you refresh as well, after hitting back? Did you go all the way back to the queue? Regardless, there are an overwhelming amount of people who claim that this is exactly how they secured so many groups on their spreadsheets, people I'd trust too. It should be an easy fix, shouldn't have been left that way in the first place, and hopefully it will be sorted. But I tend to believe the huge number who claim they used it, purely due to the sheer number of them. 

Yes, it was:  I know this because I successfully used one of the links about a minute after the thread was created.  Within minutes it was flooded with users and no one else I know who saw it successfully used it.  I suspect the link was also very quickly removed by the mods, but the Google Sheets doc still existed earlier when I looked.

I can't find the post but someone mentioned that they have been manifesting The 1975 playing the festival for 10 years.    I love this & really hope the person got a ticket if they end up playing this year.   

I am sure if someone can find Matty Healy & ask him about the Glastonbury slot, he will say it straight out...yes hopefully! 

I luckly got in twice on two separate PCs, the back button trick to get multiple ticket for me did not work, and i tried it quickly. no idea why that rumour exists   every session or queue id had a random chance of getting in sooner or later - the browser was not a factor. pressing F5 when i pressed it didn't do much. although i got a bad IP error message when i got frustrated and press it too much - which was game over for that session   the shutting down, no idea, that sounds like a operating system thing, nothing to do with seetickets