Return-Path: X-Original-To: apmail-couchdb-marketing-archive@minotaur.apache.org Delivered-To: apmail-couchdb-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3DA7110B52 for ; Thu, 10 Apr 2014 12:55:31 +0000 (UTC) Received: (qmail 70733 invoked by uid 500); 10 Apr 2014 12:55:30 -0000 Delivered-To: apmail-couchdb-marketing-archive@couchdb.apache.org Received: (qmail 70621 invoked by uid 500); 10 Apr 2014 12:55:28 -0000 Mailing-List: contact marketing-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: marketing@couchdb.apache.org Delivered-To: mailing list marketing@couchdb.apache.org Received: (qmail 70404 invoked by uid 99); 10 Apr 2014 12:55:24 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Apr 2014 12:55:24 +0000 Received: from localhost (HELO mail-qg0-f41.google.com) (127.0.0.1) (smtp-auth username nslater, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Apr 2014 12:55:23 +0000 Received: by mail-qg0-f41.google.com with SMTP id z60so2262537qgd.28 for ; Thu, 10 Apr 2014 05:55:22 -0700 (PDT) X-Gm-Message-State: ALoCoQloojn7vM0hEj90LTLD+8ucxKUcaPbOn9BlepdoS6d7b/toN+3BNWfkC5cW6hj4Zh5wl0mm MIME-Version: 1.0 X-Received: by 10.140.87.151 with SMTP id r23mr18878401qgd.75.1397134522632; Thu, 10 Apr 2014 05:55:22 -0700 (PDT) Received: by 10.140.92.231 with HTTP; Thu, 10 Apr 2014 05:55:22 -0700 (PDT) X-Originating-IP: [87.151.166.208] In-Reply-To: References: Date: Thu, 10 Apr 2014 14:55:22 +0200 Message-ID: Subject: Re: Where to post on Google+ From: Noah Slater To: Alexander Shorin Cc: Noah Slater , "marketing@couchdb.apache.org" , Benoit Chesneau Content-Type: text/plain; charset=ISO-8859-1 What about just deleting our page? Have one place we post news? What's common practice? On 10 April 2014 13:25, Alexander Shorin wrote: > Imho, it's one of the awkward moment of G+. > > If you share something with only just the community, followers of your > page which aren't members of that community wouldn't receive > notification about your post. Use case: I'd like to receive news from > and about CouchDB, but I don't belongs to that community. So posting > from page account and resharing with community sounds reasonable from > point of cover all the followers. > > On other hand, if you following CouchDB page and you're member of > related community you'll receive duplicate notification, you'll see > duplicated posts on your home page as like as on Posts page of > CouchDB. Hopefully, this could be fixed via special "silent" circle. > > Things going crazy when you'd like to share something with multiple > communities: you'll have N similar posts on your page and someone's > too. Benoit knows how's that (: > > So, while this "design flaw" exists, imho, better follow the rule to > cover more audience as possible - from this point your actions are > reasonable. > > > -- > ,,,^..^,,, > > > On Thu, Apr 10, 2014 at 3:12 PM, Noah Slater wrote: >> Hi, >> >> I've been posting to both the CouchDB page *and* the CouchDB >> community. But if you look at the CouchDB page, that means things are >> showing up twice. >> >> https://plus.google.com/u/1/b/109226482722655790973/109226482722655790973/posts >> >> So I figure: just post to the CouchDB community. It looks like those >> things are pulled into the CouchDB page anyway. >> >> Can Alexander or Benoit confirm for me? >> >> Thanks, >> >> -- >> Noah Slater >> https://twitter.com/nslater -- Noah Slater https://twitter.com/nslater