I say this because -- according to the company's official response -- the recordings were only created on the Android version and not the iOS version of their app.
They also state that the recording is only cached locally on the phone and not uploaded to their servers.
Leads me to think that it's very likely their Android app programmer(s) wrote some test code to save the file, and forgot to delete it or conditionally hide it in their release version of the App. There's no excuse for the sloppy programmer(s) if this was the case, I'm just saying the 'bug' angle is a possibility, because the Company has also been very quick to fix it and release an updated version for the Andriod app.
One more thing, I wouldn't call something like this a 'minor' bug. Likely their PR team threw that word in.
> Source: Lovense's official account on Reddit: https://www.reddit.com/r/sex/comments/7bmi3i/psa_lovense_rem...
I think it totally applies here.
Not removing temporary files is a very common bug. As a developer, I've encountered it several times, sometimes I caused it, sometimes I fixed it, and I've seen it happen in other people software just as often. This is one of the reason I hate temporary files, they just don't wan't to be temporary.
Make it look like an accident.
Ultimately I don't think we can judge intent in situations like these, especially because it's so easy to disguise. A sentence can be constructed in favor of any opinion; so I'll spare you my attempt at an alternate reading of the situation that makes them sound guilty so long as you agree that it's possible to do.
I think a few questions can be raised about whether we can trust a company's claim that a problem stops exactly at the limits of what's been made publicly visible. How do we really know that select installations weren't phoning home with their captures?
This is a great moment to plug the idea that we really should be able to see the source code of the software we're running.
They did post a bug fix though.
Why? How do you "accidentally" record someone?
The reason they store the file probably has to do with technical constraints. Maybe the audio API they are using only works with files and not memory buffers, maybe the buffer took too much space, maybe it is a workaround of some kind. We won't know without analyzing their code.
Also if the app is using the mic outside of the app, you'd see a big red bar at the top of your screen.
They also let you do things like record what other apps, etc are doing. Think of the Linux top command, on iOS there's no real reason for an app to need to list the other processes, so you can't. However, if you want to know what apps are running on the phone this would be a very useful API to have access to.
Private APIs are not meant for use by third-party developers. They are not publicly documented and are subject to change without warning.
Apple markets privacy as one of the features for the iPhone.
Yes I do. https://github.com/theShiva/
'no excuse' because of the context and sensitivity. It's a different issue if the programmer was leaving around some code execution log files or non-sensitive data on the disk...
A file containing recordings (audio & video?) of a sexual experience doesn't constitute 'temp file clean up bug' in my world. That said, we may be working in different worlds.
BUT, personally I assume that anything I do with a smartphone gets uploaded to the cloud via a permission I mistakenly gave, bug, or they can get hacked. In other words, certain kind of pictures, movies or acts don't (IMO) mix with a smartphone.
To me, this sounds like the recording of remote sessions which would involve some sort of connection (otherwise how would it be remote if it's only on the device itself?)
Similar here: The developers logged information onto the device itself in one version of the software and didn't hesitate to push a new release.
From an engineering perspective relatively small bugs. Impact a bit larger.
At the point in time when Google pulled that stunt, unprotected networks were still incredibly common. A company like Google playing dumb on that, or actually not knowing that, would be pretty sad.
I can completely see how this sort of thing could happen accidentally - not that it’s a great excuse for sloppy work, but mistakes do happen.
I use that a lot to turn off contacts access to apps that have no business reading my contacts.
In the Free Software world, packaging of applications generally involves a third-party who does that packaging, and has specific guidelines to adhere to. E.g., Debian Package Maintainers and the Debian Policy Manual.
Note: I don't agree with a "permissions tax."
It's kinda funny that everyone is upset about a temp file when the device itself sends their entire porn history to Google everyday of the week.
Basically, if you don't want to be spied on, stop using Google products.