Skip to Content

I’m sure you’re all aware of the recent #blogtheft issue – where some rogue has been lifting content lock stock and barrel from here and reproducing it – sans author name – on their website www.sap-abap4.com. Stop Thief – It’s #blogtheft! and Stolen Content have blogged about it here already.

In Craig’s Friday Morning Report yesterday, I suggested:

13:32 qmacro: get SAP hosting to send alternative “STOLEN!” images to rogue referrer – Google “image theft apache” for examples

and straight after the conference call finished, I thought I’d demo how that could be done. I implemented such a mechanism for images on an SDN blog post of mine, images that just happened to be hosted on my machine. I wrote about how that was done in a weblog post:

Dealing with “#blogtheft” from SAP’s Developer Network

This morning, @thorstenster alerted me to the fact that SAP have now implemented this for images hosted here on SDN:

image

Now that’s a great reaction! Kudos to the SAP Community Network hackers who look after the servers here. To implement something like that in such a short space of time and on the production servers … I take my hat off to you folks. Well done.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Mark Finnern
    … or something.
    I think it was Darren Hague that brought it up first in the SAP Mentor forum. I pushed to implement it and may be your implementation tipped the scale to pull the trigger.

    Thanks for the support, Mark.

    (0) 
    1. DJ Adams Post author
      Hey Mark

      Aha, SAP Mentor Forum, not a member of that 🙂

      Anyway, great work Darren, I know you and the others have been working hard behind the scenes on this, oauth and other stuff lately.

      Cheers
      dj

      (0) 

Leave a Reply