8 ms·
Sex toy company Lovense admits its Android app locally stored audio recordings
- olympus 9y agoOh wow. While recording audio is concerning, I am so glad to be living in the timeline where I can control my sex toy with my smartphone. The next thing they need is an Alexa skill (which someone might already have).
- typetehcodez 9y agoThat's a real humdinger!
- porfirium 9y agoIncendiary title, even if correct. There is no proof whatsoever the recordings were uploaded anywhere.
- untog 9y ago...where does the title say they were uploaded? It says they were recorded. The company admits they were recorded.
- BinaryIdiot 9y ago> admits recording users' remote sessions 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?)
- porfirium 9y agoHence the "incendiary but correct". Just the "admits recording" is incendiary enough. Or you think the title wasn't written with the purpose of being clicked upon?
- whamlastxmas 9y agoRecording something in a technical context generally implies that it's accessable to the person or group that caused the recording to happen. That is not the case here and the headline is somewhat misleading.
- Dylan16807 9y agoIt says they recorded it, which strongly implies they had the data and their servers did the recording.
- scythe 9y ago"Sex toy company admits recording..." implies that the company did the recording. A more accurate title might begin "Sex toy company admits product records..."
- return0 9y agothe title is crafted to imply that the sex toy company was recording its users, could only do that remotely. but hey, titles sell
- BinaryIdiot 9y agoNot sure why you were so heavily downvoted; the title explicitly says "recording user's remote sessions". To record something remotely heavily implies a connection between two places. If it was only recording on the device and nothing else there would be zero reason to say "remote" because it wouldn't be remote, it would be a local recording.
- DonHopkins 9y agoThey only call it a 'minor bug' because nobody's discovered the 'major bug' yet. Gotta leave yourself some wiggle room (so to speak).
- justboxing 9y agoNormally I'd call BS on a Company calling unauthorized collection of data a 'minor' bug, but in this particular case, it seems likely that this is the case. I say this because -- according to the company's official response[1] -- 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_remote_control_vibrator_app_recording/dpm4050/ https://www.reddit.com/r/sex/comments/7bmi3i/psa_lovense_rem...
- loceng 9y agoIn the technical sense it sounds like a minor bug in, in the other implications not so minor - perhaps another mistake on their part of not being more clear with language.
- cantrip 9y agoIt's possible this was only done on Android specifically because the odds of this being picked up and the app rejected by Apple are close to 100% while the odds of that happening in Google Play are about 0%.
- fleitz 9y agohaha. yeah, no. Apple catches UI issues and obvious use of private APIs. You just need the slimmest of excuses to do what you want. Like if you want to track a user's location put a location feature ANYWHERE in the app. 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.
- 659087 9y agoJust like it was "accidental" when Google's street view cars were capturing wifi data.
- johannes1234321 9y agoYes, likely. It'S plausible that Google captured Wifi signals in order to get to the SSID etc. to build a location database and they forgot to cut of the data part, possibly assuming it was encrypted anyways. Considering that they announced the mistake themselves and the short time the car was in receiving distance makes this a quit believable thing. 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.
- 659087 9y ago> and they forgot to cut of the data part, possibly assuming it was encrypted anyways 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.
- johannes1234321 9y agoLet's assume they did that on purpose: What's the purpose they get? Some random fragments of communication? They already have more relevant info via Google analytics and such about anybody, than what they gather while driving by ...
- matthewmacleod 9y agoYou’re being facetious, but it’s more like when the whole “Apple is tracking you through your iPhone” thing was going on - in that case, it was similarly a local database which was recording data which should have been erased, but it wasn’t transmitted to anyone. 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.
- squarefoot 9y agoI believe we should push Google, Apple etc. into taxing permissions usage, say 2% for every permission if you use it and 5% if you require it but don't use it, so that if common sense doesn't work at least greed will encourage programmers to require access only to what is really necessary.
- bdcravens 9y agoHow would you tax free apps?
- sidlls 9y agoDo not permit them. Free apps are just a way to reinforce the user-is-the-product problem that exists today. Note: I don't agree with a "permissions tax."
- fleitz 9y agoYou may also want to purchase your phone from a company that isn't the world's largest advertising company. 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.
- deleted 9y ago[deleted]
- dredmorbius 9y agoIn many professional contexts, a bond is required to be paid. 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.
- cabaalis 9y agoIt does make sense to pay a fee for usage of the hardware, if only to guarantee legitimate usage.
- mattbierner 9y agoOne nice thing about their hardware though is that it is very easy to write custom software to control it. Almost concerning easy actually. See the Metafetish project for one example of this: https://github.com/metafetish https://github.com/metafetish
- _jal 9y agoThis is my new favorite Github project, but I only read it for the app names.
- echan00 9y agoThe issue was probably blown more out of proportion by the writers who are encouraged to come up with click-bait headlines
- tryingagainbro 9y agoFeature or a bug the company deserves no mercy, you should triple check those things--after you quadruple check them. 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.