Show Instagram photos on eyeo.com

[jsitarz]

Background

Showing to our visitors/candidates people behind the products we make

What to change

Would it be possible to link our Instagram photos on our website where we have pictures displayed?

[juliandoucette]

Cool Idea :)

Have you sent this to product already?
-- We need to know what this looks like and how it works

If accepted by product, we'll also have to investigate:

• How to manage which photos do/don't get shown
• Whether or not this has privacy implications

[jsitarz]

thanks! yes, I added in cc jeen and paul. it would look like on this page ( scroll down) ​http://careers.backbase.com/ - will check with legal if there are any issues

[jsitarz]

checked with Judith, she mentioned that she doesn't have any issues with that as long as pictures are coming from us so only from adblockplus / eyeo instagram

[jsitarz]

hey all, in case we go forward with this one we would use this instagram account : ​https://www.instagram.com/_eyeo/?hl=en

[juliandoucette]

it would look like on this page ( scroll down) ​​http://careers.backbase.com/

The images on this page are not coming from Instagram?

---

We can choose different images and change the website layout of eyeo.com anytime. We can even link the images on eyeo.com to images on Instagram. Is that not enough?

If we dynamically pull the latest images from Instagram using the browser then:

• Users and Robots that do not run JavaScript will not see them
  • I don't know if Google runs JavaScript before indexing pages
    • This is worth testing
• Instagram (Facebook) will be able to track our users on our website
  • We don't currently mention anything about this in our privacy policy jnink

[jnink]

Replying to juliandoucette:

it would look like on this page ( scroll down) ​​http://careers.backbase.com/

The images on this page are not coming from Instagram?

---

We can choose different images and change the website layout of eyeo.com anytime. We can even link the images on eyeo.com to images on Instagram. Is that not enough?

If we dynamically pull the latest images from Instagram using the browser then:

• Users and Robots that do not run JavaScript will not see them
  • I don't know if Google runs JavaScript before indexing pages
    • This is worth testing
• Instagram (Facebook) will be able to track our users on our website
  • We don't currently mention anything about this in our privacy policy jnink

I know, this is something which I need to change in case technically it makes sense to include them dynamically instead of linking. Let me know what is the final solution and then I will take care of the privacy policy.
The only thing I don't know is what kind of data would be involved in the trakcing of Instagram. Do you have any idea? Is it similar to the "like" button? meaning IP address invvolved? If so, that would be an issue privacywise and wouldn't be permitted.

[greiner]

Replying to juliandoucette:

If we dynamically pull the latest images from Instagram using the browser then:

Why would this even be an option? We should be able to implement such a fetching mechanism on the server-side because by doing that there'd be no privacy issue, no client-side security issues, no performance hit on page load and no potential leakage of API keys.

One point I'd like to highlight is that I haven't heard anyone's expectations of how quickly updates that were made to our Instagram page should be reflected on eyeo.com. Based on the frequency of our posts on Instagram, updating the pictures once a day seems to be more than sufficient. Note that we also do regular page updates that for reordering people on eyeo.com/team.

[juliandoucette]

Replying to greiner:

Why would this even be an option? We should be able to implement such a fetching mechanism on the server-side because by doing that there'd be no privacy issue, no client-side security issues, no performance hit on page load and no potential leakage of API keys.

Good question. I think that I made incorrect assumptions here. And I agree that pulling data from instagram from our backend would be a better idea if we pull data from instagram at all.

[juliandoucette]

The only thing I don't know is what kind of data would be involved in the trakcing of Instagram. Do you have any idea? Is it similar to the "like" button? meaning IP address invvolved? If so, that would be an issue privacywise and wouldn't be permitted.

This depends on how we implement it.

• If we used Instagram's embed then it would be like a like button or a YouTube video
• If we used Instagram's API from the frontend then it would send the user's IP address and our API key (at least)
• If we used Instagram's API from the backend then it would send our server's IP address and our API key (at least)

[jnink]

