April 8 2009 Conference Call: Difference between revisions
Joe.andrieu (talk | contribs) |
Joe.andrieu (talk | contribs) (→Notes) |
||
| Line 17: | Line 17: | ||
==Notes== | ==Notes== | ||
Joe updated the group on the new association being formed. | |||
Keith updated the group on ListenLog progress. The next NPR tuner is going to be released May 31 and we would like to be in there. | |||
~1.5 million users. For a while it was the #1 free app on iTunes. | |||
Because of the shear amount of users, we want to make sure we make the right decisions. | |||
Because of the timeline and the impact, we are looking to make it super simple. We've outlined some end-user functionality on the wiki, but at a minimum, we are writing data to the log. | |||
One particular hurdle is figuring out how to use the device as an identity "token" without allowing that identity to be reverse engineered from the datastore. This would allow users to claim their datastore through an associated authentication loop, while avoiding both a signup process and identity-tagged log entries. (That is, the logs should be effectively anonymous.) | |||
==Next Meeting== | ==Next Meeting== | ||
*[[April 22 2009 Conference Call]] | *[[April 22 2009 Conference Call]] | ||
Revision as of 12:09, 8 April 2009
Conference Call Notes
Drafted by Joe Andrieu, April 8, 2009
IRC
#vrm at chat.freenode.net
Other Calls
Attendees
- Joe Andrieu
- Dean Landsman
- Keith Hopper
Notes
Joe updated the group on the new association being formed.
Keith updated the group on ListenLog progress. The next NPR tuner is going to be released May 31 and we would like to be in there.
~1.5 million users. For a while it was the #1 free app on iTunes.
Because of the shear amount of users, we want to make sure we make the right decisions.
Because of the timeline and the impact, we are looking to make it super simple. We've outlined some end-user functionality on the wiki, but at a minimum, we are writing data to the log.
One particular hurdle is figuring out how to use the device as an identity "token" without allowing that identity to be reverse engineered from the datastore. This would allow users to claim their datastore through an associated authentication loop, while avoiding both a signup process and identity-tagged log entries. (That is, the logs should be effectively anonymous.)