3 ms·

You're being extremely critical in this entire thread. Tell me: How is having this field, unnecessary or not, a risk? You want me to take the site offline. But

You're being extremely critical in this entire thread. Tell me: How is having this field, unnecessary or not, a risk? You want me to take the site offline. But it's providing value to my own business, and apparently other people find it interesting as well. It's merely a REST API for an existing open source project. And whether people use the library or the REST API is the same from a risk perspective from their point of view. I'm providing value here, and am happy to run the risk you're advising against. So I will not take it offline.

jacquesm 10y ago
> You're being extremely critical in this entire thread. Yes. > Tell me: How is having this field, unnecessary or not, a risk? - an unnecessary field implies that that field is either being collected or being used in the calculations, if it isn't then it simply should not be there. > But it's providing value to my own business, and apparently other people find it interesting as well. I'm sure it is, but it is also a risk and it seems as though you have not done the homework required to field a service such as this. That's a dangerous hobby. > It's merely a REST API for an existing open source project. No, it is a piece of software that you field that has the risk of affecting businesses that use it in a critical and potentially negative way if you mess up and it does not appear that you treat this subject with the seriousness normally associated with such a project. > And whether people use the library or the REST API is the same from a risk perspective from their point of view. That is so far from the truth that I again wonder if you know what you are doing. > I'm providing value here, and am happy to run the risk you're advising against. > So I will not take it offline. Suit yourself.

3 ms·

You're being extremely critical in this entire thread. Tell me: How is having this field, unnecessary or not, a risk? You want me to take the site offline. But

by mherrmann 10y ago

jacquesm 10y ago
> You're being extremely critical in this entire thread. Yes. > Tell me: How is having this field, unnecessary or not, a risk? - an unnecessary field implies that that field is either being collected or being used in the calculations, if it isn't then it simply should not be there. > But it's providing value to my own business, and apparently other people find it interesting as well. I'm sure it is, but it is also a risk and it seems as though you have not done the homework required to field a service such as this. That's a dangerous hobby. > It's merely a REST API for an existing open source project. No, it is a piece of software that you field that has the risk of affecting businesses that use it in a critical and potentially negative way if you mess up and it does not appear that you treat this subject with the seriousness normally associated with such a project. > And whether people use the library or the REST API is the same from a risk perspective from their point of view. That is so far from the truth that I again wonder if you know what you are doing. > I'm providing value here, and am happy to run the risk you're advising against. > So I will not take it offline. Suit yourself.