The story is that the author hadn't considered this, and there's a lot of different ways we could dig into that:
- the general quality of education we're giving journalists about privacy and security.
- 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.
- 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 we should have a set of general, open standards for how journalists conduct interviews that will help avoid problems like this.
- 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.
And so on. I couldn't agree more, I don't think it's a non-story, I think it's a very important story. 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.
----
> And if it is, good on the author for making it transparent
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.