This weekend I was looking for a side project to play around with Go so I built a simple web experiment to test the self control of the internet: it has a single button, a live click counter, and a timer. I want to see how long the internet can collectively resist clicking it.
The backend is a very simple Go binary with Go's std http server, web sockets, a WAL-style log of clicks, plain CSS and Comic Sans.
Inspired by Silicon Valley's (HBO series) Bro app, OneMillionCheckBoxes and Cookie Clicker
This is really cool, now I'm tempted to add some kind of interactive element like this to my website. reminds me of the 2000s internet online user/views counters
I'm mesmerised by how many people take time to click all these! :D
It has been updated by people from: AE, IT, FR, US, IN, BE, GB, AU, PL, MX, DK, BR, JP, DE, CH, IL, SK, ES, SE, CA, NL, AR, NZ, PF, IS, CO, CL, GE, PT, RO, FI, PH, CZ
Yeah hahah, I suspect a lot of the clicks have already been automated, when I went to sleep it was at around ~4k clicks and in the morning it had gone up to 140k clicks
Curious to see how much load/clicks the hacky Go code will handle
I was thinking about your logging/storage. If for every click you log action/IP/date/time/etc, 100-200 bytes of text and I gave you about 1000 clicks with my auto-clicker in a couple of minutes, and if 10-20 people like me do this and leave it running while we watch LotR-extended, could we hurt your storage?
At 100ms per click, 1sec = 10 clicks, 600 per min, 36000 per hour, x4 h for LotR-Ext = 144k x 200 bytes x 20 people = 576,000,000 bytes, nope we won't hurt your storage if you log 200 bytes per click :)
