On Thu, Dec 10, 2009 at 10:15 PM, Brion Vibber <[email protected]> wrote:
> Evan said:
>> 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.
Isn't it extremely easy to filter out and present them like Twitter
with this system? Just hold onto every already shown ID
Pseudo-code (actually, looks rather like Python ;-) )
for notice in notices:
if notice.repeat_of in shown:
continue
elif notice.id in shown:
continue
if notice.repeat_of:
shown.add(notice.repeat_of)
else:
shown.add(notice.id)
notice.show()
As long as the notices' show-method shows all the repeated persons
when repeat_of exists, it'll work just like *I THINK* Twitter works (I
haven't used Twitter since identi.ca came...).
Like: it will pop to the top (yay!) the last time someone repeated it.
--
Beste helsing,
Odin Hørthe Omdal <[email protected]>
http://velmont.no
_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev
