[p2pu-dev] P2PU API

[Pippa Buchanan]

I hadn't thought about visualisations - but yes, that would be cool and
incredibly useful for SoW when reporting back to our other stakeholders :-)

On 30 May 2011 16:05, Stian Håklev <shaklev at gmail.com> wrote:

> I could see two different use-cases for APIs (and I'd love to hear about
> others). One would be to give access to system statistics, and let people
> create cool data visualizations, etc faster than if they had to have all
> their code written in Python and included int he official platform. The
> other is if someone actually wanted to develop a stand-alone client for
> P2PU, for example for a mobile platform. I'm more interested in #1, and it
> seems more doable (we are a much less stable platform than Twitter in terms
> of functionality, and I don't immediately see the use of a stand-alone
> client, neither do I expect anyone to put tons of time into developing one).
> But I'd love to hear from others what uses you expect.
>
> Stian
>
>
> On Mon, May 30, 2011 at 19:53, Pippa Buchanan <Pippa.Buchanan at gmail.com>wrote:
>
>> Can I add in an additional question for this - as I know it would provide
>> more clarity when explaining the benefits for me and other less actively
>> geeky community members. I'm only feeling 23.768% geek today :-)
>> *
>> How do we imagine the API being used?
>>
>> *Er, am I right in assuming that an API would allow people to build tools
>> to pull and push data onto the system? So theoretically a tool might be
>> built to allow offline creation of course and group content such as tasks?
>>
>> Or a wordpress plugin might be built using the API which would allow users
>> to submit a blog post as a response to a task?
>>
>> Obviously, the great thing about APIs is that they really allow
>> interesting mashups to occur which we can't really predict - but it is
>> really helpful to know what types of things could obviously be developed
>> using this.
>>
>> On 30 May 2011 09:05, Philipp Schmidt <phi.schmidt at gmail.com> wrote:
>>
>>> A P2PU API has come up on various threads. It's an interesting idea. Can
>>> we get a little more concrete on the following points, so we can get
>>> feedback from community and board, as well as determine prioritization vs.
>>> other development needs?
>>>
>>> * What are the concrete benefits to P2PU? (drawbacks, risks?)
>>>
>>> * What is the effort needed to implement, support?
>>> - paid staff vs. volunteer contributions
>>>
>>> * What are the actual next steps to move this forward?
>>>
>>> Best - P
>>>
>>>
>>> _______________________________________________
>>> p2pu-dev mailing list
>>> p2pu-dev at lists.p2pu.org
>>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>>
>>>
>>
>> _______________________________________________
>> p2pu-dev mailing list
>> p2pu-dev at lists.p2pu.org
>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>>
>>
>
>
> --
> http://reganmian.net/blog -- Random Stuff that Matters
>
>
> _______________________________________________
> 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/20110530/80802626/attachment.html>