On 12/10/2009 01:04 PM, Evan Prodromou wrote:
[snip]
Some pros to this implementation:
* because they're "real" notices, repeats flow out everywhere
"normal" notices go: on the Web, in the API, over XMPP, SMS,
OMB, RSS and Atom, and to Twitter and Facebook. They also appear
in your profile timeline.
* we can implement the Twitter retweet API methods relatively easily.
I love it!
Some downsides:
* Repeats will get "repeated" everywhere; we don't remove
duplicates. So, if there are 100 repeats of a notice, those
repeats will appear in search results, on the public timeline,
in groups, in tag streams, in inboxes; everywhere. This is just
how things work right now, but it's one of the major advantages
to Twitter's retweet system that they don't get duped (I think...).
*nod* it will give us the opportunity to figure out how to filter and
present them better in the future, too, so we'll be able to improve how
we show them within the site while still retaining basic functionality
for OMB federation and bridging to other services.
-- brion
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
