Profile cover photo
Profile photo
Stacey Williams-Ng
174 followers
174 followers
About
Posts

Post has attachment
Writing children's books, contrary to popular belief, is not child's play.
Add a comment...

Post has attachment
Our new website makes it easy for #picturebook writers and illustrators to submit!
Add a comment...

Post has shared content
(Will I ever learn?)
Wow. Lots of great discussion re: the whole Extended Circles sharing dilemma. Nearly all sources I've found (including Google staff) say that using Extended Circles CAN share/force your posts into the Incoming streams of people who are not following you AND who have public follower counts on their profiles.

Also, if you want your post to be more easily reshared, use Public instead of Extended Circles. From Pooja Srinivas:

"If someone reshares something you've posted to Extended Circles, they will not be able to reshare it to public. The only options available would be specific circles/individuals, all circles, and Extended Circles. So if you want to make it easier for your posts to be reshared, post to Public instead of Extended Circles."

Some useful resources:

https://plus.google.com/113805478630918777008/posts/Di1myF9fxbg
(Updated version via Pooja Srinivas at Google)

https://plus.google.com/113117251731252114390/posts/TQy3ejQ6N5h
(via Mike Elgan, who says:

"The Extended circles button sends your post to all the people in your circles, plus all the people in their circles who have public follower counts on their profiles.")

http://ansonalex.com/wp-content/uploads/2011/07/Google-Plus-Stream-Update-Flowchart1.jpg
(via Jason Henke - sorry, G+ is still not letting me link to people)

http://crosscutcommunications.com/wp-content/uploads/2011/07/Extendedcircles-2-1024x625.jpg
(via Paul Fabretti)

http://www.google.com/support/profiles/bin/static.py?hl=en&page=guide.cs&guide=1257347&answer=1302427&rd=1
(via Google+ info & several referring sources)

Because of this, I have made my Circles private/hidden instead of public. This way, I won't have to worry about my Circles getting posts in their Incoming Streams they may not necessarily want. I am also going to refrain from using sharing by Extended Circles except on rare occasion.

Some people have suggest blocking as a way of cleaning up one's Incoming Stream. Here's info about Blocking in Google+:

http://www.google.com/support/+/bin/static.py?hl=en&page=guide.cs&guide=1347964&topic=1358051&answer=1047934&rd=1

http://www.google.com/support/chat/bin/answer.py?answer=161879
(via Rebecca Woodhead)

After reading the above, I'm not going to use blocking unless someone is really REALLY chatty in my Incoming stream. Hopefully Google will coming up with a better solution to all this confusion soon.

Thanks to all for your input! To see earlier discussion leading up to this one:

https://plus.google.com/115121110877145330939/posts/fCv5MuFeggC
https://plus.google.com/115121110877145330939/posts/M3SoByGNKGx
https://plus.google.com/115121110877145330939/posts/59P7UFEN1aQ
Add a comment...
Wait while more posts are being loaded
https://plus.google.com/+StaceyWilliamsNg
plus.google.com
crawl=CC-MAIN-2018-47
491050
application/http; msgtype=response
sha1:ZY6GO4FXEAM7N4WF56QPNUEPEKS2MP4N
<urn:uuid:48615630-a4ee-4a00-8e82-044046d21b4b>
2018-11-18T14:04:30Z
172.217.7.238
text/html
sha1:6DPCCM6ZRPUYY6W2TCVMJLJJIHVLMYN5
<urn:uuid:81c2ca4b-4dc0-4684-9af5-d3e213f16c67>
https://plus.google.com/+StaceyWilliamsNg
response
<urn:uuid:81772c5b-4a71-4788-843c-2e21ba9b846d>
isPartOf: CC-MAIN-2018-47
publisher: Common Crawl
description: Wide crawl of the web for November 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-138-129-164.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/