This sounds like a really cool idea and I'd like to see it. I hope you move forward with it for the contest. Also, here's something related (I think)... My app entry in the #dohackathon allows every user to start immediately without any login -- I generate a GUID (secret id) that connects the user to her content. It's kind of weird but check it out and see what you think. It allows the app to save data for the user but not require the user login ever. Plus I've added a way for the user to easily get the long GUID using a QR Code so they can access their content from any device. I'd be interested in whether or not you could use this idea in your app too.
If you get a chance take a look at my entry and let's discuss the login thing. Good luck.
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!
This sounds like a really cool idea and I'd like to see it. I hope you move forward with it for the contest. Also, here's something related (I think)... My app entry in the #dohackathon allows every user to start immediately without any login -- I generate a GUID (secret id) that connects the user to her content. It's kind of weird but check it out and see what you think. It allows the app to save data for the user but not require the user login ever. Plus I've added a way for the user to easily get the long GUID using a QR Code so they can access their content from any device. I'd be interested in whether or not you could use this idea in your app too.
If you get a chance take a look at my entry and let's discuss the login thing. Good luck.
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.