Evan Prodromou wrote:
OK, this is pushed to gitorious in 0.9.x. Repeating is in the database
and Web UI, as well as in the API.
Repeats are shown in the Web UI with "Repeated by" on most pages,
"Repeat of" on profile (which doesn't show author info).
Sarven, the form and the Web UI need some polish; the sooner the better.
Please give it a look, folks.
We've pushed 0.9.0rc2 to identi.ca, so "regular" users are getting to
test out this feature for the first time. Here are some big issues
people have, and some proposed changes to deal with them.
* *Group reposts*. See http://identi.ca/notice/17305317 for an
example. Repeats of notices with "!group" in them get reposted to
that group. One solution posited was to change !group to #group. I
strongly disapprove of unnecessarily modifying the input text, and
!group is an address, not a category, anyways. /I'd like to change
our behaviour so that for repeats the link in the rendered content
remains, and the notice tag remains, but the notice is not
distributed to the group inbox nor to the inboxes of group
members./ Objections?
* *Replies.* Similarly, a repeat of user X's notice is marked as a
reply to that user (since the text of the repeat is "RT @X ...").
Similarly, any mentions inside the original notice text are
duplicated. /I'd like to change our code so that repeats aren't
stored as replies for either the original author or anyone
mentioned in the original content. I think we should also not save
the original notice ID in reply_to for the repeat./
* *Conversations. *Repeats appear in the tree on the conversation
page. See http://identi.ca/notice/17305286 and
http://identi.ca/notice/17304105. I see two ways to fix this: a)
don't store the original notice's conversation ID in the repeat's
"conversation" column, or b) store the ID, but don't show notices
with non-null repeat-of columns on the conversation page. Of
these, I prefer b); I think the repeat is still semantically part
of the conversation and we probably shouldn't lose that context info.
* *Confirmation.* Too easy to fumble-fingers and accidentally repeat
a notice. See http://identi.ca/notice/17341036 and
http://identi.ca/notice/17322901. Seems to me to be low-impact;
users can always go delete the repeat. However, Sarven's added a
confirmation popup, which makes repeating just a tiny bit harder,
but which seems to work nicely.
* *Repeat timestamp.* See http://identi.ca/notice/17321240. We could
change "Repeated by _nickname_" to "Repeated by _nickname_ 23
minutes ago". I'm disinclined to do it, though; seems we already
have a lot of data in the notice info area.
* *Repeat icon*. It can be hard to identify a notice as a repeat;
compare Twitter's icon at the beginning of the notice. See
http://identi.ca/notice/17321471. I think we should probably add
an indicator icon.
* *General layout*. Some people want a different layout for repeat
notices. See for example http://identi.ca/notice/17321116. I'd
generally prefer to keep our layout close to Twitter's.
* *Editable repeats. *See e.g. http://identi.ca/notice/17329151.
Some users want to add editorial notes or comments to their
repeats. I think this is probably a bad idea; since we hide the
content of the repeat most of the time (in favor of the content of
the original), it doesn't make much sense to edit it. I also think
it'd be hard to provide a user interface that makes it easy to do
one or the other.
* *The name.* See for example
http://identi.ca/conversation/17289198. I think 'repeat' is clear
and evocative of 'retweet' so /I'd like it to stay as is/.
So, the upshot: I'd like to quickly make changes for the first four
issues here, and deal with the others later.
Comments, ideas, objections?
-Evan
--
Evan Prodromou
CEO, StatusNet, Inc.
[email protected] - http://identi.ca/evan - +1-514-554-3826
_______________________________________________
StatusNet-dev mailing list
[email protected]
http://lists.status.net/mailman/listinfo/statusnet-dev
