3 ms·
Actually, I prefer this be resolved in the public arena, rather than on a case-by-case basis for everyone who encounters this problem. If the OP is accurate, th
by danso 14y ago
Actually, I prefer this be resolved in the public arena, rather than on a case-by-case basis for everyone who encounters this problem. If the OP is accurate, then this is a problematic implementation detail that every corporate user should be aware of.
- natural219 14y agoI give some leeway for problems that seem to be bugs rather than intentional features. I doubt Dropbox intended for your account to be deleted in this scenario.
- erikpukinskis 14y agoYou should probably read the article before speculating. It's not even that long. He says: "In case you’re wondering, this is not a bug: it appears to be documented (sort of)."
- Wintamute 14y agoThe wording of their FAQ suggests they are aware of this. From the OP: “If someday you leave the team, it may not be possible to convert your Teams account back to an individual account that you can access.”
- devgutt 14y agoDon't you think that the great majority of the problems should be solved publicly? Unless the problem has sensitive data I think there's no reason to use a one-to-one support channel.
- danso 14y agoIn the OP's case, where the unexpected feature was already officially alluded to, sure. But I think there are probably some unintentional security holes in which it's probably prudent to use a private channel first, and then after it's been fixed or a reasonable amount of time, disclose the problem. The problem, IMO, is worth disclosing publicly even after it's been fixed because it may be indicative of problematic internal practices that may require public scrutiny (or humiliation) to actually fix.