in short: spending a little less time on JS the language, and more on app development
@afeld I think time spent on debugging and testing on a team would be useful and it would encourage and reinforce the valuable tool of reaching out for help, being open to suggestions and critiques. It could work both ways with students degugging/looking understanding another's code and then reversing roles. It seems a lot of the entry-level web dev jobs is coming in and working with someone else's idea of code or especially whenever freelancing. That's my two cents.
even though I'm not a student :) :shipit:
im having trouble authenticating instagram. i signed up for a client and have a client ID but i don't know if i need to further authenticate something?? when i use the client ID from your code it works but when i replace it with my client ID, there is no data coming thru. any ideas?
also, question about using the client ID or acces token with js: is having these info on the client side a risk to security? what are best practices ?
ok so after further reading it seems like i need an access token and need to authenticate it wither from server side or client side
im trying the client side (implicit) authentication
hm, still no luck. i think authorized my client info? the authentication page has instructions as to how users could give us permission? is the user the user of the app or are we the developers users? this is so confusing.
well i authorized a token that doesnt seem to work nor the client id
if u have any advice as to how u got your client id to work that would be great
you can just use my client ID from the demo page
it may only work on certain endpoints without an access_token