Define Creepiness Service

API Outline:

POST /privacynotincluded/vote

{
	attribute: "creepiness" (or "confidence")
	rating: 0-99, // can be boolean by sending "true" or "false"
	id: 235325
}

Requires CSRF

Response codes: 201 is created. 400 is error (will return error text).

GET /privacynotincluded/product/235325

{
    id: 235325,
    name: “Smart Thermostat”,
	votes: [{
		attribute: "creepiness",
		rating: 45, // average of all votes
		votes: 3245,
		vote_breakdown: { // This can be an array
			"1": 34, // 0-19 vote
			"2": 355, // 20-39 vote
			"3": 34, // etc...
			"4": 355,
			"5": 23
		}
	}, {
		attribute: "confidence",
		rating: 1,
		votes: 345,
		vote_breakdown: {
			"true": 34, // "would buy"
			"false": 355
		}		
	}]
}

GET /products

Returns ranked product list array (most to least creepy?). Use same schema-per-item as individual /product above.

General Questions:

• What level of rate limiting should we enforce? (via @cadecairos)

CC: @alanmoo

[cadecairos]

@kristinashu thanks! I’m going to look over the designs and propose any changes I can think of to @gvn’s initial API proposal

Lets (you, @gvn, and I) sync up early next week to make sure we’re confident that the service will support the design before I get started on it.

[kristinashu]

We have comps for the Product detail page. This is where users can vote on a product and see how other people voted on for that product. Here are the steps:

We are still exploring home page ideas but this is where people will be able to see an overview of all the results. For example, all the products listed in order of creepiest to least creepy.

Happy to hop on vidyo if you need more clarification.