3 ms·
The obvious solution would be to ask the user for permission before opening the socket.
by Franciscouzo 9y ago
The obvious solution would be to ask the user for permission before opening the socket.
- deleted 9y ago[deleted]
- Paul-ish 9y agoThis is always the proposed answer whenever someone wants to introduce X potentially insecure API. It is lazy IMO. It requires the potentially uninformed user to make a critical decision. Plus, if we introduced every insecure-but-we-prompt API proposed, the user would be inundated with prompts and it would reduce their productivity.
- MertsA 9y agoForget impacting their productivity, we've already seen what happens when you defer these questions to the user. They always hit yes or okay. It's like it's not even there, people would view mindlessly accepting prompts like that's just how you're meant to use a computer.
- ascorbic 9y agoMore important than reducing productivity is the problem that prompt-overload conditions people to just blindly click accept.