Redent enhancement: redent to group

Redent enhancement: redent to group

Issue ID:2144
Issue Category:enhancement
Component:uncategorized
Priority:normal
Status:active
Assigned:evan
Version:0.9
Milestone:0.9
Keywords:repeat redent redents retweet RT RD

I refer to the redent button as a bully-button because it reposts the entire dent again to the same group(s). The members of this group have already read it and I think they do not feel the urge to read it again. This leads to just ignoring redents.

On the other hand it would be an interesting feature if you could redent to another group. For instance when someone dented something and you think, hey this is a nice quote, you should be able to click the redent button (this should remove all "!" from dent ~ s/!//g) and you should be able to choose from a list of groups you're member of to add for instance !q.

The only problem I can see here is that the 140 char limit would be exceeded, but this is a coder's problem, which I do not think about atm.

As well you should be able to redent to no groups.

Oh, and if this is implemented I think you can change "RT" into "RD" since it will not annoy me any longer.

Legacy Data

This issue was migrated from another tracking system. The legacy data at time of import is provided below as a reference.

Ticket ID: 
2144
Reported by: 
pietercolpaert
Owner: 
evan
Status: 
new
Type: 
enhancement
Component: 
uncategorized
Priority: 
3
Version: 
0.9
Milestone: 
0.9

Updates

#1

rysiek

@pietercolpaert: maybe the RD button should *change* !'s into #'s, rather than remove them altogether?

→ Might be better solution

#2

I'm not 100% but I'm pretty sure that the devs do not want to implement a repeat system that drops group tags. i.e. changing !q to #q

Because this would destroy the link to the group.

http://lists.status.net/pipermail/statusnet-dev/2009-December/003020.html

#3

#1751 is ''detect repeats within a group''.

#4

The problem I see in this is that what if someone who is a member of the group isn't actively watching their client when those dents are being posted?

Case in point: a few weeks ago, I was away all day, but left Gwibber open. When I got back, I redented from my backscroll a few dents from the group and got yelled at by group members. I felt that perhaps I was passing on information which those who weren't around earlier would have been unlikely to see but would be interested to see.

If there should be an assumption that "If you weren't there when it was posted originally, you miss out forever" then that's something which may be better handled with policy/etiquette rather than a technical measure which essentially breaks the purpose of group memberships: to see dents in your feed without having to watch hashtags.

#5

Related: if I am a member of group !group, and I redent a dent which someone posted with "!group" but without being a member of !group, the dent is still not posted into !group.

#6

There's not currently a way to do repeats with a specific destination, whether it be a person or group. Being able to select specific user or group destinations while posting *and* while repeating -- separate from the @-mentions and !-groups within your original text -- will be good to do, but isn't quite ready in the system yet.

Note that repeats are not actually sent to groups at all; they're only sent to your followers and anyone else consuming your public stream. (If they do go to groups, that's an unexpected bug, and not one we've been able to reproduce before.)

Manually copy-pasting a message and putting "RD" or "RT" or a symbol at the front is not treated the same as repeating; that is sending a new message, and any group markers that are in the message are then interpreted just as if you were sending any other message -- the message goes to any groups that you're in that are listed.

#7

(Note that Gwibber doesn't actually do repeats -- it copy-pastes text into a new notice, which is the cause of extra group delivery.)

Login or Register to modify this issue, or to receive updates by email.

You can also subscribe to the RSS feed for updates to this issue.