Hey Craig,

Yeah, this is a totally desirable feature, IMO.

I've been following "Open Like" ( http://openlike.org/ ) as a possible
option for this - however, it's currently a bit stagnant as a project
as well as currently being "faux-pen" (similar to XAuth) - where it
depends on a central registry of services.

Last I read, they were going to release a v2 (which I've never seen
beyond a "prototype" back in June), and along with that announcement
they claimed there would be a v3 that supported "pluggable services"
via OExchange - http://www.oexchange.org/ . I started an OExchange
implementation back in the summer that I need to revisit and commit
real soon now (tm).

I *think* OExchange goes a long way in this regard (there's a fairly
minimal difference between a "share" and a "like"/ "favourite" imo).
We should be able to - at the very least - build upon oexchange here.

Thoughts?

.j

On Sat, Sep 18, 2010 at 8:30 PM, Craig Andrews
<candr...@integralblue.com> wrote:
> I'm wondering how favoring a notice that is not currently on your home
> StatusNet instance could work. Here's an example:
>
> My account is on http://identi.ca/candrews. Let's say I'm browsing around
> teh intarwebs, and come across a notice at http://obscure.com/notice/123
> which I like. I am not subscribed to this obscure user's stream, nor do I
> want to - it's just a one off notice I like. Because the site is obscure,
> no one at identi.ca has subscribed to this user's stream, so
> http://obscure.com/notice/123 isn't known as a remote notice in
> identi.ca's database.
>
> I would like to favorite http://obscure.com/notice/123 Ignore the fact
> that there is no UI to do so for now :-)
>
> 1. At the protocol level, can OStatus favor this notice? Or would
> subscription/previous awareness be required?
>
> 2. If it is possible at the protocol level, at the StatusNet code level,
> how can we send that favor notification? (Again, ignoring the fact there
> is no UI to do so for now)
>
> Background: I'm plotting how to make a Facebook-esq "Like" button - but
> based on StatusNet. And this is one part that I haven't been able to wrap
> my mind around yet.
>
> Thanks,
> ~Craig
>



-- 
James Walker :: http://walkah.net/ :: http://james.status.net/
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev

Reply via email to