2 ms·
I'm not that type of "developer". I don't do that to my users, and I wouldn't want that as a user either. Remember, this behaviour (even if it is explicitly me
by userbinator 8y ago
I'm not that type of "developer". I don't do that to my users, and I wouldn't want that as a user either.
Remember, this behaviour (even if it is explicitly mentioned in the EULA) used to be called spyware and tools were created to detect and remove such things. Then the big companies caught on and spun it in the "but it's for the users!" direction, and now it's harmless? I see the "if you're using this and Azure you should trust Microsoft already" point, but this is presumably software that isn't for just interacting with Azure.
Given the sort of data that usually resides in databases, an application for interacting with them that will occasionally make connections out into the Internet just triggers suspicion regardless.