It's not that people don't care or have given up on privacy - it's that a lot of times developers lie to the user about what's happening, or at the least obfuscate it. The cynic in me says that the lack of transparency about this is intentional look at the outcry that happens when people learn about fb/meta snooping through their device, or the various apps turning on cameras and microphones when the user doesn't expect it. We have been trained to manipulate apps, not hardware that's the only 'surface' visible to the user. Part of this is technical education, but I think a lot of it also comes down to the fact that these devices are hermetically sealed from the average user, and even the average technical user. There's an assumption that unless you explicitly send something out, or actively make a post - something that involves clicking 'send' or 'share' - that the device is a receiver only when.that's just not the case. I think the sheer amount of data being transferred off of our various devices completely shocks the average, non-technical user. That's also a good point part of the way you change journalist attitudes towards data security is you get journalists to research it and then talk to each other and very transparently say, "hey, these things we thought were safe aren't, and we are making mistakes with data right now." It's a lot more powerful and effective for a journalist to say that about themselves and about their field than for us to criticize them for bringing the issue up - even if it feels at points in the article like the author hasn't really grasped all of the problems with what they're doing yet. > And if it is, good on the author for making it transparent Otter.ai is a small part of it though, and the story is more about the context/environment that causes a story like this to be written and that causes this to be news. I couldn't agree more, I don't think it's a non-story, I think it's a very important story. if you're being interviewed by a journalist about something sensitive, should you inquire into what their setup is, and should you explicitly make requests like asking them to promise not to use a 3rd-party for processing the interview.Īnd so on. whether we should have a set of general, open standards for how journalists conduct interviews that will help avoid problems like this. whether we in the tech industry are being irresponsible by just constantly assuring the public that AI-driven services don't involve interaction with human employees/contractors. whether or not Otter.ai (and other tech services in general) have a responsibility to turn away journalists that they think might be putting other people in danger by using the services. the general quality of education we're giving journalists about privacy and security. The story is that the author hadn't considered this, and there's a lot of different ways we could dig into that: Do your users understand what of their data you have and how you use it? I feel like they learned a lot researching the article and basically put their own inadequacies on display for public scrutiny, which many others may not do.Ĭonsider this next time you update your company's Privacy Policy and wonder if it's understandable, to who, can be discovered at all, etc. And if it is, good on the author for making it transparent. If this is representative of the trade, I think as tech we have a lot of education left to do for everyone's safety. It seems like they never before considered the implications of using the service and sending interview contents off-device at all. The title was the name of their informant, and I think they were shocked Otter played an informant's name back at them. I think the article is extremely interesting: As I kept reading, it eventually dawned on me that what had disturbed the author and gotten their attention at all was really just that a customer survey used the same title they had used when saving the interview recording file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |