Well the first thing to ask yourself is where your bottleneck is. If the site is slow and high latency because your servers are collapsing under the sudden load, that's what you need to fix. The fact that everyone is making round trips to Utah or whatever is largely irrelevant.
If it's slow because the WiFi at the conference is congested, you could probably speed it up by caching and serving static assets locally, but this would require a lot of cooperation from the WiFi provider at the event. You could map the DNS for your CDN to a locally hosted server.
You could set up your own WiFi (if the organizers let you do that), but unless you want your users to have to constantly switch networks, you'll need a fat enough pipe to your own WiFi to serve ALL of the bandwidth needs of your users.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well the first thing to ask yourself is where your bottleneck is. If the site is slow and high latency because your servers are collapsing under the sudden load, that's what you need to fix. The fact that everyone is making round trips to Utah or whatever is largely irrelevant.
If it's slow because the WiFi at the conference is congested, you could probably speed it up by caching and serving static assets locally, but this would require a lot of cooperation from the WiFi provider at the event. You could map the DNS for your CDN to a locally hosted server.
You could set up your own WiFi (if the organizers let you do that), but unless you want your users to have to constantly switch networks, you'll need a fat enough pipe to your own WiFi to serve ALL of the bandwidth needs of your users.