Instagram

From IndieWeb
Jump to: navigation, search


Instagram is a popular photo and short video hosting silo most well known for square photos that have been processed with an image filter.

Contents

Why

Why use Instagram?

Indie photo posting client

Some of us have found it to be a useful client for posting to your site via Micropub and ownyourgram.

If your site supports receiving Micropub requests for publishing photos, you may want to consider creating a private Instagram account, using it to setup ownyourgram, and then use Instagram’s native mobile app(s) and servers purely as a convenient client for posting photos and short videos to your own site.

This technique of using a silo purely as a client to get content to your own site is also referred to as "silos as plumbing".

See PESOS below for more details.

Features

(this section is a stub and needs your contribution to complete it!)

  • photo post with:
    • reduced resolution photo, e.g. 1080x810
    • a caption (is just the first comment if it is by the author)
    • inline hyperlinked hashtags (in caption or any comment by author)
    • person-tags at locations (points) on the photo
    • venue (from Facebook's venue database)
  • multi-photo post (since 2017-02-22)
    • even lower resolution than single photo posts, e.g.: 750x750, 640x640
    • a caption (is just the first comment if it is by the author)
    • inline hyperlinked hashtags
    • limitations: no photo editing (filters only), must be square cropped
    • venue (from Facebook's venue database)
  • video post (since 2013, initially 15 second length limit, extended to 30-60sec?)
  • story (AKA "Your Story") singular post, one per profile (since mid-2016)
    • ephemeral photos and videos that disappear in 24h. The story feature allowed posting multiple photos (and/or videos) in a time sequence (shown in sequence one at a time) which many use to tell a story about their day. Access to individual story items disappear from other users' views within 24 hours.
  • comment on photos
  • like photos
  • follow users
  • notifications of comments, likes, follows, and person-tags
  • report abuse regarding a user, photo, or comment
  • search for
    • users
    • hashtags
  • private account
  • profile page (equivalent of indieweb homepage) configuration including
    • icon
    • name (as displayed next to icon, before posts)
    • 150 character bio
    • website - but not another silo profile[1]
  • who to follow - shown when you follow someone
    • 3 suggested users to follow
  • settings
    • comments
      • "Hide inappropriate comments: Hide comments that contain words or phrases often reported as offensive" toggle.
      • "Custom keywords: Comments that contain any of the words or phrases above will be hidden. Add keywords, separated by commas."
      • turn off commenting
  • ...

Exporting your data

Instaport.me and flickstagram.org let you export your Instagram photos.

freedom.io (source) can copy all of your Instagram photos and videos to WordPress, Tumblr, or Blogger, creating a new blog post for each, with the original dates and all comments intact.

Norm's instagram-backup tool exports Instagram photos and metadata.

Single Photo Bookmarklet

If you view a single photo permalink page, the following bookmarklet will extract the permalink (trimmed), photo jpg URL, and photo caption and copy them into a text note, suitable for posting as a photo that's auto-linked:

For plain text:

javascript:n=document.images.length-1;s=document.images[n].src;s=s.split('?');s=s[0];u=document.location.toString().substring(0,39);prompt('Choose "Copy ⌘C" to copy photo post:',s+' '+u+'\n'+document.getElementsByTagName("h1")[0].innerText.replace(/\n\.(\n\.)+/g,'\n'))

For HTML (e.g. storage files. escapes & < >)

javascript:n=document.images.length-1;s=document.images[n].src;s=s.split('?');s=s[0];u=document.location.toString().substring(0,39);prompt('Choose "Copy ⌘C" to copy photo post:',s+' '+u+'\n'+document.getElementsByTagName("h1")[0].innerText.replace(/\n\.(\n\.)+/g,'\n').replace(/\&/g,'&amp;').replace(/\</g,'&lt;').replace(/\>/g,'&gt;'))

Any questions, let me know! Tantek Çelik (I used the second version ("For HTML") myself as part of my photo post authoring flow until 2017-085. -t).

Drag and drop-able button version can be found here

Bookmarklet improvements

  • remove errant username from start of caption text
  • support multi-photo posts (detecting, producing markup)
  • support video posts (detecting, producing markup)
  • support mixed multi-photo/video posts

POSSE

Instagram does not have a photo upload API. However they do have comments delete / create APIs. Sadly commenting via the API is not supported. So here's how you can fake POSSE to Instagram:

  1. You post to Instagram using their client app, including location information, people tags, and caption (first comment).
  2. Your server receives a notification of the photo post via webhook call back
  3. Your server copies the photo (in PESOS fashion) to your own server
    1. creating a permalink for the photo on your own server
    2. copying the location information, people tags, and caption
    3. adding a link to the copy of the photo on Instagram with rel-syndication
  4. Your server deletes the first comment on the Instagram photo
  5. Your server creates a new first comment (thus caption) on the Instagram photo, as you, with:
    1. original caption contents followed by permashortlink for the photo on your server

And bingo, you've effectively created a POSSE copy of your photo on Instagram since it now has a permashortlink back to the new "original" on your own site.

At this point you can also use a service like Bridgy to backfeed comments on the photo from Instagram to your own site.

POSSE responses

  • Kyle Mahan POSSEs likes for Instagram photos via the official Instagram API (which is read-only for everything except, inexplicably, for likes) since 2015-01-03
    • Added POSSE for comments via "unofficial" API (Selenium/PhantomJS browser automation) on 2015-07-12
  • Bridgy Publish can POSSE likes to Instagram since 2015-01-07
  • ...

POSSE via Workflow.is

Sebastiaan Andeweg uses the iOS app Workflow to semi-automate his photo posting workflow, including a post to Instagram. He documented his Workflow workflow on Workflow.

POSSE as mobile browser

Instagram recently updated their mobile web site to allow mobile web photo posts, thus it should be possible to have your server POSSE to Instagram for you by acting as your mobile browser.

Also looking into this for Bridgy Publish support:

Manual POSSE

gRegor Morrill

gRegor Morrill posts photos on gregorlove.com first, manually posts the same photo and caption to Instagram, copies the Instagram URL and adds it as a syndication link on the original photo post.

Tantek

Tantek Çelik posts photos on Swarm (private account) for ease of mobile publishing, then uses those to create photo posts on tantek.com, and manually posts the same photo and (sometimes abbreviated) caption to Instagram, copies the Instagram URL and adds it as a syndication link on the original photo post.

Manual Notes

Some users manually cross-post occasional notes posts to Instagram, e.g.:

Tweet text to Instagram

As of this edit:

  • the original has only *2* favorites. (2,346 followers on account)
  • the POSSE copy: *130* likes and *3* comments. (14,512 followers on account)

For some reason, POSSE copies, even of *notes*, on Instagram receive more interactions per follower.

Hypothesis: the Instagram reader experience is so much smoother and nicer that it tends to encourage more use and thus more interactions.

IndieWeb note to Instagram


PESOS

Additional approaches:

Previously Tantek

Tantek Çelik uses his iPod Touch to publish photos to Swarm and Instagram for ease of posting from mobile device to the web.

Previously:

From 2015-244 to 2017-085, Tantek Çelik did manual PESOS from Instagram to public posts on his own site (tantek.com), and then used Falcon to automatically POSSE his photo posts to Facebook, Flickr, & Twitter with Bridgy Publish, as well as link back to the Instagram copy as syndication.

Since 2017-087, Tantek Çelik has been manually POSSEing to Instagram (see #Tantek above).

cweiske

Christian Weiske uses instagram2micropub to archive private instagram posts to a self-hosted Known instance automatically.

backfeed

You can use Bridgy to get some backfeed of responses from Instagram POSSE copies.

(this section is a stub)

  • limitations with Brid.gy: only first 10 likes come through.
    • Scraping the public Instagram web pages only gives you the oldest 10 likes for a picture. After that, the UI says 'and X others' anyway. The property is called edge_media_preview_like, and includes a full count, but no names, pictures or URLs of the people who like it, other than the first 10. (You can't poll either, because they give you the first, not the last.)

You can supposedly get your own API key (in sandbox mode) to do your own backfeed. (does anyone do this?)

  • Getting likes seems to be impossible without getting your app approved. Some endpoints work, others give a HTTP 200 status, but an empty array.
    • /users/self/media/recent works, probably because it contains you own pictures
    • /media/:id/likes does not work, probably because the likes are other people's content
    • /users/self/media/liked does not work, probably because your likes contain other people's content
  • Getting your app approved seems to be hard.

API

Supposed Features and Limitations

  • Instagram's official API can potentially create (and delete) comments and likes, but not photos.

Like

Ryan Barrett has found that Instagram's API now supports progammatically "liking" photos (used to 400).

Location

Cannot Comment

Ryan Barrett has found that authing with scope=comments works, but the API call still 400s.

According to Instagram's API documentation, their commenting API only works for those who are whitelisted. Unfortunately the criteria for application for whitelisting are very restrictive.

Unofficial

  • Work has also been done on determining its unofficial API (which is against Instagram's terms of service, but allows you to post): https://github.com/mislav/instagram/wiki
  • Instagram Worm uploaded photos using private/undocumented API (needs citation)
  • Instagram private API changes affect unofficial apps and photos uploaded via unofficial apps
  • Add ?__a=1 to the end of an Instagram profile, photo, or feed URL (e.g. /) to get JSON metadata. This JSON is also embedded in the normal HTML pages. Example parsing code in granary.
    • For feed URLs, the array of photo objects is in the FeedPage.feed.media.nodes[] element.
    • For profile URLs, the array of photo objects is in the ProfilePage.user.media.nodes[] element.
    • For photo URLs, the photo objects are the PostPage[].media element(s).

Permissions approval

Instagram is locking down their API and requiring all apps to go through a review process similar to Facebook's. Apps can apply now; the API restrictions start in June 2016. Developer details, legal details.

Specifically, they plan to restrict and require approval for /users/self/feed and /media/popular and any use cases that send photos outside of Instagram.

Here's the new set of permissions (OAuth scopes):

  • basic - to read a user’s profile info and media (granted by default)
  • public_content - to read any public profile info and media on a user’s behalf
  • follower_list - to read the list of followers and followed-by users
  • comments - to post and delete comments on a user’s behalf
  • relationships - to follow and unfollow accounts on a user’s behalf
  • likes - to like and unlike media on a user’s behalf

Ryan Barrett applied for basic permissions for Bridgy and oauth-dropins in Jan 2016. Both were rejected.

UX Observation

  • Videos and Photos have a very similar UI. --Bret.io 00:38, 1 July 2013 (PDT)
  • 2013 video UI: single-tapping would pause the video, you have to tap the play control to replay.
  • 2015 videos started autolooping (like Vine) without sound, and single-tapping was changed to toggle sound on/off.

Adoption

Criticism

username takeovers

How Instagram closed my account and gave it to a football celebrity - "My name is Andrés Iniesta and my only mistake was having the exact name and last name as a famous football player."

Bad Silo Interop with Twitter

Shortly after it was purchased by Facebook, Instagram stopped including Twitter metadata on their photo pages, so Twitter Cards no longer show image previews for Instagram photos.

Instagram drives more traffic to their site, at the cost of a worse experience for users.

Using OwnYourGram or another method of PESOSing your photos out of Instagram, you can control how your photos are shared on other silos like Twitter. (e.g., by including Twitter metadata, or by posting the photos directly).

Switch from Foursquare to Facebook venues

Some time in 2014-05, Instagram switched from using Foursquare's venue database (e.g. in the iOS app UI) to using Facebook's places database.

This has resulted in:

  • fewer venue matches (often completely missing venues that were present on Foursquare)
  • less accurate venue locations such as misspellings, "venues" with varied granularity (business vs neighborhood)
  • loss of venue information when cross-posting from Instagram to Foursquare (i.e. checks you into the wrong location, or a generic neighborhood rather than a specific venue)

See also

Lack of privacy of location data

When posting a photo to Instagram, if "add to photo map" is enabled (even if no venue is chosen) then the exact lat/lng of the photo is recorded. When viewing the single photo you won't see the location of it. However, when viewing the person's user profile you can switch to the map view and see their photos all on a map.

instagram-map-aaronpk-far.png instagram-map-aaronpk-close.png

The map shows photos as clusters, and zooming in will expand the clusters into smaller clusters until finally individual photos appear on the map.

It is relatively easy to figure out the approximate location of someone's work or home by looking for these clusters.

See Also

Uneditable Custom Locations

When adding a photo at a venue that doesn't exist, it is possible to create a "custom location", which is unfortunately not editable from that point on.

One potential up-side is when searching for venues, your custom locations now show up at the top of the list without needing a round-trip to the server to search.

instagram-custom-location-search.png

Creating this custom location prompts only for the name, the exact geo location is added automatically, meaning it is not possible to adjust the specific location of the venue.

Censorship beyond community guidelines

Instagram is establishing a history of censoring by removing (and sometimes restoring later) and/or hashtag results that are not actual violations of their Community Guidelines, and are otherwise innocuous material. For example:

gay kiss
Instagram has reportedly removed a photograph of a gay couple kissing at their wedding as "inappropriate".
some sexual content
Instagram's removal of sexual content has been criticised as being inconsistently enforced.
menstrual blood
http://www.scoopwhoop.com/news/insta-photo/
http://www.cosmopolitan.com/sex-love/news/a38309/instagram-apologizes-for-removing-poignant-photos-of-a-woman-on-her-period/

Article listing blocked/limited hashtags as of 2016-05-10: http://thedatapack.com/banned-instagram-hashtags-update/

DMCA

No license metadata

Unlike Flickr (and your own site if you so choose!), there's no metadata for marking photos or indeed whole photostreams as licensed under Creative Commons licenses.

i-am-cc.org lets you choose a CC license for your Instagram photographs, but you have to log into the service every three months to 'renew' the license grant.

most locked-in and user-hostile

From 2016-03-26 jwz post: Instagram Hates The Internet
Instagram is a dialup BBS. It is the most locked-in and user-hostile of the bunch, as I will now express through the medium of a <TABLE>

(analysis therein)

Downtime

  • 2013-08-28 17:27-0400 EDT

  • 2014-08-22 various times throughout the day - "news" activity on photos feature was down with user-unfriendly nginx default error message:
2014-234-instagram-502-nginx.jpg

See also

Personal tools
Namespaces
Variants
Actions
Recent & Upcoming
Resources
Toolbox