[p2pu-dev] P2PU API

John Britton public at johndbritton.com
Tue May 31 15:14:36 UTC 2011

I'd love to have a clear understanding of what we're doing about data
privacy. Ideally we should be telling people that anything they submit (save
for passwords,  billing info, or anything else we promise not to share) will
be publicly accessible. The default state for data submitted to the site is
contact info:
@johndbritton - http://twitter.com/johndbritton

On Tue, May 31, 2011 at 4:16 AM, Philipp Schmidt <phi.schmidt at gmail.com>wrote:

> On 31 May 2011 06:01, Jessy Kate Schingler <jessy at jessykate.com> wrote:
>> i agree with stian;s characterization. let's call the statistics stuff a
>> reporting API, and the other an extension API (as in, people could use it to
>> extend the ways people interact with p2pu).
> this is a good distinction. i know that our lawyers have serious concerns
> about anything that exposes user data (even in semi-aggregate form, and even
> if the same data could be scraped from the site) which affects the reporting
> API. however, metrics are an in-house priority so even if we can't easily
> make this data available through an API, we will have much better reporting
> / tracking / status information in the near future.
> i'd love to push on the idea of the extension API, because that seems an
> opportunity to build additional features and ways to learn for our users,
> and connect P2PU to other sites/platforms/services.
> -- P
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20110531/2fbef2e5/attachment.html>

More information about the p2pu-dev mailing list