Hi,

I just started to test and hack @anywhere.
what I found is documented here [0].

as I got more information I'll update on the above doc

[0] -
http://docs.google.com/Doc?docid=0AYWl57IYdOIPZGhkcG52bnpfODVkZHN4M2Qyaw&hl=en

thanks
On Sat, Apr 17, 2010 at 2:08 AM, Arunoda Susiripala <
[email protected]> wrote:

> hi,
>
> This is about my gsoc proposal [0] which is about to build a twitter
> @anywhere like platform
> Now twitter @anywhere is out [1] and I think this is the right time to
> start the discussion.
>
> @anywhere provides
> ------------------------------
> * allows users use current API as a Javascript library [2]
> * some set of special widgets that rendered on the page using js (follow
> button,statusbox)
>
> problems
> -------------
> * Do we actually going to compatible twitter's @anywhere API. We have
> twitter like API.
>   So are we going to wrap it with javascript
> * The biggest problem - Twiiter is centralized but we are federated.
>    So how can we deal with remote users.
>    eg:- How a abc.status.net user subscribe to identi.ca (this seems not
> to be a big problem)
>          How do we render statusBox for remote users and get their User
> Object to play with(which is currently done by @anywhere) .
>
>
> [0] -
> http://docs.google.com/Doc?docid=0AYWl57IYdOIPZGhkcG52bnpfNjJmamYyaHZ3aA&hl=en
> [1] - http://dev.twitter.com
> [2] - http://twitter.com/anywhere/status/12238165571
>
> thanks.
>
> --
> Arunoda Susiripala
> http://arunoda.com
> http://twitter.com/arunoda
>



-- 
Arunoda Susiripala
http://arunoda.com
http://twitter.com/arunoda
_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev

Reply via email to