HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
facebookarchive
instagram-ruby-gem
Ruby2016–2016
facebookarchive / instagram-ruby-gem · Archived

instagram-ruby-gem

The official gem for the Instagram API

Explore on GitHubRead Hacker News discussions
2Distinct people
2Mentions
0Explicit recommenders
1.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The official gem for the Instagram API

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2016-04-08 21:46:50 UTC to 2016-08-02 16:27:35 UTC. Weeks start Monday, UTC.

012016-04-04 00:00:00 UTC to 2016-04-11 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 42016-04-11 00:00:00 UTC to 2016-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-18 00:00:00 UTC to 2016-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-25 00:00:00 UTC to 2016-05-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-02 00:00:00 UTC to 2016-05-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-09 00:00:00 UTC to 2016-05-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-16 00:00:00 UTC to 2016-05-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-23 00:00:00 UTC to 2016-05-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-30 00:00:00 UTC to 2016-06-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 302016-06-06 00:00:00 UTC to 2016-06-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-13 00:00:00 UTC to 2016-06-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-20 00:00:00 UTC to 2016-06-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-27 00:00:00 UTC to 2016-07-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-04 00:00:00 UTC to 2016-07-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-11 00:00:00 UTC to 2016-07-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-18 00:00:00 UTC to 2016-07-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-25 00:00:00 UTC to 2016-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-01 00:00:00 UTC to 2016-08-08 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 1

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 42016-04-04 00:00:00 UTC2016-04-11 00:00:00 UTC101
Apr 112016-04-11 00:00:00 UTC2016-04-18 00:00:00 UTC000
Apr 182016-04-18 00:00:00 UTC2016-04-25 00:00:00 UTC000
Apr 252016-04-25 00:00:00 UTC2016-05-02 00:00:00 UTC000
May 22016-05-02 00:00:00 UTC2016-05-09 00:00:00 UTC000
May 92016-05-09 00:00:00 UTC2016-05-16 00:00:00 UTC000
May 162016-05-16 00:00:00 UTC2016-05-23 00:00:00 UTC000
May 232016-05-23 00:00:00 UTC2016-05-30 00:00:00 UTC000
May 302016-05-30 00:00:00 UTC2016-06-06 00:00:00 UTC000
Jun 62016-06-06 00:00:00 UTC2016-06-13 00:00:00 UTC000
Jun 132016-06-13 00:00:00 UTC2016-06-20 00:00:00 UTC000
Jun 202016-06-20 00:00:00 UTC2016-06-27 00:00:00 UTC000
Jun 272016-06-27 00:00:00 UTC2016-07-04 00:00:00 UTC000
Jul 42016-07-04 00:00:00 UTC2016-07-11 00:00:00 UTC000
Jul 112016-07-11 00:00:00 UTC2016-07-18 00:00:00 UTC000
Jul 182016-07-18 00:00:00 UTC2016-07-25 00:00:00 UTC000
Jul 252016-07-25 00:00:00 UTC2016-08-01 00:00:00 UTC000
Aug 12016-08-01 00:00:00 UTC2016-08-08 00:00:00 UTC101

What Hacker News says

2 sources
instakill·Aug 2, 2016
Instagram, instead of focusing on making important improvements to its own app and platform, decide to clone Snapchat. Color me surprised. Things that are shit with IG and still require attention: - there is no real onboarding experience [1] - good luck contacting a human that works at Instagram with a support query as a user [2] - good luck contacting a human that works at Instagram with a support query as a developer [2] - developer libraries are abandoned [3] - the API is a joke. - There is still a lack of support for HD photography. - The 3rd party developer experience is ... well ask some of your peers and you'll quickly find out. [1] Someone at Instagram, for the love of the internet just do some reading up on this. Here's an article to get you started: https://medium.com/@scottbelsky/crafting-the-first-mile-of-p... [2] unless you s
Read the rest
talk them on Twitter. That's not creepy at all though, is it? [3] https://github.com/facebookarchive/instagram-ruby-gem
In Introducing Instagram Stories

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.