How would per-user ratings be tracked? What if a user of my app who is
not also a BreweryDB user wants to rate a beer? Or would the rating
for a given beer be some aggregate of all ratings for that beer?
Just a thought, what if every rating were tied to a user identifier,
like email address, that every BreweryDB app could look up. Then, a
rating of a given beer by
f...@example.com in FrostyMug could be read
by Steve's Beer RAM app. The ratings by each user (as long as they use
the same email address) are consistent throughout the BreweryDB
ecosystem, and each app developer can determine for themselves how to
aggregate the ratings for recommendations. This would work even if
f...@example.com is not a BreweyDB user.
Are there privacy/third-party concerns with sending user information
from my app to BreweryDB even if that user has not explicitly said
they want to register with BreweryDB? What about using an md5 hash of
the email address instead? Only the individual apps know their users'
email addresses, and BreweryDB only sees the hash.
-- Josh
On May 14, 9:43 am, David Register Website <
da...@davidmregister.com>
wrote:
> Got it. For got that POST was not limited.
>
>
>
>
>
>
>
>
>
> On Mon, May 14, 2012 at 9:40 AM, Jason Austin <
ja...@pintlabs.com> wrote:
> > The piece to add a new rating would probably be POST requests, which don't
> > count against your request limits (neither do PUT and DELETE).
>
> > On Mon, May 14, 2012 at 9:38 AM, David Register Website <
> >
da...@davidmregister.com> wrote:
>
> >> I think most beer website have some kind p rating system for their beers.
> >> I have built one as well. This would be a nice feature and would give us a
> >> good starting point to always have data to work with, even for those not so
> >> popular beers. But we also have to keep in mind that the user might get
> >> "rating happy" and use up all your request....
>
> >> On Mon, May 14, 2012 at 9:33 AM, Jason Austin <
ja...@pintlabs.com> wrote:
>
> >>> So a question to a few of you who have made your own rating system…would
> >>> you be interested in "centralizing" those ratings in BreweryDB, pulling
> >>> data from BreweryDB and pushing rating data from your application back to
> >>> BreweryDB? The benefits would be more ratings from the community of
> >>> BreweryDB users, so you would have ratings for beers and breweries that
> >>> your specific users may not have rated yet.
>
> >>> - Jason
>
> >>> *Jason Austin*
> > *Jason Austin*