On Dec 9, 2009, at 10:57 AM, Jan Wildeboer wrote: > Hrmbl. Agreed. Repeat is not really right.
It's not? From what I understand (and I could be mistaken), many of the possible scenarios being discussed do show the same notice more than once. That's "repeating" it, in my view. > I still fail to see a real usecase for this behaviour anyway. Other than matching Twitter's retweet API, so do I. I'm not thrilled with Twitter's functionality and sincerely dislike the inability to edit the retweet-ed notice before it gets published. I never use Twitter's "retweet" button because of this limitation. > IMHO whatever > I do should be in my timeline. Agreed. > So I would always see it as a new notice. This is why it sounds like "repeat" to me…. From a user's perspective, I am "repeating" another user's notice. The only synonym I can think of is "rebroadcast", but "repeat" sounds simpler and more generic. > For > space saving identical notes could be reduced to a link, but at leat the > time difference of the OP and my "re-minding" is an important statistical > info that I would like to collect. > > "Remind my friends" is a good term though! > > Jan I kind of like that, but the "remind" terminology strikes me as too specific to a calendaring use case. On that note, this also raises the point that if I, for example, don't see one of my subscriptions' notices that has been repeated (or forwarded or whatever), but then another user I'm subscribed to also repeats or forwards the same notice, I would like both to appear in my timeline since I may get to see the second but not the first. Furthermore, the notion of repeatedly seeing the same or similar notices from various people gives me an important peripheral awareness of how many in my network are thinking about the same topic at any given time. This is something I've come to rely on as I began to follow more and more people, so I actually appreciate seeing multiple "retweets" from different people multiple times. My 2 cents. :) Whatever happens, it is very exciting to see StatusNet developing so nicely and so rapidly. Cheers, -Meitar Moscovitz Personal: http://maymay.net Professional: http://MeitarMoscovitz.com > Jan H Wildeboer | > EMEA Open Source Affairs | Office: +49 (0)89 205071-207 > Red Hat GmbH | Mobile: +49 (0)174 33 23 249 > Technopark II, Haus C | Fax: +49 (0)89 205071-111 > Werner-von-Siemens-Ring 11 -15 | > 85630 Grasbrunn | > _____________________________________________________________________ > > Reg. Adresse: Red Hat GmbH, > Technopark II, Haus C, Werner-von-Siemens-Ring 11 -15 > 85630 Grasbrunn, Handelsregister: Amtsgericht Muenchen HRB 153243 > Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham, > Charles Cachera > _____________________________________________________________________ > > GPG Key: 3AC3C8AB > Fingerprint: 3D1E C4E0 DD67 E16D E47A 9564 A72F 5C39 3AC3 C8AB > > ----- Original Message ----- > From: [email protected] > <[email protected]> > To: [email protected] <[email protected]> > Sent: Wed Dec 09 12:50:23 2009 > Subject: Re: [StatusNet-dev] Forward (retweet) support > > On 12/8/09 9:56 PM, Jan Wildeboer wrote: >> I would suggest "repeat". Repost hints at it becoming a complete new >> entry. >> But AFAICS the real function is merely adding a link to a post from s/o >> else. >> >> So the function is to repeat sth. in the sense of amplifying or spreading. > > To me, "repeat" still says that it'll get sent out a second time, but > what it's doing is more like "share this with my subscribers who haven't > seen it yet". > > How about "Share"? > > (If we're really ambitious, that could then fold out to options whether > to share to other services with a repost, or just to your local friends.) > > -- brion vibber (brion @ status.net) > _______________________________________________ > StatusNet-dev mailing list > [email protected] > http://lists.status.net/mailman/listinfo/statusnet-dev > _______________________________________________ > StatusNet-dev mailing list > [email protected] > http://lists.status.net/mailman/listinfo/statusnet-dev _______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