Replying to juliandoucette:

The only thing I don't know is what kind of data would be involved in the trakcing of Instagram. Do you have any idea? Is it similar to the "like" button? meaning IP address invvolved? If so, that would be an issue privacywise and wouldn't be permitted.

This depends on how we implement it.

• If we used Instagram's embed then it would be like a like button or a YouTube video
• If we used Instagram's API from the frontend then it would send the user's IP address and our API key (at least)
• If we used Instagram's API from the backend then it would send our server's IP address and our API key (at least)

Great, then my answer is clear: let's go with greiner's proposal, as everything else would be a privacy issue. When we do that, we don't need to amend the privacy policy at all (as it does not affect personal data).

[juliandoucette]

We are going to need more details about the background and requirements of this change to move it forward.

[jeen]

• The Instagram feed should display in a grid format on the ​https://eyeo.com/en/jobs/page
• Title: Life at #eyeo
• Description: Meet the talented team behind Adblock Plus, Adblock Browser and Flattr. We are tight knit family based out of Cologne, Berlin and the world. Take a look at all the fun we have together!
• This will go at the bottom of the page, above the footer, and fill the width of the page.
• The grid should be 6 images wide and upon hovering over the image, the eyeo comment/caption should display against a black semi opaque layover, left aligned from the bottom of the image.
• The images should be refreshed daily.
• Once we implement this we can remove the images from the Why work with us tab.

[juliandoucette]

• Confirmed
• Created blocking Sitescripts ticket #5407

@jlow I think this is P3 (A core developer will implement this eventually after it is unblocked and marked Ready). Please let us know if you think that this needs to be done more urgently.

[jeen]

@juliandoucette can we bump this up, please?

[juliandoucette]

Replying to jeen:

@juliandoucette can we bump this up, please?

https://issues.adblockplus.org/ticket/5407#comment:1

[ire]

Since #5407 is taking a while, I came up with what I think could be a good intermediary solution.

Instagram has a way to get a JSON format of a user's instagram page. So, we can get the information from our eyeo instagram page by doing a simple GET request on the following URL:

https://www.instagram.com/_eyeo/?__a=1

I wrote a simple global we can use the get the images with python:

import urllib2
import json

def get_instagram_user_media(user='_eyeo'):
  try:
    request = urllib2.Request('https://www.instagram.com/' + user + '/?__a=1&hl=en')
    opener = urllib2.build_opener()
    open_request = opener.open(request)
    response = json.loads(open_request.read())
    media = response['user']['media']['nodes']
    return media if media else []
  except:
    return []

And we can get the images in our template like so:

{% set media = get_instagram_user_media() %}

{% for item in media %}
<img src="{{ item.display_src }}">
{% endfor %}

Instagram doesn't publicize this method, in fact they will probably disable it at some point. But I think we can still use this in the interim, assuming #5407 is being worked on.

[juliandoucette]

Since #5407 is taking a while, I came up with what I think could be a good intermediary solution.

Well done!

And/But if we put instagram image srcs into our pages then instagram will be able to track all of our page visits and we will have to update our privacy policy.

[greiner]

Note that Instagram is ​abandoning its current API in favor of Facebook's ​Instagram Graph API which, at this point, is only available for business accounts.

So maybe we could already start using that one instead of implementing this workaround because it sounds like it could break at any point without us noticing.

@Julian AFAIK an update to our privacy policy would be insufficient for complying with GDPR. We'd have to serve the images from our servers or get explicit consent from the visitor before making the request.

[ire]

Ah alright, I think I misunderstood the privacy issue then.

Note that Instagram is ​abandoning its current API in favor of Facebook's ​Instagram Graph API which, at this point, is only available for business accounts.

So maybe we could already start using that one instead of implementing this workaround because it sounds like it could break at any point without us noticing.

Yup that makes sense. +1

[juliandoucette]

Migrated to ​https://gitlab.com/eyeo/web.eyeo.com/issues/17.