CHANGE ACESTREAM IN SODA PLAYER SOFTWARE
CHANGE ACESTREAM IN SODA PLAYER CODE

What exactly do you want from all this? A personal response from the company? Did you email them? What did they say? There is nothing we can do here, and most people with brains aren't going to boycott a company for something unverifiable as this. Yet hundreds of people are ready to burn this place to the ground over a bug that no one can get to happen. Can YOU explain what its doing? It's happening on YOUR machine? This is my problem, I can't get it to reproduce, nor can the hundreds of others who posted here.

CHANGE ACESTREAM IN SODA PLAYER SOFTWARE

It's also interesting to me that it A) only happens on MAC, and B) it only seems to happen once and only with you and the OP.Д¬an anyone explain why its doing it? Or more likely is it a very random, what software developers would deem unable to reproduce bug. I don't know what you expect them, or us to do? Ive run this program for a year now, and since this thread, been running it every single day while watching and it doesn't access shit. Both times only verifiable once by the two people (you included) who found it. And no, I don't work with, have any vested interest in, or represent anyone at that company, just someone who has been in software development for a couple of decades and trying to give some insight =)Дon't know what to tell you, it's happened on two peoples machines, both Mac's. Sometimes letting internet drama die out on its own is better then adding fuel to the fire by trying to plead a case against a bug that has no reproducible steps. So in all honestly this might not even have ticked on their radar of give a shits because there is nothing to give a shit about? I know it would be 'better' for them to respond, I agree, but I am still using the app today, as every other user on our home network does (2 kids, wife, and I all stream using it) and haven't had an issue and I am guessing hundreds of thousands of others are too. In the month this has been up, not one person has come in with proof its happening, and the OP even admits he can't get it to happen again.Could it be? Sure! I am not saying it was 'clean', but there isn't any real evidence the program was doing much of anything other then verifying cache data. There is NOTHING About what OP Posted that is malicious or 'weird' unless you don't have any real understanding of how programs interact with memory and files. Yes, it even could be malicious, but then why isn't EVERYONE having this issue? Why only 2 people? It could have been anything, honestly, it could have just been a process gone fucking awry.

CHANGE ACESTREAM IN SODA PLAYER CODE

It might be scanning for an alternate config file that one of the devs was using on the fly and forgot to remove the code for, it could have been a test for streaming protected content paid for through their app that went haywire. Scanning files doesn't mean its reading them, it doesn't mean its opening them, it just means that its scanning memory footprints.

ONE person has UNVERIFIABLE screenshot that Soda was accessing files, and even then, its not really 'Doing' anything malicious.

I don't know what to say really, just reading all this. But it seems that they are not intending to answer so far. None the less, i would really like for the team behind sodaplayer to take this incident seriously, i know others have pinged them, and i have also tried to send them a link to this post also, via their website. It can be remotely disabled, or perhaps, it can be remotely triggered Ontop of this, i tried to reproduce today without luck, while streaming another acestream link for quiet a while, so either maybe one of the following is true:

I cannot find a reason why it should have a feature doing this kind of file access at all. In this context i opened up the details which displayed open file descriptors to these private word documents, ontop of the presumed access to my keybase files. This lead me to investigate the processes in the activity monitor - where Soda stream had a subprocess, the one showed in OP, with a large number of bytes read from disk. It was discovered as i, after a while of streaming, got a keybase client warning, that a program had accessed the private shared folder shared between me and a number of my connections on the platform. The incident was discovered while my setup was streaming while streaming F1 via acestream.

Change acestream in soda player