4 ms·

> So why ask for the country of the seller in the API? I must admit I'm not 100% sure either. I'm just exposing the API of the underlying open source project w

> So why ask for the country of the seller in the API? I must admit I'm not 100% sure either. I'm just exposing the API of the underlying open source project which says to supply the seller's country [1]. [1]: https://github.com/mpociot/vat-calculator https://github.com/mpociot/vat-calculator At the bottom, where it says "Important"

jacquesm 10y ago
If you're 'not sure' you should take this offline until you are sure. Bookkeeping is an extremely bad area to go 'move fast and break stuff' because what you're breaking is other people's administrations and you won't have a way to fix it or even to reach them to inform them of an issue.
- mherrmann 10y ago
  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.

jacquesm 10y ago

If you're 'not sure' you should take this offline until you are sure. Bookkeeping is an extremely bad area to go 'move fast and break stuff' because what you're breaking is other people's administrations and you won't have a way to fix it or even to reach them to inform them of an issue.

mherrmann 10y ago
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.