3 ms·
You may be reading/interpreting this wrong - the wrapper gives users the option to explicitly say they're not interested in X, Y or Z. Assuming that developers
by nkozyra 12y ago
You may be reading/interpreting this wrong - the wrapper gives users the option to explicitly say they're not interested in X, Y or Z.
Assuming that developers are required to qualify their presentation with some sort of context, ie "New movies about cowboys" or "Little League scores in Atlanta, GA" it will defer to the user's choices as it does now.
There is always room for abuse, but unlike spam, the application knows the source, so it's easy to cut the head off.
- weego 12y agoAlso for Now developers, pushing a card to a user is only the intent for that user to get a card (and the intent to show it in certain contexts, like on their commute, at work, leisure time and location based). There is still the Now API black box between you and the end user (plus the end user can just ignore all cards from you if they want with a single swipe). The bigger problem really was that content in the cards sent then gets fed into the Now content "context" algorithm. So for example if you receive content from something about recipes you might find you get spammed with information about restaurants around you at lunch times for example. It really doesn't all feel that great in some regards.
- nkozyra 12y agoBut isn't this iterative learning? The first time you use Google Now you generally have some very weak recommendations, but as you filter the results (by adding apps, expressly saying 'yes' or 'no' to cards), it gets better. By and large there's a lot of ML behind the scenes, but it's also supervised learning. It gets better with more data.