Timeout isn't the only way. You could set a version variable on pageload, and have a conditional version check on init. If the versions match and localstorage exists, load from localstorage, if not, grab from the server and update.
It's a strange loop, actually. The requiring attribution would be more restrictive, since the current license does not require attribution. If you re-license it with a license that does not require a less restrictive license, and then license it again with a license that is more restrictive, then you've violated the original one.
Logically, it implies "You can only release it under this license".
That is, the license says, "This is obvious, and doesn't need a license", and is a joke.
In the last hybrid I got a ride in, if you were drawing too heavily on the gas engine, the console backlighting would go from a soothing bluish-green to an angry red. Rather dramatic feedback, but I could feel myself responding to it - and I was a passenger.
There's a particular hybrid car out there that actually does have that if you drive outside of "environmentally sound" parameters... i.e. too hard of accelerations or high speeds. The idea is to encourage driving in such a way that maximizes your mileage, thus making the trees happy.
The first image that would come to my mind is the leaves swirling in my wake as I press the pedal to the floor around a fun corner (observing all proper speed limits and common sense, of course).
It seems that some designs are justified by people seeing a design they like, rationalizing it after the fact, and applying their rationalization in a way that is too general, without considering other ways the design could be interpreted.
This is a terrible a tragedy to befall a member of the nodejs community. I have alway believed that the compassion of the internet community comes through when things like this happen. C'on guys, lets help a brother out!
