News for hackers. Stuff that matters.
Re:Show HN: Self-Scraping Instagram Search Engine by callmeed on Tuesday September 02, 2014 @02:55PM (#8259420)
I like this. I'm a big IGer and so is my wife. I was at the Giants game for Star Wars day with my kids Sunday so looking through all the #attpark / #sfgiants hashtags is fun.

However, here's one thing that annoys me with this and all "endless scrolling" web apps: when when I scroll down several pages, then click an image to see it bigger, when I go back I'm no longer at my "page".

Re:Show HN: Self-Scraping Instagram Search Engine by eiriklv on Tuesday September 02, 2014 @03:13PM (#8259509)
A really good point there! It's on the todo-list :)
Re:Show HN: Self-Scraping Instagram Search Engine by elwell on Tuesday September 02, 2014 @01:27PM (#8258909)
I'm pretty sure IG doesn't like any names that have Insta or Gram in them. (That's why Webstagram changed to Websta). Just a heads up before you develop your brand and then get kicked off their API.
[deleted]
Re:Show HN: Self-Scraping Instagram Search Engine by phpnode on Tuesday September 02, 2014 @01:48PM (#8259032)
they don't want people to be confused and think that your service is official. it's generally bad practise to tie your brand to someone else's anyway.
Re:Show HN: Self-Scraping Instagram Search Engine by eiriklv on Tuesday September 02, 2014 @01:51PM (#8259052)
Main developer here - That's a very valid point (which i see now), and we'll look into it straight away
Re:Show HN: Self-Scraping Instagram Search Engine by justboxing on Tuesday September 02, 2014 @01:59PM (#8259095)
Hi Erik,

I found the specific language in their Branding "Guidelines" that forbid the use of "Insta" and "Gram" in app or domain name.

Here's the link: https://help.instagram.com/304689166306603/

Relevant Section:

Naming Applications and Products

If you offer an application, website or product that is compatible with or related to the Instagram service, such as an app or website that uses the Instagram APIs, you may fairly and accurately describe how your application, website or product relates to Instagram. But you may not use the Instagram trademarks in your own brand, or suggest that Instagram sponsors or endorses you or your products.

Don’t:

Use “Instagram,” “IG”, “Insta” or “Gram” in your app or product name or domain name

Use the Camera Logos, or the Instagram name or logo, in your brand identity, such as your app icon, logo or product design

Use the Instagram stylized font in your logo or product or marketing materials

Re:Show HN: Self-Scraping Instagram Search Engine by eiriklv on Tuesday September 02, 2014 @02:08PM (#8259142)
Thanks! As said earlier, we'll look into it straight away. Hopefully we're able to find a solution where we don't trash our domain and rank.. :/
Re:Show HN: Self-Scraping Instagram Search Engine by eiriklv on Tuesday September 02, 2014 @02:20PM (#8259214)
We're changing our logo and titles right away.
Re:Show HN: Self-Scraping Instagram Search Engine by justboxing on Tuesday September 02, 2014 @02:31PM (#8259280)
Good Luck!
Re:Show HN: Self-Scraping Instagram Search Engine by hnriot on Tuesday September 02, 2014 @02:32PM (#8259288)
It says not to do this very clearly when you register your clientid.
Re:Show HN: Self-Scraping Instagram Search Engine by stormen on Tuesday September 02, 2014 @12:23PM (#8258500)
Backend in node.js. We leverage the fact that we get huge amounts of bot traffic, by saving all entries they fetch from Instagram to build our database of popular tags and users.
Re:Show HN: Self-Scraping Instagram Search Engine by rezacks on Wednesday September 03, 2014 @01:31AM (#8261638)
Nice work, could user remove their photos (if they want)? Maybe you could provide some special hashtag like #noindex, just some thoughts...

keep going!

Re:Show HN: Self-Scraping Instagram Search Engine by ape4 on Tuesday September 02, 2014 @02:34PM (#8259301)
How is it SELF-scraping. Isn't it THEM-scraping
Re:Show HN: Self-Scraping Instagram Search Engine by eiriklv on Tuesday September 02, 2014 @03:16PM (#8259523)
Point taken :) We just didn't think of a better term at the moment of posting.