Hacker News new | past | comments | ask | show | jobs | submit login

I think I've made it pretty clear "personal convenience" is not the issue at stake here. I guess you're just arguing in bad faith at this point.



As you said previously...

>Do you normally assume the worst about people when you debate them?

I don't know what I said here that seemed to offended you. If you point out something that truly crossed a line, I can apologize. You weren't the one who my original comment was directed towards and in your very first comment you admitted yourself that this type of behavior was potentially unethical. I don't think I have said anything worse than that and I don't know what I did that you consider bad faith. The one example you gave of a negative result was a recruiter calling your mother. Stopping that falls under the category of "personal convenience". We all get unwanted calls from time to time. It is annoying, but it takes a couple minutes out of your day and you move on. No reason to take that as justification for flooding public sites with "multi GB files full of random data" which is where the conversation started.


Yeah, that's not "personal convenience". I would say this borders on safety. I don't think it's that difficult to imagine how this same dataset in the hands of a bad actor is to be abused.

In your case, my assumptions of you are based on how you continually downplay concerns to "not happening" or "that's no big deal". You also readily accused me of avoiding repercussions, then walking back and walking forward those claims in some kafka-esque dance.

"Arguing in bad faith" also doesn't mean you've offended me. It's just a realization that you have some other motivation at stake here. People don't just recategorize a safety and privacy issue as "personal convenience" while dancing around calling it a problem.


I guess we are just going to have to agree to disagree.

I don't consider spam phone calls as a safety threat and you do. I am not excusing the abuse of this data. I simply think these are some of the risks someone accepts by participating in this activity.

I don't know what I said that you consider denying your concerns as "not happening". Saying you should just accept those results or stop participating is not saying those results aren't happening.

I don't know why you are so tied to "repercussions" as been some type of problematic word. All it means is unintended and unwanted results. It wasn't a judgement of you. It was a literal descriptor.

My only motivation is that I am developer, I do data analysis, and I use public services. I empathize with the people who have to clean up after users abuse these services and I don't like when public services need to be downgraded because of such abuse.


I will take back that you're here in bad faith, I apologize. You just lack equivalent empathy for people who have had these APIs used on them, had their data sold, etc... as the empathy you have for developers cleaning up data from people trying to avoid having these APIs weaponized against them. Empathy is selective, and my empathy for the devs is much lower because that's what they get paid to do. I think that's a fair stance to have.

If data being 100% available is a natural consequence you're okay with, and I have to accept that then you will have to accept that people who don't agree with this growing practice but don't want to be excluded from society will introduce entropy to make those systems less efficient as a natural consequence. The efficiency and ease of access of which is what makes them weapons.

I take issue with "repercussions" because it comes off as a dog whistle for "people who believe in privacy have something to hide". I understand that's not 100% of what you meant, but it's awful close. Generally, I don't think it's okay for data to live on forever other than in highly significant events, even then it should likely be anonymized.

I do agree that we'll have to agree to disagree that not participating in the new public discourse is a viable approach.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: