Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve "report" feature #14

Open
vrde opened this issue Dec 19, 2016 · 1 comment
Open

Improve "report" feature #14

vrde opened this issue Dec 19, 2016 · 1 comment

Comments

@vrde
Copy link
Collaborator

vrde commented Dec 19, 2016

From #7 (comment), by @vecna:

"report" is the action we want to trigger, a bug report or a will report ? if is a bug, is about the parsing, if is about the parsing is due to the lack of language support, so we've to drive the user on the community page and tell us how the "Public" looks like in their language. if is a report, we've to keep track of the postId, so we can interact with the system (or even automatize) a post removal

Right now the report is just a mailto:support@tracking.exposed. An idea is to improve the report feature adding a dialog asking the user to share some info with us.

@vecna
Copy link
Member

vecna commented Dec 19, 2016

ideally, to receive a certain level of automation, for every sent post we can generate a random number, that random number can be sent to us via event and used in an API call like POST https://facebook.tracking.exposed/remove/$userId/impression

{
     "randomImpressionNumber": 34242343,
     "signature": ...
}

The signature is computed with private key of hash(randomImpressionNumber + userId),

Backend side, we check such consistency, hooking via API we automatize the removal.
( The backend operations are still to be defined: do we remove the users impression, but not the HTML? )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants