Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 54654 invoked from network); 22 Apr 2009 08:32:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Apr 2009 08:32:44 -0000 Received: (qmail 56113 invoked by uid 500); 22 Apr 2009 08:32:44 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 56080 invoked by uid 500); 22 Apr 2009 08:32:44 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 56070 invoked by uid 99); 22 Apr 2009 08:32:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2009 08:32:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vdichev@gmail.com designates 209.85.220.220 as permitted sender) Received: from [209.85.220.220] (HELO mail-fx0-f220.google.com) (209.85.220.220) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2009 08:32:36 +0000 Received: by fxm20 with SMTP id 20so3251448fxm.12 for ; Wed, 22 Apr 2009 01:32:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=YDssjeXDczBR3HcDijoTv8U0mmbM1uDyWFyUev/TWEA=; b=N0vC+H5v7iwTsdk2FmAD/m1enuOjzK6YbLZAiyb4t4c2hvHLIs7FQdtoB9ma2INC1I JhqBQcCH6+CVt0mzjWeyTnGrLw8GKQ8bOvIupvZWUItIvVLSQx8Drh7xo0KahtvrHDC+ FwAHtJVmz+5GDCqJ9spQEytSPBm1x3BxBj5zU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=hrwETRKsydMHaan45/EF+DBRllyrPRCLpJlT+3lStHnLmqwtHOVYn71t1K7ee5vz6A 4aPRk1vPCQK6plbL2P7G5riv+Ll5gOqYCuMRmn/PQNwloFuiwWNvl6Rogq/nW32nH9dH w112gsZD2lfy4T6YwoE6xkpFqiODR1SVzim2s= MIME-Version: 1.0 Sender: vdichev@gmail.com Received: by 10.239.164.76 with SMTP id s12mr364765hbd.125.1240389135958; Wed, 22 Apr 2009 01:32:15 -0700 (PDT) In-Reply-To: <8A31ECBF-5811-4EF3-B9BA-6560DCEA4679@gmail.com> References: <1F42185C-C34E-436B-AE96-198071707A93@gmail.com> <960ac33e0904212356l7264e684s8636cd26fe7fd2c9@mail.gmail.com> <8A31ECBF-5811-4EF3-B9BA-6560DCEA4679@gmail.com> Date: Wed, 22 Apr 2009 11:32:15 +0300 X-Google-Sender-Auth: e2038e2ee85a5107 Message-ID: Subject: Re: Favourite feed From: Vassil Dichev To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Oliver, seems you're thinking along the same lines here. ESME already stores some meta-information that the message has been "resent". What we could do is make it more explicit in the UI: - make it possible to resend manually, not via an automatic action - indicate explicitly on the timeline that a message has been resent (possibly include info who resent it) - create timelines of messages resent from your followers and from all followers (public). This alone would provide a lot of value, as it harnesses the collective filtering and streamlines it to avoid duplicates. In addition, one could also reply to an already resent message to add content.