Keep track of already handled cv's on separate systems

[PeeHaa]

On a normal working day I'm working on at least 3 different systems.

I would really love to have some way to keep track of cv requests I already handled.

I think this should be doable with either a custom login or an oauth logged in based on the SO account (if this is possible).

Am I alone to think this would be useful?

[MadaraUchiha]

I think it might be possible. I don't see why not. It would require some thoughts about DB and server-side, but seems doable enough.

[ghost]

AFAIK this should be possible through the Stack OAuth to authenticate a user then on the our end make profile in database for that user storing their visited posts click-tracked and also I think Stack API should allow seeing if the user has already voted on a post. I'll look into that part when I have the time.

[MadaraUchiha]

I really must learn the Stack API one day :|

On Sat, Aug 3, 2013 at 5:17 AM, Kyra D. [email protected] wrote:

AFAIK this should be possible through the Stack OAuth to authenticate a
user then on the our end make profile in database for that user storing
their visited posts click-tracked and also I think Stack API should allow
seeing if the user has already voted on a post. I'll look into that part
when I have the time.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-22046783
.

[ghost]

Setting the authentication scope to the following I would expect we should be able to access voting history. I can't figure out how through the API what object would return voting info. Possibly might not be such an object made yet.

private_info - access full history of a user's private actions on the site.

Also I am rather hesitant to have people grant such access to the app. It's like hey everyone gimme the keys to your private stuff and we'll make your life more convenient. I wonder if the API allows you to fine tune the permissions. I know some OAuth apps will notify the user of what information is being allowed to be accessed when they are prompted for access. If so, then I would be fine with it since all we would access is the close/delete vote history. Both of which are not a privacy concern as much as up/down votes.

Update

See: http://stackapps.com/questions/4260/accessing-authenticated-users-close-delete-history
Upvote the crap out of that so we can get that feature implemented.

[DaveRandom]

FYI API v2.2 is just around the corner, SE are currently testing a mobile app that uses it. I know it contains a lot more in the way of writeable methods for authenticated users, it may quite possibly provide deeper access to profile info as well - you could always go and ask in the Tavern on meta but past experience tells me they won't give much away before its released.

[ghost]

@DaveRandom I asked about this and seems like it won't have such access =o(

The only thing I can think of doing as an alternative is to have the cv-pls plugin submit the question ids voted on to cv-pls.com which will store it in users vote table so can then filter those out on an authenticated user. Otherwise no way to ensure persistent tracking across multiple systems. Thoughts?