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

Implement /api/v1/zombiereport #52

Open
vecna opened this issue Jan 26, 2017 · 1 comment
Open

Implement /api/v1/zombiereport #52

vecna opened this issue Jan 26, 2017 · 1 comment
Assignees

Comments

@vecna
Copy link
Member

vecna commented Jan 26, 2017

A POST cryptographic signed containing number fields:

{
    timestamp: ISO format about when the post is done
    content1: number
    content2: number
}

content has to be defined on tracking-exposed/web-extension#23

from the headers publicKey is associated to an authenticated user, and the number are updated. the number reported are send incrementally. Will never happen that a number sent would be lesser than the previous.

@vecna
Copy link
Member Author

vecna commented Feb 27, 2017

The reason why slave is used despite the historical heritage, is because the interface report back how much time the facebook user spent on facebook. This voluntary contribution is a form of nowadays slavery. but probably using zombie the message remain the same without dealing with the master/slave historical meaning.

@vecna vecna changed the title Implement /api/v1/slavereport Implement /api/v1/zombiereport Feb 27, 2017
@vecna vecna self-assigned this Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant