Thanks for your contribution to this Ben - I was quite stunned by Megalag's finding, and I agree with you that it could definitely be characterized as wire fraud.
I think the very interesting wrinkle here is that, for the most part, their victims are corporations - meaning, sadly, that it's much more likely they will be prosecuted, either in civil or criminal court.
Was the VPT site not working for you, so you had to resort to archive.org? Original link https://vptdigital.com/blog/honey-detecting-testers/ . Anyone having trouble -- contact Ben Edelman (easily found by web search) and I will genuinely value the opportunity to get to the bottom of what is wrong.
Your diagnosis is correct. VPT has been most focused on building our testing automation, then improving reports and dashboards. We knew this spike of traffic was coming, but we didn't finish sufficient WordPress optimizations. Apologies.
I just love it - what's the chance that some internet stranger cites some site (pub intended) of another strange on some random forum, and that site/blog's owner immediately chimes in (as a member of that forum, no less) to take up the discussion, and to answer questions and share some (insider/off-the-beaten-track) insights. It is wonderful to see such positive interactions and knowledge sharing of humanity.
In your interview with MegaLag posted in the video, you say something along the lines that civil courts are probably the most likely place any lawsuits would be held (I forget the exact wording used).
If you had used Honey, would you join a civil or class action suit against them?
I believe in class actions as the most efficient way for large groups (of consumers or small businesses) to resolve disputes. Have to think about the specific claim. Yesterday's write-up covers a scheme harming other affiliates (creators, influencers, reviewers, etc.) and also harming merchants and networks. I don't know if users are direct victims of the stand-down violations and concealment.
Bloomberg reports both that Applovin says they did get user consent ("Users never get downloads with any of our products without explicitly requesting it") and that they're nonetheless shutting down the app install business because it was, supposedly, "not economically viable."
ADB can show you what package install'd a package. I've been running a setup but I gernally buy a bunch of the same phone, but after they get wifi they install masive amounts of junk.
Yup, can see what package installed a package both via ADB and even in the Settings > Apps GUI. Of course that's a slightly different question from whether the install was nonconsensual.
Are you sure BlueStacks installs apps without user consent? I know BlueStacks as an emulator to play Android games on PC and Mac. That's a legitimate business, 100% consistent with what users want. Versus what I (author of the piece linked above) reported is that AppLovin is installing apps that users don't want -- installing silently, installing when users tap X, installing after a quick (5 second) countdown.
I think the structure of this article definitely made it harder to find the details to some of these questions—the fact that it's posted as 5-8 different "blog" entries instead of a single webpage made it harder then it needed to be to get to the technical conclusions section. Also, some of the method call listings on this page: https://www.benedelman.org/applovin-execution-path/ were unnecessarily verbose, and duplicative with the later pages that actually explained the flow in more detail e.g. https://www.benedelman.org/applovin-execution-sdk/
Having all of the sections of the article on the same page would have helped surface and resolve a lot of these potential editorial issues.
Thanks for these suggestions. You may be right. I split the article into pages based on feedback from early readers that it was too long. Custom nav bar in the top-right, but maybe still not quite right. I've never previously posted anything of this length or complexity.
Thanks also for reading so carefully. My web stats say many people stopped at the summary!
I'm the author of the article linked at the start of the thread. Replying to try to focus the discussion on the specific change I was writing about.
Piker, can you say more about how "the change" make the documents "accessible" (or more accessible)? They were already at Internet Archive just fine. Several sites already copied the documents from IA and added their own presentation, cross-linking, notifications, and other services on top. I don't see the proposed changes as helping with this. Indeed, by sending the latest data only to CourtListener but not to IA, the proposed changes stand in the way of the other sites and services you envision -- as it seems they'll now have to license the data from FLP/CL (on a paid basis), rather than get it free directly from IA. These are the general concerns I was trying to present in my article.
>> FLP also proposed to upload litigation materials to IA in only machine-readable formats compressed into enormous multi-gigabyte tarballs, ending the human-readable individual HTML files that have for years made it easy for normal users with standard web browsers to see court records.
Perhaps the "only" is telling here. Were they previously also uploading the tarballs? No wholesale user would want to scrape the thousands of extra pages of HTML to download the content. So if they weren't already uploading the tarballs, this is actually a beneficial change.
Previously FLP was uploading files that users can read with a web browser -- HTML, PDF, and also XML with metadata. I could and did link directly to HTML and PDFs, including circulating these materials with coauthors and research assistants and members of the press.
If FLP begins uploading only huge tarballs, and not the individual constituent files, I won't be able to do any of that.
You should consider filing a formal comment with DOT about your experience, and especially your surprise at the unexpected charges. This is straightforward using the Comment Now button on http://www.regulations.gov/#!documentDetail;D=DOT-OST-2013-0... . DOT is currently evaluating my complaint against BA on this subject.
Indeed. DOT fines tend to be small in this area. On the other hand, it is notable that DOT considered and rejected each of AA's defenses. That could be useful as precedent.
Some passengers may also have meritorious claims they'd like to bring against AA on an individual basis.
Of course I agree that health is more important than affiliate commissions. So the comparison only goes so far.