4 ms·

https://web.archive.org/web/20191207221404/https://github.com/mgp25/Instagram-API https://web.archive.org/web/20191207221404/https://github.co... > Why did I m

https://web.archive.org/web/20191207221404/https://github.com/mgp25/Instagram-API https://web.archive.org/web/20191207221404/https://github.co... > Why did I make this API? > After legal measures, Facebook, WhatsApp and Instagram blocked my accounts. In order to use Instagram on my phone I needed a new phone, as they banned my UDID, so that is basically why I made this API.

pmlnr 7y ago
Anyone has the actual git repo as well?
- segmondy 7y ago
  If you fork git repos, make sure to pull them down, if the official repo is taken down, your forks will disappear unless you have a copy. Here's a script I made to backup all your repos, throw it into a cron and run once a month or something, where 20 is the largest number of pages you have, adjust accordingly. I actually wrote this up when a fork I had disappeared. #!/bin/bash USERNAME='segmond' for i in `seq 1 20`; do curl --fail -s https://api.github.com/users/$USERNAME/repos?page=$i | jq '.[] | .clone_url' | xargs -t -n1 git clone sleep 1 done
  - dicytea 7y ago
    > if the official repo is taken down, your forks will disappear unless you have a copy. https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility https://help.github.com/en/github/collaborating-with-issues-... I don't think that's true, I've personally recovered deleted repositories by finding its forks. edit: Ah never mind it seems things work differently in the case of DMCA takedowns
    - AdamJacobMuller 7y ago
      There is also a big difference between clicking `fork` on github vs cloning and creating a new repository (on github) and then changing the remote URL and pushing. The latter isn't "github fork" even if it is a "git fork" and won't be affected by most[1] automated takedowns. 1> where most is defined as somewhere between 0 and 100%
- deleted 7y ago
  [deleted]

pmlnr 7y ago

Anyone has the actual git repo as well?

segmondy 7y ago
If you fork git repos, make sure to pull them down, if the official repo is taken down, your forks will disappear unless you have a copy. Here's a script I made to backup all your repos, throw it into a cron and run once a month or something, where 20 is the largest number of pages you have, adjust accordingly. I actually wrote this up when a fork I had disappeared. #!/bin/bash USERNAME='segmond' for i in `seq 1 20`; do curl --fail -s https://api.github.com/users/$USERNAME/repos?page=$i | jq '.[] | .clone_url' | xargs -t -n1 git clone sleep 1 done
- dicytea 7y ago
  > if the official repo is taken down, your forks will disappear unless you have a copy. https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility https://help.github.com/en/github/collaborating-with-issues-... I don't think that's true, I've personally recovered deleted repositories by finding its forks. edit: Ah never mind it seems things work differently in the case of DMCA takedowns
  - AdamJacobMuller 7y ago
    There is also a big difference between clicking `fork` on github vs cloning and creating a new repository (on github) and then changing the remote URL and pushing. The latter isn't "github fork" even if it is a "git fork" and won't be affected by most[1] automated takedowns. 1> where most is defined as somewhere between 0 and 100%
deleted 7y ago
[deleted]