Deployed version can be found here: https://myrhy.me/secrature

hashtag, as the key name 'hashtag' states :)

Not the Instagram developer APIs, but the one that instagram's frontend consumes. The script scrapes instagram's frontend here.

Interesting, I might reverse engineer and see if we can introduce some kind of backoff and then resume the scraping again.

I suppose this is indeed a bug, since new recently tagged images will push the page downwards. Currently the script assumes no new image additions until the scraping is done which is clearly wrong, I'll open an issue and fix it soon.

Thanks!

This scraper was written to get images and create a dataset for ML models for personal project while studying Machine Learning and Artificial Intelligence.

curious why you are scraping instagram for this purpose and not something like flickr which has a reasonable public api and tagged creative commons licensed images that are suitable for your ML purposes. at the very least, it's worth investigating archive.org's many freely licensed archives for this sort of thing.

as somebody that has fielded numerous emails from friends asking me to remove tagged photos of them from flickr, i sort of wonder about the ethics of harvesting these sorts of images from instagram, a community whose norms sort of revolve around semi-public sharing of photos. I don't doubt that there's some rationale for harvesting the images from ig, but aside from thumbing your nose at their TOS, it feels like it's a greater violation of trust to harvest your friends and strangers photos for an ML project without their informed consent.

at the very least, it's worth considering pointing your app's gaze at a set of images licensed for any purpose whatsoever rather than ones that are explicitly licensed All Rights Reserved by their respective photographers.

Does it also offer ability to search categories of images with keywords?

That's cool - what are your goals with this project?

Just decorate a function that you want to trigger on a particular event with @ghooks.events(*args) decorator, with args as the list of events that it should listen to.

I had built it a few months ago. I wanted to write a stable CLI and wanted to automate something that I'd have to use GUI for.

I setup CI, wrote few test cases and also made a style convention. This was the first project where I setup CI, write tests, adhere to a standard, and write good, atomic commits.

I learnt to use `argparse` module.

It is possible to upload more then 1 file with description and name of the gist as of now.

There is also an option if you want the gist to be secret or not. Though currently, the gists are made anonymously, they'll not be associated with your account. That is something that I should implement in near future.