I tried the vimeo IP blocklist test in case Amazon have also blacklisted a bunch of Digital Ocean IP addresses, but strangely I can wget the link just fine from the server directly:
Our members have been finding this a lot lately, especially as we are affiliated with Amazon UK and Amazon France.
Being able to onebox and show suggested products relevant to the discussion obviously helps us as our forum funds increase when an item is purchased using the affiliation link.
But the onebox now not showing is crazy and not helping anyone. I have since found this thread from @merefield
I was ejected from their programme for that ‘transgression’.
I use the official image links they provide and generate in their toolbar instead. You can set them within table markdown to make them look a bit better. It’s a little more work, of course, but it really depends on how often you need to do it.
Legally it’s against their terms, but I do agree with Jeff, the time I was “punished” was probably down to a finickity reviewer having a bad day. (and probably not familiar with Discourse).
Btw, Amazon UK has rejected me twice for ‘being a forum’ (not mentioned anywhere in their rules!). The US has no issue. It’s incredibly frustrating how they seem to observe different rules depending on the locale.
As with Amazon’s Seller support it all depends on who receives your query or in this case application as to what response you get!
The Amazon’s Associates Program Operating Agreement has recently been updated 6 Sept 2019 (uk) and 1st October on .com.
As always they have the “we reserve the right to modify change any part of the agreement terms and conditions” ( section 13) and if you don’t like it…tough, leave (section 6) …they are such a joy to work with!
We are not Amazon affiliates, nor are any of our members who post links to Amazon products on our Discourse.
Our members sometimes post links to products on Amazon which may be of interest to our community but it won’t be that many, I would say it’s as low an average as one Amazon link per day. So we’re not really abusing the system.
I’m still not quite sure why I can wget the URL directly from the server without an issue though
Is there anything else I could try or test? Any caches I could flush or processes I could restart which may ‘refresh’ something?
Thanks for the suggestion, a quick glance suggests that I need to subscribe to a paid-for service in order for that to work. Any other workarounds I could use?
Curious as to how Amazon know that Discourse is making the request and blocking it on the fly, as the wget route on the same server still works fine.
