My guess is that the script ran repeatedly, even after a good connection was established. Telecom companies only billed whole minutes, so a call of 13:01 would be billed as 14 minutes. Or to put it simply, if her script made multiple calls every second, the library would get billed for multiple minutes per minute. If I made fifteen 1-second calls in a minute, I would get billed for 15 minutes of calls in that single minute.
Also, phone companies would typically bill a large flat fee for each long distance call. So making a ton of short calls was more expensive than a single long call. If her script was configured to reestablish the connection in between each upload (instead of simply starting it the once, then uploading multiple times), then the library would get billed a lot of those flat fees for each individual call.
I also found out the hard way that cell phone providers’ “free minutes” plans (back before virtually every phone plan had unlimited minutes) didn’t kick in if the call was started before the time. If your minutes were free after 8PM and you started a three hour call at 7:59, the entire call would be billed, instead of only the first minute.
Based on the description, my guess is that the script solved the problem of having the line interrupted by only doing a single 56k transaction per phone call.
Lots of times, phone calls were billed $$$ for the first minute and $ for every minute after that. If her script only did one transaction per call and not even using the full minute, that could add up fast.
And, given that it took a month for the bill to come, she could have been doing something wrong even during the day. Nobody would have noticed until the bill, and the 1am calls stood out the most when the bill finally came. Maybe there was a local exchange that didn’t require long distance?
I think the bug and the cost were not that the cost was different at that time of day, but that by running at night without worry of interruption her script ran multiple times doing upload after upload after upload. If it had been during the day they would only have a few succeed because the line would get interrupted or couldn’t be used. Maybe during the day they’d only succeed on 3-5 calls but at night the script was making 50, 60, maybe even 70 calls.
Phone services used to have “peak” and “off-peak” hours. Calls made after a certain time, say 7 or 8 in the evening would cost less than calls made during the day. So yes, if it had been during the day it would probably have been more expensive.
While not the same as phone bills, still today electricity changes in cost depending on the time of day. Electricity costs less in the middle of the night. It makes sense to have higher cost during peak demand when charging by usage and there is an impractical bandwidth limit.
Oh there are some details left out that I desperately need to have clarified.
My guess is that the script ran repeatedly, even after a good connection was established. Telecom companies only billed whole minutes, so a call of 13:01 would be billed as 14 minutes. Or to put it simply, if her script made multiple calls every second, the library would get billed for multiple minutes per minute. If I made fifteen 1-second calls in a minute, I would get billed for 15 minutes of calls in that single minute.
Also, phone companies would typically bill a large flat fee for each long distance call. So making a ton of short calls was more expensive than a single long call. If her script was configured to reestablish the connection in between each upload (instead of simply starting it the once, then uploading multiple times), then the library would get billed a lot of those flat fees for each individual call.
I also found out the hard way that cell phone providers’ “free minutes” plans (back before virtually every phone plan had unlimited minutes) didn’t kick in if the call was started before the time. If your minutes were free after 8PM and you started a three hour call at 7:59, the entire call would be billed, instead of only the first minute.
Based on the description, my guess is that the script solved the problem of having the line interrupted by only doing a single 56k transaction per phone call.
Lots of times, phone calls were billed $$$ for the first minute and $ for every minute after that. If her script only did one transaction per call and not even using the full minute, that could add up fast.
And, given that it took a month for the bill to come, she could have been doing something wrong even during the day. Nobody would have noticed until the bill, and the 1am calls stood out the most when the bill finally came. Maybe there was a local exchange that didn’t require long distance?
I think the bug and the cost were not that the cost was different at that time of day, but that by running at night without worry of interruption her script ran multiple times doing upload after upload after upload. If it had been during the day they would only have a few succeed because the line would get interrupted or couldn’t be used. Maybe during the day they’d only succeed on 3-5 calls but at night the script was making 50, 60, maybe even 70 calls.
Also, I hate the name of the column. The frequent mention of the name “Who, Me?” just takes me out.
Also what appears to be a typo, Regomize, but is actually them merging “Register” and “anonymize”.
Phone services used to have “peak” and “off-peak” hours. Calls made after a certain time, say 7 or 8 in the evening would cost less than calls made during the day. So yes, if it had been during the day it would probably have been more expensive.
While not the same as phone bills, still today electricity changes in cost depending on the time of day. Electricity costs less in the middle of the night. It makes sense to have higher cost during peak demand when charging by usage and there is an impractical bandwidth limit.