"Another idea was to have a prompt asking if you wish to upload the log or not, after every crash. Apart from the extra implementation time, players will still often click "Don't send", either because that's what they have been doing for many years or because they just want to quickly get back in the game or because they feel that the crash was somehow their fault."
https://factorio.com/blog/post/fff-231
Here, the developer is trying to infer user reasoning and intent
Curiously, he omits the possibility that users would prefer not to send the data
When in fact this is exactly what users indicate they prefer
He pretends that "Don't send" is ambiguous, for example, that despite clicking "Don't send" users actually don't care if data is sent
But there is nothing here that indicates users wanted to send data or that they do not care
Software developers can obviously do whatever they want and they can act against the interests of users
This includes ignoring or explaining away the preferences of their users ("Don't send") and engaging in speculation about user reasoning and intent
The developer here seems dismissive of users' reasons for clicking "Don't send", even though he does not know the reasons and can only speculate. At the same time he expects readers to take his reasons for collecting crash logs as justified. Then he unilaterally decides to remove user choice (the "Don't send" button) and substitute his own choice (send data) as a default
Perhaps lack of developer pre-release testing and quality control is relevant to this discussion. Alas, the problem is framed as one of data collection and user consent where the "solution" is making data collection surreptitious and making "consent" uninformed, implied