For a very long time I ran publicly accessible NTP servers. Usually this required little to no maintenance, sometimes we'd get hammered (like when a large ISP rebooted all of their customers boxes at the same time). But usually it wasn't a big deal.
Now, when you have hundreds of thousands of people using your services, it doesn't take many people who have decided you are going to fix their problem, as a percentage to get overwhelmed. Mostly users were great, but there were a few...
My company provided Linux support, and our support number included an option users could select that was prefaced with "If you are an existing customer and are having a service impacting emergency, press 1 to receive a call back from a technician within 15 minutes."
This system would allow them to leave a voicemail and then would log a bug in our tracking system and would start calling our senior on-call tech and their backup, 24 hours a day. It was either the second or third time in a week this happened, and I replied with a "You are not a customer, this is not a service impacting outage, and you are reporting our servers replying to your computer's requests for time service."
The level of vitriol I received in return convinced me it was time to stop offering NTP as a public service.
Most people will spend some time understanding what is going on before reaching out to someone they've never heard of before, expecting them to fix the problem. But if you have enough people using something you provide, you will run across people who have huge expectations of you and get pissed off if you don't fix their problem.
Did you charge callers. I wonder if "you will be billed £20 for this call [or $30 or whatever]; current customers will have this cost refunded" would be enough (even if you never charged) to put people off.
Alternatively, why not just require the customer to enter their 10+ digit account number to proceed further?
So, it was definitely a judgment call about if we should add something requiring a special code for access, charging, etc... In this case, we had to make the judgment call about implementing something like this, or stopping public NTP service.
Part of the equation also included that pool.ntp.org was now available and fairly well populated, when we started offering NTP service it wasn't a thing.
As for "if the customer gets angry at the response, it's fine...", well, what if you're taking the time to reply and then getting angry responses? What a waste of emotional energy.
Personally I'd agree that the correct thing to do is not to reply, there's only so many hours in the day, and there's really _nothing_ he can do to fix anything.
Never underestimate desperate people's selective deafness; when you want to solve a problem, you will filter out everything between you and it, and will see only "place $VERB in the subject of your email". The false positives from this method will be the most desperate, and probably the least congenial.
I have a TextExpander snippet auto-reply. Takes me maybe 10 seconds to reply to a given email. It's hard to give advice without knowing the rough volume of the emails the author deals with; I can imagine situations where this would be a perfectly viable strategy, or times when even that would be an unreasonable amount of work.
If you don't want to receive e-mails, don't put your e-mail.
If you just want to receive some kind of e-mails (like just congrats but not bugs), add that information in the end. Of course some people won't comply, but that's just human behavoir.
Now, just putting your e-mail and letting the black hole eat them without an answer is very disappointing to those who took their time to read the license/about/readme, find your e-mail, put their hope that you're able to help them in some problem, and then... nothing.
Edit
Yes, I did read the thread, the original post, and so on. I'm just putting myself in the position of the average costumer, or not-so-average, that took time to read the available documentation and tried to fix something, or to ask for a new feature, or anything else. He isn't receiving spam. I'm not suggesting, either, that he should address the problem or even find out who's the correct person to blame inside the company X that did the GUI of the radio for the company Y that finaly sold it to DENSO that will sell it to Toyota...
One way to fix would be, for example, changing the license in any future version to read "If you're using this software inside any component that will be used in a car, you should display the Copyright_automotive.txt contents instead of this one".
Edit 2
As far as I could find (in https://curl.haxx.se/docs/copyright.html), I would never blame regular car users, not even some tech users, if they couldn't find what Daniel is responsible for. The license just says:
---
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1996 - 2016, Daniel Stenberg, [email protected], and many contributors, see the THANKS file.
All rights reserved.
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.
---If you read that and can find where it says that it's not about the GPS, the mapping of the Electronic Fuel Injection, the windshield wipers, or something else, or even that it's about some specific piece of software, please, just point it out.
He is not obligated to answer every email he receives.
He is certainly not obligated to play first-tier tech support for anyone who happens to purchase a product that uses curl.
Trust me, that wouldn't fix it. As someone who works for a company whose name resembles a popular Microsoft product, putting in disclaimers (in our case on our support contact form) doesn't help one bit. They don't care.
maybe you would be getting 2x the support calls without the disclaimer, even if this number is unchanged from before the disclaimer
My last job was managing the support for a smaller university, and every so often we'd get people who just searched "Help Desk" and somehow stumbled onto our University Help Desk phone number. They'd get insanely frustrated when, rather often, we were completely unable to help them because the product was too niche or specific for my technicians to even begin to know how to troubleshoot; we had low enough call volume that the free publicity for the school after helping strangers more than offset the time spent solving a problem that wasn't ours to solve. But when the callers would get really upset and disgruntled, I'm not entirely sure what they expected, especially since my technicians would make it perfectly clear that we weren't a generic Help Desk, we were specific to a university. I have plenty of sympathy for them not being able to get good support through the correct channels, but when you know you're not at the right place and just hoping, it doesn't seem fair to peg blame on the people you know are the wrong people to contact.
Edit to reflect your edit:
I would imagine that the part that reads "THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,..." should give away that this is not for support. Also that it doesn't read like a support document at all, and that it's not included in the car's support manual, and that the email doesn't mention Toyota at all. If they email that address from that page, they're not reading the file, they're just scanning for an email address. I'm not saying people who do this are idiots or anything of the sort - as someone who loves helping with tech issues, I sympathize and even empathize after having crap service from many companies. But the people are creating their own disappointment.
Why would he know anything about the delay in audio and video when connecting through bluetooth? Or about the GPS?
He's happy to get emails about curl, even bug reports.
Have you ever had a customer service or tech support job? This line would just be used as a further launching point for an angry and argumentative person. Expect replies as "Thanks asshole" or "Surely you must know someone there who can help, instead you collect your big six figure salary while us working joes get stiffed," etc.
When I did tech support for $electronics_company, you would not believe the negatively you're on the receiving end of. The author is clearly making the correct move. Why be on the receiving end of negativity when you don't need to be? Yes, maybe there are people like you out there who would appreciate a short response, but you're maybe 1% of the population in regards to this. Argubaly, if you don't know what a FOSS copyright statement is and start emailing any email you find, more than likely you're not going to be the tech wizard who is thankful for a reply. You'll be the pissed off guy with a radio that doesn't work and see any reply as a smug 'piss off.'
I think one of life's tough lessons is that you can't help everyone and that discriminating who you let into your life is very important.
(I already ruled out the spark plugs and coils by swapping them around, and told them of this in writing, but they still told me that was the problem without running a compression test...)
I mean, a single web search would reveal that the person probably doesn't work for <insert brand>. Would you email somebody about a Toyota car if their address wasn't "[email protected]" or something? Besides, if they had bothered to read the license, it's clear it comes "WITHOUT WARRANTY OF ANY KIND".
Also, many companies make it intentionally hard to find a contact address. Mr. Stenberg shouldn't be disadvantages because some company which doesn't care about customer relations has decided to use his excellent piece of open source software.
> I’ve learned over the years that just trying to explain how I have nothing to do with the product they’re using is often just too time consuming and energy draining to be worth it.
Responding to emails can be way more draining than you'd expect.
I think it's easy to say that "it's fine" without stepping into Daniel's shoes, but the responder still has to carry some of the emotional weight of that interaction through the rest of his day. I don't blame him one bit for wanting not part of that.
Remember, this is customer service. You and many others may be nice and have reasonable expectations, but it's the outliers that sour the whole experience. I also would not opt-in to wasting my time and energy on these responses.
I work for a small company whose name is reminiscent of a popular Microsoft product. We get a non-trivial amount of tech support-type questions pertaining to it. At first you either help them or politely explain to them that they have the wrong company ... after a while it's just noise.
When someone randomly throws an email in a direction completely irrelevant to their issue, they are just grasping at straws. It would not be unreasonable to assume they've tried 20 other emails before or after this one, where most are likely to be more relevant to their issue.
If that person doesn't know the difference, any response you could send them would be of no help nor comfort, and the risks of continued questioning once you've opened that box is simply not worth it.
They wrote me back! Not with the music, but an apology saying they didn't have the music score to send out. As an adult, I get it.. and I also have to say as a kid I was elated to receive a response back from the company. I didn't really expect to hear back from them at all.
I'm conflicted about this but I realize the bigger company has limitations. And a small shop has even more limitations. I get both sides.
To them a reply and it doesn't matter what's in the reply as they're not reading it anyway, means they have somebody to vent to. And if Daniel doesn't solve it. T-mobile is a bad company. DO NOT ever understimate the stupidity of people. No reply is best reply in cases like this!
Aren't statements like these frowned upon in HN? It's unfair of you to use a use a fake statistic like that and call people 'stupid'.
I personally just like knowing somebody read my letter instead of going into a black hole. And I kind of expect these things to go into black holes, so it's actually kind of heart warming when I receive any kind of response.
And this response would at least tell me to try a different contact. (I know in this case who Daniel Stenberg is and know what curl is so I wouldn't make this specific mistake, but sometimes hunting for support contact information returns things that are vague.)
If the customer gets angry at the response, it's fine because it just means they don't understand, which means they are just getting angrier at the car company. The car company deserves that since they made it so hard to contact them.