The cashier has no way of knowing that the person he/she calls is actually the cardholder. If the card were stolen, the thief could give the cashier a friend's number and the friend could pretend to be the cardholder. The cashier was right to call in the police.
None of those suggestions would have helped, since the card apparently had actually been reported stolen to the credit card company. Given that, there is no way he/she would be leaving that store without the involvement of the police. Might as well call them in as early as possible and get it over with.
All the credit card company knows is that the card was reported stolen. If the cashier calls them, they will tell the cashier to call the police. The credit card company is not going to call the mom to verify. She already reported the card stolen. The cashier is right to assume that the driver's license is fake (made to match the card), or perhaps that the license was stolen along with the card and doctored or is being used by someone who looks similar. Given that, there is no easy way for the cashier or the credit card company to verify that the person in the store is authorized to use the card.
RTFA. In this case, he was paying an installation fee after the fact. A day after the fact, in fact. Best Buy called him up at home and demanded that he come back in to pay this outstanding debt.
I have heard of an incident where the governor of New Mexico was mistaken for a foreign observer by another state governor at a meeting of state governors.
It didn't take that long for $1 bills to disappear when Canada switched. Small bills typically last less than two years in circulation before they are too worn to be used. The banks send worn bills back to the government for replacement.
Of course, if you had $2 bills (or coins) in common circulation, you would have to carry a lot fewer $1 bills (or coins). $2 bills are very convenient.
You can't get power out of an endless chain. Thermodynamics doesn't allow it. You can't get more energy out of a system than was put into it. (Fossil fuels and nuclear power systems are not an exception. They are just cases where the energy was stored a long time ago and is now being extracted.)
I think it's more likely that the industry would have fought against the expense of implementing airbags even if there had been no patent and no licensing fees.
On the other hand, I have often noticed that material safety data sheets are sometimes unreasonably dire in their warnings, and tend to always prescribe the most extreme measures imaginable without regard to the extent of the possible exposure.
Don't believe me? Look at the data sheet for table salt. "Lab Protective Equip: GOGGLES; LAB COAT; PROPER GLOVES", "In the event of a fire, wear full protective clothing and NIOSH-approved self-contained breathing apparatus with full facepiece operated in the pressure demand or other positive pressure mode.", " Ventilate area of leak or spill. Wear appropriate personal protective equipment as specified in Section 8. Spills: Sweep up and containerize for reclamation or disposal. Vacuuming or wet sweeping may be used to avoid dust dispersal.", "Containers of this material may be hazardous when empty since they retain product residues."
Oops, I forgot to wear my goggles and gloves when I had dinner this evening. I wonder if I'll live.
To be fair, I think that MSDS's are written with mass industrial processes in mind. Perhaps you have to be a bit more careful if you're working with a thousand tonnes of finely-ground salt. Still, MSDS's do not seem to me to be a very good guide to the overall hazardousness of a substance, especially when they say something as vague as "THE CHEMICAL, PHYSICAL, AND TOXICOLOGICAL PROPERTIES HAVE NOT BEEN THOROUGHLY INVESTIGATED."
How are you going to coordinate that all businesses and organizations do the change at the same time? Or are you just going to have to remember which ones are changing this week, which ones are changing next week, and which ones are not changing at all? It's a heck of a lot easier to just change the clocks. Everybody stays in synch, and businesses don't have to reprint everything that has their business hours on it.
Because while you can change your business' working hours, you can't force your suppliers and customers to change too. Having individual companies each set their own 'standard' business hours as an alternative to DST would in some cases ensure that little gets done in the first or last hour of the day, and in others would force businesses to go from an eight hour working day to a nine hour working day. The only way this could possibly work, is if the government mandated that all businesses, schools, etc. shift their standard business hours, which is more or less what they have done. The mandated changing of the clocks is just a convenient way to shift everybody's business hours at once, and keep everything synchronized. It also eliminates the need to change printed schedules. If everybody was going to shift their working hours on their own, every business would have to change their business hours signs. Every bus and train schedule would have to be reprinted, etc.
NiMH's seem to fade too fast if you're not using them. I use alkalines for most things that don't get used regularly, which is by far the majority of my battery usage. I don't want to have to recharge the battery in every clock and remote control every few weeks. I experimented with rechargeable alkalines for a while, but they're kind of a pain too because if you drain them completely they die.
Wow, what a stupid business model. If millions depend on a message getting through, it shouldn't be going via email with no automatic confirmation of receipt. Anybody whose business is destroyed when (not if) this fails, deserves what they get for being so stupid.
Well, when you are running ISP with ONE HUNDRED EIGHTY THOUSAND IP addresses, I guess it is not so easy to know what each and every one of them does.
Perhaps. It depends what they were doing. It shouldn't be that hard to automatically monitor for IP addresses pumping out millions of spam emails. That aside, I don't necessarily expect an ISP to know what is going on on each of their IP addresses, but I certainly expect them to respond when they are informed that there is a problem. Any ISP that fails to take appropriate action deserves to be blacklisted. Their innocent customers are victims of the ISP's negligence, not of the blacklist.
The problem is that too many ISPs profit hansomely by providing internet service to spammers, but deny any responsibility. There's no good way to resolve that short of blacklisting. The ISP's are free to run their domain however they see fit, but others are not obliged to carry their traffic.
...decided to blacklist ENTIRE The Planet, because of alleged spam support. Which consist of total 7 (seven) "incidents" in last 3 years.
Depending on what these 'incidents' consisted of, and how the Planet responded, that may well be six incidents too many. If the blacklisting inconveniences you, you need to find a better ISP. (Yes, a better ISP may be more expensive. You get what you pay for.)
I agree with you, except that it's not entirely clear that the business model is unethical. If a company writes code based on a GPL'ed program and keeps that modified program in-house that's clearly fine. If a company and a customer find that it is mutually beneficial for the latter to pay the former for a custom program, and then for both parties to keep that program just to themselves it's the same thing. It's just a bigger 'house'. Of course, this relationship can be spoiled by either party so it will only work in a situation where it is in both parties' interests.
I haven't looked into it closely, but I suspect that if someone leaked the code without authorization, the leaker would be in violation of copyright since he was not licensed under the GPL or otherwise to distribute the code. Anyone receiving the code from the leaker would not have any rights under the GPL, for the same reason. The GPL says "if you distribute copies of such a program...you must give the recipients all the rights that you have". It doesn't say you have to give those rights to anyone else. People seem to think of the GPL as some magical property that attaches to the software. Fundamentally, it is a legal agreement between the distributor and the recipient of the software that authorizes the recipient to redistribute the software and imposes some restrictions on both parties.
No, you have misunderstood. You cannot give binaries to customers without releasing the source to those customers. The GPL gives you the option of allowing public access to the source code instead, but this is not required.
Yes, but if you paid $100,000 for a piece of software would you give it to someone else for free? What if the software were custom-written for your business, and would only really be useful to your competitors?
I disagree with you about excluding his ISP from responsibility here. If MAPS is working the way they should be, then this subnet would not have been blocked unless the writer's ISP had failed to deal with a problem that had been previously reported to them. His ISP's customer service has everything to do with the problem he experienced.
That's all fine, but still the most likely explanation for the problem that you had, is that your ISP did not do a good job of controlling spam originating from its IP block, and of responding to complaints about that spam. Your best strategy to prevent this kind of impact on your business is to use a more reputable ISP.
The fact that the sale is 'private' isn't the point. The issue is that you're only obligated to give the source to the people to whom you give/sell binaries. If you give the binaries to five customers, you have to release the source to those five customers. If you release the binaries to whoever wants them, you have to do likewise with the source. Simple.
As others have pointed out, the customers receiving the binaries and source are free to redistribute them, and probably cannot be constrained from doing so by any non-disclosure agreement..
Betcha that putting jamming equipment on top of hospitals and schools violates whatever rule of warfare forbids bombing hospitals and schools. You can't mount an antiaircraft gun on an ambulence, either, and expect it not to get bombed.
Slashdot Mirror
The cashier has no way of knowing that the person he/she calls is actually the cardholder. If the card were stolen, the thief could give the cashier a friend's number and the friend could pretend to be the cardholder. The cashier was right to call in the police.
All the credit card company knows is that the card was reported stolen. If the cashier calls them, they will tell the cashier to call the police. The credit card company is not going to call the mom to verify. She already reported the card stolen. The cashier is right to assume that the driver's license is fake (made to match the card), or perhaps that the license was stolen along with the card and doctored or is being used by someone who looks similar. Given that, there is no easy way for the cashier or the credit card company to verify that the person in the store is authorized to use the card.
RTFA. In this case, he was paying an installation fee after the fact. A day after the fact, in fact. Best Buy called him up at home and demanded that he come back in to pay this outstanding debt.
I have heard of an incident where the governor of New Mexico was mistaken for a foreign observer by another state governor at a meeting of state governors.
It didn't take that long for $1 bills to disappear when Canada switched. Small bills typically last less than two years in circulation before they are too worn to be used. The banks send worn bills back to the government for replacement.
Of course, if you had $2 bills (or coins) in common circulation, you would have to carry a lot fewer $1 bills (or coins). $2 bills are very convenient.
You can't get power out of an endless chain. Thermodynamics doesn't allow it. You can't get more energy out of a system than was put into it. (Fossil fuels and nuclear power systems are not an exception. They are just cases where the energy was stored a long time ago and is now being extracted.)
I think it's more likely that the industry would have fought against the expense of implementing airbags even if there had been no patent and no licensing fees.
Don't believe me? Look at the data sheet for table salt. "Lab Protective Equip: GOGGLES; LAB COAT; PROPER GLOVES", "In the event of a fire, wear full protective clothing and NIOSH-approved self-contained breathing apparatus with full facepiece operated in the pressure demand or other positive pressure mode.", " Ventilate area of leak or spill. Wear appropriate personal protective equipment as specified in Section 8. Spills: Sweep up and containerize for reclamation or disposal. Vacuuming or wet sweeping may be used to avoid dust dispersal.", "Containers of this material may be hazardous when empty since they retain product residues."
Oops, I forgot to wear my goggles and gloves when I had dinner this evening. I wonder if I'll live.
To be fair, I think that MSDS's are written with mass industrial processes in mind. Perhaps you have to be a bit more careful if you're working with a thousand tonnes of finely-ground salt. Still, MSDS's do not seem to me to be a very good guide to the overall hazardousness of a substance, especially when they say something as vague as "THE CHEMICAL, PHYSICAL, AND TOXICOLOGICAL PROPERTIES HAVE NOT BEEN THOROUGHLY INVESTIGATED."
The grandparent's point was that 6.8 > 3.9, so if the tubes aren't needed 12 hours of the day, turning them off extends their useful life.
How are you going to coordinate that all businesses and organizations do the change at the same time? Or are you just going to have to remember which ones are changing this week, which ones are changing next week, and which ones are not changing at all? It's a heck of a lot easier to just change the clocks. Everybody stays in synch, and businesses don't have to reprint everything that has their business hours on it.
Because while you can change your business' working hours, you can't force your suppliers and customers to change too. Having individual companies each set their own 'standard' business hours as an alternative to DST would in some cases ensure that little gets done in the first or last hour of the day, and in others would force businesses to go from an eight hour working day to a nine hour working day. The only way this could possibly work, is if the government mandated that all businesses, schools, etc. shift their standard business hours, which is more or less what they have done. The mandated changing of the clocks is just a convenient way to shift everybody's business hours at once, and keep everything synchronized. It also eliminates the need to change printed schedules. If everybody was going to shift their working hours on their own, every business would have to change their business hours signs. Every bus and train schedule would have to be reprinted, etc.
NiMH's seem to fade too fast if you're not using them. I use alkalines for most things that don't get used regularly, which is by far the majority of my battery usage. I don't want to have to recharge the battery in every clock and remote control every few weeks. I experimented with rechargeable alkalines for a while, but they're kind of a pain too because if you drain them completely they die.
It might cost you $200,000 and take eight months longer, then. Depending on the business needs, that might not be OK.
Wow, what a stupid business model. If millions depend on a message getting through, it shouldn't be going via email with no automatic confirmation of receipt. Anybody whose business is destroyed when (not if) this fails, deserves what they get for being so stupid.
Perhaps. It depends what they were doing. It shouldn't be that hard to automatically monitor for IP addresses pumping out millions of spam emails. That aside, I don't necessarily expect an ISP to know what is going on on each of their IP addresses, but I certainly expect them to respond when they are informed that there is a problem. Any ISP that fails to take appropriate action deserves to be blacklisted. Their innocent customers are victims of the ISP's negligence, not of the blacklist.
The problem is that too many ISPs profit hansomely by providing internet service to spammers, but deny any responsibility. There's no good way to resolve that short of blacklisting. The ISP's are free to run their domain however they see fit, but others are not obliged to carry their traffic.
Depending on what these 'incidents' consisted of, and how the Planet responded, that may well be six incidents too many. If the blacklisting inconveniences you, you need to find a better ISP. (Yes, a better ISP may be more expensive. You get what you pay for.)
I haven't looked into it closely, but I suspect that if someone leaked the code without authorization, the leaker would be in violation of copyright since he was not licensed under the GPL or otherwise to distribute the code. Anyone receiving the code from the leaker would not have any rights under the GPL, for the same reason. The GPL says "if you distribute copies of such a program...you must give the recipients all the rights that you have". It doesn't say you have to give those rights to anyone else. People seem to think of the GPL as some magical property that attaches to the software. Fundamentally, it is a legal agreement between the distributor and the recipient of the software that authorizes the recipient to redistribute the software and imposes some restrictions on both parties.
No, you have misunderstood. You cannot give binaries to customers without releasing the source to those customers. The GPL gives you the option of allowing public access to the source code instead, but this is not required.
Yes, but if you paid $100,000 for a piece of software would you give it to someone else for free? What if the software were custom-written for your business, and would only really be useful to your competitors?
I disagree with you about excluding his ISP from responsibility here. If MAPS is working the way they should be, then this subnet would not have been blocked unless the writer's ISP had failed to deal with a problem that had been previously reported to them. His ISP's customer service has everything to do with the problem he experienced.
That's all fine, but still the most likely explanation for the problem that you had, is that your ISP did not do a good job of controlling spam originating from its IP block, and of responding to complaints about that spam. Your best strategy to prevent this kind of impact on your business is to use a more reputable ISP.
As others have pointed out, the customers receiving the binaries and source are free to redistribute them, and probably cannot be constrained from doing so by any non-disclosure agreement..
I would be fine with it being integrated, if it were off by default.
It's rock. Silica is pretty resilient.
Betcha that putting jamming equipment on top of hospitals and schools violates whatever rule of warfare forbids bombing hospitals and schools. You can't mount an antiaircraft gun on an ambulence, either, and expect it not to get bombed.