I really like how you are going auth with the secret GUID, that's really cool!
In my case the auth needs to be in some way tied to a User's token to hit the dev.to API. OAuth would be ideal here but if I can't get oauth access I will probably put my token in an ENV var. Then I will be able to get the view count of my own posts, but wouldn't be able to get view counts of OTHERS posts. If that were the case other developers would need to deploy their own instance, and replace the api keys to try it for themselves. I don't want to collect others Personal Access Tokens as that would be a bad security practice. So hopefully I can get oauth access, to either way I'm forging ahead!
Since I'm tied to dev.to auth I don't think I can use your cool GUID approach! But I'll definitely keep it in mind for other things!
Hey @raddevus !
I really like how you are going auth with the secret GUID, that's really cool!
In my case the
authneeds to be in some way tied to a User's token to hit the dev.to API. OAuth would be ideal here but if I can't get oauth access I will probably put my token in an ENV var. Then I will be able to get the view count of my own posts, but wouldn't be able to get view counts of OTHERS posts. If that were the case other developers would need to deploy their own instance, and replace the api keys to try it for themselves. I don't want to collect others Personal Access Tokens as that would be a bad security practice. So hopefully I can get oauth access, to either way I'm forging ahead!Since I'm tied to dev.to auth I don't think I can use your cool GUID approach! But I'll definitely keep it in mind for other things!
That makes sense. I'll look for updates as you move forward on your interesting project.