The original site is down for me, so going based on the app I was thinking it was about the actual edible Honey product, not Honey the discount coupon thing.
It started as a clone of the camelcamelcamel Amazon price history site and got kicked out by Amazon for abusing the system. It pivoted to a coupon site and started sucking down user data with the plugin when PayPal paid $4Bil CASH. Honey cost me affiliate marketing commissions.
Over 15 years ago I worked with a telco that had similar affiliate issues. We decided to stop paying any affiliate commission at all and evaluate sales after some time to decide to continue the experiment or not. There was a little decrease in traffic to the site but no measurable decrease in sales of new plans. There were several check moments and data validation after that, but sales numbers remained as they were.
The conclusion was that affiliate marketing claimed a lot of sales in their reporting, but the brand was strong enough (this company was #2 by market share in the country and #1 on most brand metrics) to get those customers without affiliate links.
there's something seriously wrong with this archived link. It's not staying still for one moment. It's constantly twitching and the text scrolls to weird positions. It's unreadable because of this.
Is it the archive at fault or is the original webpage this way?
- The Honey browser extension inserted their own affiliate link at checkout, depriving others of affiliate revenue.
- Honey collected discount codes entered by users while shopping online, then shook down website owners to have the discount codes removed.
- Honey should have "stood down" if an affiliate link was detected, but their algorithm would decide to skip the stand down based on if the user could be the an affiliate representative testing for compliance.
It's comparing Honey's behavior to a well-known and comprehended scandal. Simile is a tried and tested way (hah!) to explain otherwise potentially hard to understand or dry content.
It's not about the severity of the impact, its the fact that they were breaking the rules and explicitly coding to actively avoid being caught by testers.
Original MegaLag video: https://www.youtube.com/watch?v=qCGT_CKGgFE
You'd think that if you were an engineer building and maintaing a system like this, you'd have an "are we the baddies?" moment, but guess not.
For context, Ben Edelman the author of the blog post was in the video at https://youtu.be/qCGT_CKGgFE?t=1980
Their personal site is also linked in the video description https://www.benedelman.org/honey-detecting-testers/
The original site is down for me, so going based on the app I was thinking it was about the actual edible Honey product, not Honey the discount coupon thing.
It started as a clone of the camelcamelcamel Amazon price history site and got kicked out by Amazon for abusing the system. It pivoted to a coupon site and started sucking down user data with the plugin when PayPal paid $4Bil CASH. Honey cost me affiliate marketing commissions.
Apparently this thing got approved for the chrome store, which confirms that "store" approvals are near worthless for malware filtering.
Over 15 years ago I worked with a telco that had similar affiliate issues. We decided to stop paying any affiliate commission at all and evaluate sales after some time to decide to continue the experiment or not. There was a little decrease in traffic to the site but no measurable decrease in sales of new plans. There were several check moments and data validation after that, but sales numbers remained as they were.
The conclusion was that affiliate marketing claimed a lot of sales in their reporting, but the brand was strong enough (this company was #2 by market share in the country and #1 on most brand metrics) to get those customers without affiliate links.
Archived link: https://web.archive.org/web/20251230214339/https://vptdigita...
there's something seriously wrong with this archived link. It's not staying still for one moment. It's constantly twitching and the text scrolls to weird positions. It's unreadable because of this.
Is it the archive at fault or is the original webpage this way?
It constantly reloads for me (Firefox.) Just hit X which replaces the reload button while the page is loading and it will stop.
Disable JavaScript, reason #99e99.
I thought this was going to be about honey adulteration, which is a major problem.
Same, and that article would have been way more interesting (cf. EVOO).
Obviously Internet affiliate marketing schemes are built on mutual exploitation of asymmetric data collection. This cannot possibly surprise anyone.
TLDR;
- The Honey browser extension inserted their own affiliate link at checkout, depriving others of affiliate revenue.
- Honey collected discount codes entered by users while shopping online, then shook down website owners to have the discount codes removed.
- Honey should have "stood down" if an affiliate link was detected, but their algorithm would decide to skip the stand down based on if the user could be the an affiliate representative testing for compliance.
Allegedly.
Wow, I am very surprised that cookie stuffing[0] is still a thing. This could have been written 20 years ago.
[0] https://en.wikipedia.org/wiki/Cookie_stuffing
No honor among thieves, eh?
Likening any of this to Volkswagen emissions compliance scandal does a huge disservice by treating "Affiliate Marketing" as far too important.
"Who gets a kickback on this toothbrush" is a much MUCH less important question than "do you pollute the air we are all breathing".
It's comparing Honey's behavior to a well-known and comprehended scandal. Simile is a tried and tested way (hah!) to explain otherwise potentially hard to understand or dry content.
It's not about the severity of the impact, its the fact that they were breaking the rules and explicitly coding to actively avoid being caught by testers.