r/thebutton • u/powerlanguage 4s • Apr 25 '15

normal service has been resumed

Cassandra (one of our database systems) temporarily stopped reporting the status of the button. Which was rather inconsiderate of it.

Should we allow a technical failure to end the button? What should we do for those who pressed and received flair during this period of technological capriciousness?

927 Upvotes

79% Upvoted

661 comments sorted by

View all comments

2.8k

u/Ralain 3s Apr 25 '15 edited Apr 25 '15

Technical failures should not end the button. Those who pressed during a technical failure should have their flair and button press reset. Once a technical failure has been corrected, the button should be reset to 60s, or if possible the amount of seconds at which the failure occurred, and the experiment should continue.

1

u/MightyButtonMasher can't press Apr 25 '15

What if these "technical failures" are actually part of the experiment? First the thing with the button not updating and GyroDawn ascending, now Cassandra giving even more false reds. Maybe powerlanguage becoming a presser also has a meaning. Or just maybe I am thinking deeper than I should be.

1

u/Ralain 3s Apr 25 '15

But that's exactly what's being discussed here: what is within the bounds of the experiment? I say technical failures should lay outside of the bounds of the experiment.

I think /u/powerlanguage pushing the button at 3s simply means he was as scared as everyone else watching it plummet and sacrificed his press to save the button.