On Thu, 2010-09-09 at 21:58 +0200, Axel Beckert wrote: > On Thu, Sep 09, 2010 at 01:55:54PM -0600, Aaron Toponce wrote: > > It just came to my attention that the web interface keeps everything in > > place when "recycling" a notice, including group tags. As you can > > imagine, if the notice is popular, the group gets spammed with the same > > notice over, and over, and over again. Instead, because the notice has > > already reached those groups once, any additional re-notice should > > change the group tags to hash tags, to prevent spamming thou group. > > Good idea! +1
This is not, actually, a good idea. First, it's based on an incorrect assumption -- that "repeating" a notice will repost it to the same groups it's already been sent to. That's incorrect! IF CLIENT SOFTWARE USES THE REPEAT API, this will not happen. If the client software does not use the repeat API, then it's going to get reposted to each group and each mentioned user. The way to fix this problem is to encourage client developers to use the repeat API. If you know of a client that doesn't do this, let us know, and we'll put the hammer on them. Lastly, it's simply incorrect to replace group tags with hash tags. Group tags are addresses, just like mentioned users are addresses. It would be incorrect to change "@evan check this out" to "#evan check this out", and it's incorrect to change "!group check this out" to "#group check this out". -Evan ________________________________________________________________________ Evan Prodromou, CEO StatusNet Inc., 1124 rue Marie-Anne Est #32, Montreal, QC H2J 2T5 T: 438-380-4801 x101 C: 514-554-3826 W: http://evan.status.net/ E: e...@status.net
_______________________________________________ StatusNet-dev mailing list StatusNet-dev@lists.status.net http://lists.status.net/mailman/listinfo/statusnet-dev
