All of the following information is based on go version go1.17.1 darwin/amd64
.
GOOS | Out of the Box |
---|---|
aix |
✅ |
android |
✅ |
Instagram scraping user tags 2020 | |
Brief demonstration on how to scrape and collect user tags without needing login information. | |
A lot of data end points such as "viewing followers" is blocked by public users(not logged in). | |
This is a way to bypass one of these endpoints. | |
Scrape user tags (same as the url) -> instagram.com/username/tagged | |
https://www.instagram.com/graphql/query/?query_hash=31fe64d9463cbbe58319dced405c6206&variables={"id":"29883180","first":12} | |
Url Breakdown |
Price breakdown vs DigitalOcean, Vultr and Linode: | |
RAM / CPU Cores / STORAGE / Transfer | |
$5/mo | |
LightSail: 512MB, 1, 20GB SSD, 1TB | |
DO: 512MB, 1, 20GB SSD, 1TB | |
VULTR: 768MB, 1, 15GB SSD, 1TB | |
$10/mo |
1. Bryce Canyon National Park - Thors Hammer | |
2. Skagit Valley Tulip Festival | |
3. Big Sur/Bixby Canyon Bridge | |
4. George Rickey - Triple Execentric gyratory (Cleveland) | |
5. Spring Grove Cemetery - Cincinatti | |
6. Colonial creek campground (Diablo Lake) - Seattle | |
7. Crater Lake - Oregon | |
8. Chesil Beach | |
9. Lakeview Cemetery - Hacerot Angel | |
10. Devils Den - Williston Florida |
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
(10/30/2016) I am not sure when and how this gist gained quite a few stars... But as stated in the v1.13 change log (from 06/16/2015): some content may be outdated, and I am not going to fix them. Moreover, having learned much myself, I do not necessarily agree with every point made in this document from 2.5 years ago. Therefore, please take views from this document with a grain of salt, and do further research as you see fit.
This document was initally written for a friend of mine, Jiawen Li, so it might reflect some personal tastes here and there. For instance, some discussions are geared towards Windows, though *nix is obviously superior. For another example, when I say "you seem to love Sublime Text a lot," I'm certainly not expecting most people to love Sublime (in fact I never used it for more than three minutes in a row).
This document is written in Markdown. The Markdown rendering engine on GitHub Gist is somewhat limited a
git branch -m old_branch new_branch # Rename branch locally | |
git push origin :old_branch # Delete the old branch | |
git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote |
#Introduction
Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.
Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.
brew install git bash-completion
Configure things:
git config --global user.name "Your Name"
git config --global user.email "you@example.com"