• 0 Posts
  • 48 Comments
Joined 11 months ago
cake
Cake day: July 25th, 2023

help-circle













  • As much as people like to delve into conspiratorial gossiping, making swooping statements about how Google and Amazon work together, there’s often much simpler and more reasonable explanations.

    For one, you are one of billions of people browsing both these sites today, it’s bound to happen to some of you.

    But what prompted you to look up the horses stuff? Sometimes it’s an article, a social media post (reddit and Lemmy count), a radio segment, etc. That often leads a group of people to look up the same stuff en-masse.

    Its also possible that you’ve visited other sites about horses that have put you in that cohort, where manufacturers have placed their own tracking pixels whose info they can supply to Amazon for targeting.

    The reason why a Google / Amazon collaboration seems so unlikely is that they are competing. Not just at large, but in this specific case. Those recommendations you see on Amazon are ads too. People pay for them, and use specific targeting rules to find people to click on them. This is what both Amazon and Google sell, access to specific eyeballs (eg. males in their late 30’s who have once shown interest in motorsports). This is their secret sauce. They’d be crazy to allow that information to flow to a competitor with their own ad platform.

    I know this goes against the grain here, so feel free to downvote, but keep in mind that conjecture and wildly inaccurate gossip about what these giant companies do often muddies the waters and makes it much harder to attack them on the shady and downright evil stuff that they do do.


  • Either you misunderstand or the person you are responding to is. If you retroactively add a license to the current state of the code (for example by committing a new LICENSE file and adding the new license to the top of each file), or course that applies to the entire state of that code as of that commit. What is more difficult is that earlier commits won’t have that license explicitly unless you rewrite git history to make that happen (which is possible but tedious).

    You can always relicense code you own the rights to. You can even dual license it, or continue to use it commercially in terms contradicting the license you open sourced it as, as long as you have the permission of every contributor.

    The idea that a license added would only apply to code added after the license change is very funny.