#gplusrefugees

fixato@libranet.de

For the #GPlusRefugees out there:


Filip H.F. "FiXato" Slagter - 2022-02-27 22:05:55 GMT

#SignalFlare: A reminder to follow me elsewhere if you want to stay in touch, as #JoinDiaspora will be going offline at the start of March:
You can follow me on:
- #Mastodon: @fixato@toot.cat https://toot.cat/@FiXato
- #Friendica: @fixato@libranet.de @Fixato . https://libranet.de/profile/fixato/
- Overview of other profiles (which needs updating..): https://contact.fixato.org/
- My #Gemini blog: gemini://fixato.org

#GPlus #GooglePlus #PlusPora #CheckIn #PlusPoraRefugee #PlusPoraRefugees #GooglePlusRefugee #GPlusRefugee #GPlusRefugees #FiXato #Plexodus #JoinDiaspora

dredmorbius@joindiaspora.com

G+ Migration Post Mortem: What went well, what went poorly, what are lessons learned?

We're now well into the post-Google+ period, and I'd like to open up the question of how things went.

I've got my own mental list of things which went well or poorly in the process, of the latter, many of which involve myself.

This is open to contributions and discussion.

Discussion here or at PlexodusReddit.

There's a Plexodus Wiki Post Mortem page open as well.

#Plexodus #GPlusRefugees #GooglePlus #PostMortem

dredmorbius@joindiaspora.com

Friends+Me Google+ Exporter can still access images & video

If you're like me, well, first, my deepest sympathies, but you've used F+MGE to capture your posts and other text content, but were saving images for later, only to be caught by the Google+ shutdown.

Turns out that googleusercontent.com is still serving up those images (this may be data that's harder for Google to remove), so you can still fetch media content through Google+ Exporter.

Hop on that now if you're interested.

#GooglePlus #GplusRefugees #Plexodus #DataExport #FriendsPlusMe

dredmorbius@joindiaspora.com

Archive Team are 59% through their stretch goal of archiving G+ Communities

"Googleplus2" a/k/a G2 is a project to archive all public G+ community content. This was a "stretch" goal of the Google+ archiving project.

The tracker here shows the full project, there are 81,270 or so work sets of 100 communities, and as of a few moments ago, the project was at 59% complete, with about 6 hours left to run at present rates.

The contents should appear at the Internet Archive in about a month or so, it'll take time to move it all there.

Tracker status below:

https://tracker.archiveteam.org/googleplus2/

#googleplus #gplusrefugees #plexodus #archiveTeam #internetArchive

dredmorbius@joindiaspora.com

I'm just sitting here watching the smaps go round and round...

The Archive Team Google+ project tracker is smoking.

https://tracker.archiveteam.org/googleplus/

And it's got to go faster.

Grab a Warrior and pitch in if you can!

(Got bandwidth, storage, CPU, and modest l33t ski1z? You can help!)

https://www.archiveteam.org/index.php?title=Warrior

#GooglePlus #GplusRefugees #Plexodus #ArchiveTeam #InternetArchive #GoogleMinus

dredmorbius@joindiaspora.com

A set of 604 curated "locally notable" G+ profiles

https://pastebin.com/raw/0Wh4BJah

This list comes from a set of contributions from +Eli Fennell's listing here:

https://plus.google.com/110619855408549015935/posts/XrZkNKam1Jo

Though not strictly-speaking "signal flares", I've submitted the profiles to the Internet Archive's Wayback machine (scripted via the "Save" URL) -- that part took about 90 seconds. Sorting out grabbing all the profile names and IDs from G+ HTML (and wrestling with local systems) a couple of hours.

A really good reason to pin a #signalflare post is that that pinned post WILL SHOW UP IN THE INTERNET ARCHIVE when saved.

(I'll schedule another save or few of this through April 2.)

This'd be a good set of folks to keep tabs on and through whom to find others.

I'll be adding this to the #PlexodusWiki Notable Names Database (NNDB) ... eventually:

https://social.antefriguserat.de/

https://pastebin.com/raw/0Wh4BJah

#GooglePlus #GplusRefugees #Plexodus #SignalFlare #GplusContacts

dredmorbius@joindiaspora.com

With the demise of Mr. Jingles, my plans and suggestions

I'd posted this to the rapidly-fading PLOOS, though some of the information applies here as well.

I'll be checking the Google+ Notifications page periodically, at least twice a day if possible. That's not as slick as the Notifications pane was, so expect slower responses to anything.

I'm trying to keep on top of the Google+ Mass Migration community, as well as the (much less active) Plexodus: The Beginning is Near community.

I've had a fair bit of personal stuff going on for the past few weeks which is making online time both less available and productive. My apologies.

The Plexodus Subreddit is an excellent place to get ongoing and post-sunset information. That would be on Google+, data migration (focusing much more on data import), contacts, where people are, and yes, yet more discussions about the past and future of social, online, and user-generated media.

https://old.reddit.com/r/plexodus

There's far too much updating to do at the #PlexodusWiki. So I'll try to tend to that garden as well:

https://social.antefriguserat.de

(It means "before it was cool", in Latin, if you're wondering.)

I'm still working on my future personal blog home. That'll be at GitLab, as a continuation of the Lair of the Id. Plan is to post original longer-form content there, then syndicate it elsewhere -- Mastodon, Diaspora, and the Lair subreddit (https://old.reddit.com/r/dredmorbius).

The New Lair blog will be: https://gitlab.com/dredmorbius/lair-of-the-id.git

For those of you who were Mirandans (or want to find out what the hell that was), there's still the /r/MKaTH and /r/MKaTS subreddits. I'm open to posting a bit more content there. MKaTH -- Miranda's Knitting and Tea House, is public, MKaTS -- Miranda's Knitting and Tea Society, is a related private forum:

https://old.reddit.com/r/MKaTH

For more on what that's about:

https://old.reddit.com/r/MKaTH/wiki/faq

There's also a more general Plusser's subreddit, /r/PLOOS:

https://old.reddit.com/r/ploos/

Otherwise, I'm posting at Mastodon, Diaspora, Tildes, Reddit, Hacker News, and a few other haunts, generally as "dredmorbius", as promised.


https://old.reddit.com/r/plexodus

#googleplus #GPlusRefugees #dreddit #plexodus #plexodusReddit #plexodusWiki

dredmorbius@joindiaspora.com

Google+ will be shut down on April 2, 2019

This is Google's official G+ shutdown announcement. Text in full:

Shutting down Google+ for consumer (personal) accounts on April 2, 2019

January 30, 2019

In December 2018, we announced our decision to shut down Google+ for consumers in April 2019 due to low usage and challenges involved in maintaining a successful product that meets consumers’ expectations. We want to thank you for being part of Google+ and provide next steps, including how to download your photos and other content.

On April 2nd, your Google+ account and any Google+ pages you created will be shut down and we will begin deleting content from consumer Google+ accounts. Photos and videos from Google+ in your Album Archive and your Google+ pages will also be deleted. You can download and save your content, just make sure to do so before April. Note that photos and videos backed up in Google Photos will not be deleted.

The process of deleting content from consumer Google+ accounts, Google+ Pages, and Album Archive will take a few months, and content may remain through this time. For example, users may still see parts of their Google+ account via activity log and some consumer Google+ content may remain visible to G Suite users until consumer Google+ is deleted.

As early as February 4th, you will no longer be able to create new Google+ profiles, pages, communities or events. See the full FAQ for more details and updates leading up to the shutdown.

If you’re a Google+ Community owner or moderator, you may download and save your data for your Google+ Community. Starting early March 2019, additional data will be available for download, including author, body, and photos for every community post in a public community. Learn more

If you sign in to sites and apps using the Google+ Sign-in button, these buttons will stop working in the coming weeks but in some cases may be replaced by a Google Sign-in button. You’ll still be able to sign in with your Google Account wherever you see Google Sign-in buttons. Learn more

If you’ve used Google+ for comments on your own or other sites, this feature will be removed from Blogger by February 4th and other sites by March 7th. All your Google+ comments on all sites will be deleted starting April 2, 2019. Learn more

If you’re a G Suite customer, Google+ for your G Suite account should remain active. Contact your G Suite administrator for more details. You can also expect a new look and new features soon. Learn more

If you're a developer using Google+ APIs or Google+ Sign-in, click here to see how this will impact you.

From all of us on the Google+ team, thank you for making Google+ such a special place. We are grateful for the talented group of artists, community builders, and thought leaders who made Google+ their home. It would not have been the same without your passion and dedication.

https://support.google.com/plus/answer/9195133

And note that buried FAQ link: https://support.google.com/plus/answer/9217723

#Google #GooglePlus #GplusRefugees #Plexodus

dredmorbius@joindiaspora.com

Yonatan Zunger on Free Speech and other online forum policy issues

...I have had to sit and make these tradeoffs, so please don't try to bullshit me by explaining how it's more complicated than we think. It is insanely complicated, one of the hardest things I've ever worked on, and I still know when I'm being bullshitted. Twitter chose to optimize for traffic at the expense of user experience. That's why GamerGate, that's why Trump, that's why Nazis....

-- Yonatan Zunger on Twitter (Unrolled thread)

As I'm going through my #GooglePlus contacts, updating notable names lists, and generally reviewing old posts and such -- that's the hazard of packing up and moving, it's not the putting of things in and out of boxes, but processing what they are that takes so damned long, and that's why hired professionals are so much faster, they don't know and don't care -- and am thinking about what makes Good and Bad platforms, and how to specifically articulate what is wrong with some that have turned up, well, there's this.

The accompanying Google+ thread was excellent as well, catch it whilst you can. Yes, it's been archived, but the Way Back Machine only captures a few comments from G+ posts, a long-standing issue. So most of those comments will be lost in time, like tears in the rain.

For those not aware: Zunger was the original chief architect of Google+, and oversaw many of both its design and policy decisions. This was a massive social network -- at least by registered profiles -- of over 3.3 billion accounts. And though its activity never quite met expectations or operator's claims, it was impressive. Yonatan knows whereof he speaks. He's seen these problems. At scale. He's moved on to other things, and from Google. He's quite busy. But damned if I wouldn't love to tap into his brain and unspool some of those lessons.

And I've got all kinds of ideas on how to specifically address the questions of free speech and free-speech maximalism, which does not in fact maximise access to free speech, online or otherwise.

The #DarcyProject should take heed. @Christian Buggedei ping

#Google #GooglePlus #GplusRefugees #Plexodus #socialMedia #freeSpeech #GamerGate #Twitter #

dredmorbius@joindiaspora.com

Plussers: Bryan Ruby's Massive Google+ Blogroll

A key concept of keeping communities intact or at least in contact is for prominent members to be readily findable.

Bryan Ruby has compiled a list of 189 significant contributors to Google+, with links to their blogs and (generally) Twitter feeds. That's posted to his own blog: "My Massive Google+ Blogroll".

I've filled in RSS/Atom feeds for all but a small handful of the entries (with a script -- I'm obsessive, but not that obsessive), and made that available in various formats:

  • OPML -- this can be imported directly into most feed-readers.
  • HTML -- for posting wherever.
  • Markdown -- in case you like that sort of thing.

The entries have also been added to the #PlexodusWiki G+NNDB (Google+ Notable Names Database), another repository of public contact information: Google+ Notable Names Database. We'll roll those in with the general categories over time. Descriptions and bios would be useful.

The script can be used on other blog lists as well, though it'll likely have to be adapted to different formats. It retrieves feeds based on either HTML metadata or typical locations used -- parsing that out is ... interesting. Processing is 189 records in about 4m40s. That could be sped up considerably with parallelisation.

#googlePlus #Plexodus #RSS #feeds #blogs #gplusRefugees

dredmorbius@joindiaspora.com

What Ails Google?

Rampant and largely uninformed speculation follows.

Seems to be a bit of an overshoot, but that's a possibility.

There's been speculation, some of it mine, that something large ails teh GOOG. What specifically that is or might be is hard to say.

How it is manifesting is somewhat clearer:

  • Google+ is being shut down.
  • The shutdown period was cut, without notice by 40%.
  • Google employee morale seems sharply down.
  • Google employee exits are noticeable, though whether or not they depart from trend is hard to say.
  • Communications from Google particularly regarding the Google+ sunset, are all but nonexistent.
  • Google are actively thwarting attempts by users (including myself) to share information about the G+ sunset.
  • As are Google TC and PE volunteer moderators at the Google+ Help community.

And quite probably more.

We got problems

I'm thinking of the types of issues which might affect companies. These are numerous.

  • Revenue shortfall, realised or forecast.
  • Major shift of business, realised or forecast.
  • Major changes to regulatory environments, realised or forecast.
  • Potential political shifts.
  • Internal power struggle.
  • Union activity.
  • Employee revolt at business practices or direction.
  • Loss of goodwill / brand equity.
  • Criminal investigation(s) or charge(s).
  • Civil lawsuit(s) or charges, possibly from customers, users, employees, governments/regulators, and/or shareholders.
  • Major competitor lawsuit.
  • Regulatory investigations or actions.
  • Legislative review or attention.
  • Discovery of internal fraud.
  • Discovery of external fraud.
  • Stock or debt-related malfeasance, internal or external.
  • Forecast changes to the investment, finance, or business landscape generally.
  • National / international finance or other investigations.
  • Unorganised but significant internal criminal or tortuous activity: smuggling, drugs, sexual harassment, child pornography, prostitution, espionage.
  • Same, but organised, that is, multiple parties, possibly above rank-and-file.
  • National security actions, accompanied by gag order.
  • Other legal actions, accompanied by gag order.
  • Major hacking or infiltration events, non-state actors.
  • Major hacking or infiltration events, state actors.
  • Infiltration by organised crime.
  • Infiltration by noncriminal non-state actors.
  • Infiltration by state actors.
  • Significant data breach, possibly ongoing.
  • Realisation of major core technological vulnerabilities in software, hardware, network, or other operational vulnerabilities, not readily addressed.
  • Death by a thousand cuts: multiple coinciding threats or attacks diverting executive attention.

What symptoms fit the patient?

Several of these are documented as being present -- employee dissatisfaction, possible unionisation, employee revolt, and numerous ongoing lawsuits (not uncommon for large organisations).

The competitor lawsuit is unlikely as that would be publicly filed, as would most civil lawsuits.

Criminal investigation(s) are possible, though unlikely.

The fraud potentials, as well as infiltration, hacking, and data breach possibilities would all require some form of timely public disclosure except in truly extraordinary circumstances.

Major technical vulnerabilities seem to me unlikely to be specific to Google itself, and would therefor likely include other companies acting in some similar fashion, unless they pertain to Google-specific, non-public codebases, hardware designs, or network architectures. Which is possible. I'm not aware of other companies which have clamped down as Google have, though I've also been largely focused on Google+ shutdown issues.

The political landscape is shifting in many ways in many places, with the ongoing capture of US government by Russian influences, Brexit, rising nationalism across numerous other nations, and the like. Which of these have specific impact on Google and Google+ is hard to say, though computational propaganda techniques are one possible aspect.

Massive revenue shortfall could give rise to major internal disruptions, though I don't see it resulting in the specific actions being taken as regards Google+, including the active frustration of data export and organisation amongst users. All of these issues would have material business impacts and have to be reported on financial statements. I'm aware of no such reports, though I've not yet investigated.

This suggests something possibly central to Google+ itself, and involving data or information on the platform of a nature sufficiently diffuse to attempt thwarting most export of same, and or a suspected adversarial user network, again, on the platform. That seems a bit of a stretch, even to me, but I'll present it as a possible cause.

The various crime / tortuous activity angles may be at play, but would tend not to produce what seems to have been at least a three-month, if not an eleven month (March 2018 - January 2019) and ongoing concern, without any public announcement of the nature of the problem. Most criminal investigations take a few weeks, possibly a few months, not the better part of a year. This could be an outlier, though that's low likelihoood.

(I'll note that last year's mysterious investigations and shutdowns at a New Mexico Sunspot Solar Observatory was tied to child pornography. That resulted in an eleven day sealing of the facility, though presumably the janitor involved was not operating at Google scale. There was much speculation over other possible natures, virtually all wrong.)

Regulatory and legislative actions are also typically fairly public, and it seems unlikely that something massive and wide-reaching would not somehow be public.

That leaves various internal struggles, ongoing major investigations of a fraud, criminal, tortuous, or national security nature, major infiltration, major Google-specific technical vulnerability, major non-Google-specific technical vulnerability, and death-by-a-thousand-cuts possibilities as leading suspects from my list.

I'll note that there's nothing obvious in the Google+ data I've been compiling that stands out as problematic with the network itself.

There's the impact on Google employee morale. Generally an external attack tends to increase morale. It's betrayal from within, and most especially by leadership, which tends to decrease it. Which points at a Google-specific, and likely leadership or management issue. A forecast revenue decline could also be at play -- this would manifest as workforce reductions and lowered morale, though not so much as the utter dysfunction which seems to be accompanying the Google+ shutdown.

But I'm just a space alien cat staring at tea leaves. What do I know?

#google #googleplus #gplusRefugees #staringAtTeaLeaves

dredmorbius@joindiaspora.com

So, how big is all of Google+ Communities anyway?

Not how many communities (8 million and a skosh). Not how many actual users (a few tens of millions). But posts and text.

(I'm skipping the boring stuff like images, which blow things up a lot, but we can get to that later if you'd like.)

Suppose someone walked up to you and asked if you'd like a full copy of the Google+ Communities post archive. A few thoughts might occur to you, one being "where would I put that?"

I mean, Google, GOOGLE SCALE. Hyuuge!! Right?

Maybe ... not. At least by modern hardware standards

So, back in mid-December I sampled 36,000 randomly-selected G+ communities and got some information on them -- name, description, member count. And the ten most recent posts, along with the elapsed date range between the newest and oldest posts. So what does that give us?

First off, only 4,465 of the 36,000 communities had a full ten posts in their history. The others either never had more than 9 posts submitted, or had them purged (user deletion, spam, other actions, stuff). I'll treat any community with fewer than 10 posts as effectively zero, to simplify things.

The elapsed time gives me a post rate, which is how many posts are submitted over any given time interval. Weeks become handy, and the rate is about 1 post/wk, on average (1.0046/wk, if you want to be precise).

My 36k sample represents about 1 of every 223 actual communities, so we can multiply 4,465 by 223 and get ... about a million (996,000).

Gee, about a million, and about a post a week, so a million posts a week? Yeah, but let's be precise:

You have: 996000 * 1.0046
You want:
        Definition: 1000581.6

Yeah, that's pretty much a million posts/wk.

G+ Communities launched in December, 2012, and will be shut down in April, 2019. I'll simplify again and take Jan 1 2013 - December 31 2018, or six years of 52 weeks: 312 million posts.

But how long is a post?

I'm punting here (though ... actually I do have some data, come to think), and took a quick look at #Discovfefe, I mean, Google+ Discover. Grabbing a random few posts, they tend to run about 20-40 words typically, with some of the longer ones weighing in at 100 - 450 words. Mostly, though, about Tweet sized, which probably reflects a number of factors. Call it 250 bytes.

312 million posts * 250 bytes: 78 GB.

Yes: "Google-scale" source text for Google+ Communities is probably under 100 GB total storage.

Caveats, civet cats, and all that jazz

The short-cuts I took above probably overstate the storage estimate -- Communities are created over time, they did not all exist for the entire life of G+ communities, and posting rates may have changed. The "elapsed" interval also doesn't count communities which have stopped generating new posts.

The page weight is considerably higher. After you add in all the HTML, CSS, and Javascript, a G+ article is about 800 kB of data, and additional image assets are more. That balloons the archive size out to about 250 TB or so.

And it's likely that a fair amount of data was submitted but has been removed -- spam, deleted accounts, and the like.

And even if you're only counting text, there's some post-level metadata: the author, date, communityID, and related bits, which pad out the data requirements slightly. These numbers are rough. But the purpose is to give an approximate sense of the scale.

And photos. About 30% of posts seem to have an image attached. G+ has a max size I'd need to look up -- 2120 x 1192, apparent. But you're looking at about 93 million images or so, roughly. Some can be quite large. This beauty (and it is pretty) is 7.4 MB, at about 4k x 6k pixels, 24 MP raw. And this shot of Tulsi Gabbard as a link hero is about 1060x600 pixels.

SanDisk have one of the better image size / storage capacity references I've seen. In 12MP format (3k x 4k pixels), 1 GB can hold about 238 images, 128 GB, over 30,000.

Put it on my bill, said the duck

How much did Google pay for all of this?

No, really: How much did Google pay for all of this?

Because one aspect of this whole fiasco I kind of don't begrudge is that a handful of us got a fairly nice playground for a while. That it's getting shuttered wasn't a huge surprise. How it's being shuttered .... Well, I've written about that elsewhere.

Now, if only I knew someone who might be able to tell me the answer....

#google #socialMedia #capacityPlanning #gPlusRefugees

dredmorbius@joindiaspora.com

Google shut down the Google+ Moderators Community six weeks ago and never bothered to tell anyone

I've been trying to reach out to G+ Communities especially over the course of the shutdown, a process I'd found frustrating. There are few mechanisms for directly contacting community moderators (unlike, say Reddits "message moderators" feature), and there are few forums for G+ Community owners and moderators to get and exchange information.

One of those is the Google+ Moderators community itself, the official Google channel for mods.

I've been posting and commenting there occasionally over the course of the shutdown particularly my statistical analyses of Community size and activity. There'd been little if any response.

I thought it was simply that moderators on Google+ are apathetic. It's not that.

Six weeks ago, without informing anyone, Google effectively shut down the forum. Posts are "HfR", held for review, and unless they're approved by a moderator, they won't appear for other users. The submitter does see their posts in the community and has no indication that the post has not been submitted.

You can confirm this by viewing the community from an Incognito / unauthenticated session. Doing that just now, I realised that the forum had seen no new activity since December 10, 2018.

The two screenshots here show this. The two-column view with the visible "Sign In" button at top right, shows an Incognito view, with the most recent posts being dated 6 weeks ago. The three-column view is what I see logged in as "Edward Morbius", with several posts I've submitted in the weeks since then. I can see those. Nobody else can.

Incognito view of Google+ Moderators community

Incognito

Logged-in view of Google+ Moderators community

Logged-in

And if anyone else has posted to the community in the meantime, nobody but them can see those posts either.

This is not only extremely disrespectful and poor business practice, but it's straight up low class.

Google appear to be falling apart.

In other news: You cannot rely on the fact that posts to Google+ will be visible to other users, most especially not in Google's own Communities and spaces. Google are systematically dismantling the ability for users themselves to be informed on Google+.

If you're not using an off-Google channel for information already, start doing so NOW.

Again: there is a subreddit available at https://reddit.com/r/plexodus, devoted to the G+ exodus, run by me. You're strongly encouraged to use this. There are also /r/googleplus and /r/google, run by others, or other communities can be created. Please join one or more of these.

We have and will link other sites as well, and maintain a list of exodus communities.

The unofficial G+ Owners and Moderators Community does seem to be reliably available presently.

#google #googlePlus #plexodus #gplusRefugees

dredmorbius@joindiaspora.com

G+ Communities: Significant and Recent Activity

We're continuing to get a sense of G+ Communities and how many of these are significant, active, and have some sense of vitality.

One metric is to look by both size and recent activity.

G+ Public Communities with Recent Activity

Members Week Month
1,000 28,823 39,301
100 63,874 105,166

Members is the reported membership of the community on its Google+ landing page. Comparison is greater than or equals.

Recency is assessed as the sampling time minus the most recent post activity, both expressed as Unix timestamps (seconds from 1970-01-01:00:00:00). Week is activity within 86000 * 7 seconds, Month is activity within 86000 * 31 seconds. Comparison is less than or equals.

From previous analysis, it's likely that only 10-20%, generously, of these communities have substantive interaction between users, as opposed to other activity, including spam or link-drops. We have not investigated this dataset yet to assess this characteristic.

Still, that would leave about 3,000 - 6,000 communities of 1,000+ members with weekly or better activity, and 4,000 - 8,000 with monthly activity, and 6k - 12k and 11k - 22k of 100+ members respectively.

There is little relationship between active engagement, measured by plus-one, comment, and reshare activity, and community size. While smaller communities (especially below 100 members) are far more likely to have no activity or no recent activity, the distribution of significant recent activity is fairly uniform across a very broad range of community sizes. On a per member engagement level, the sweet spot appears to be roughly 100 - 5,000 members, though we need to investigate this further.

Very large G+ communities are frequently not particularly engaged. See the WhatsApp Community (6.8 million members) as an example. Interestingly, this doesn't appear in a G+ Community search for "WhatsApp".

Gory Details

URLs for 8,107,099 Google+ Communities were read, with 3,559 found to be deleted when accessed, and 8,103,540 read successfully yielding data.

There were 7,303,513 public, and 800,382 private communities (9.877% private). Membership and post activity are available only for public communities.

Membership status was open ("Join") for 3,689,488 (45.51%), and closed ("Ask to join") for 4,414,407 (54.45%) communities, status was unavailable for 3,204 (0.04%) communities.

Membership percentiles (preliminary):

Memb. Policy 1% 5% 10% 25% 33% 50% 67% 75% 90% 95% 99%
All 0 1 1 1 1 1 4 8 40 110 859
"Join" 0 1 1 1 1 1 1 2 17 50 380
"Ask" 0 1 1 1 1 3 7 13 58 158 1253

(NB: we want to confirm that the Join and Ask to join stats are correct as previous analysis showed higher membership for open-membership sites, though that sample excluded the very largest G+ communities. It's possible sense is inverted. Spot checks say we're not fouling this one up.)

Source

Web-scraped query of 8,107,099 Google+ Community landing pages between 5 Jan and 6 Jan, 2019.

#googlePlus #communities #stats #rStats #plexodus #gplusRefugees

dredmorbius@joindiaspora.com

Failure of Communication: No mention of imminent Google+ shutdown on G+ About or App pages

Google's failures of communication on the G+ shutdown are staggering. Crickets, after initially promising:

Over the coming months, we will provide consumers with additional information, including ways they can download and migrate their data.

And on December 12, 2018:

over the coming months we will provide users with information to help them migrate off of G+.

This extends to the Google+ About page and Google+ App page in the Android store.

Here's today's Internet Archive grab of the Google+ About page. "Discover amazing things."

But not a mention that the service will be shut down in 111 days.

Screenshot of G+ About page

Here's today's Internet Archive grab of the G+ App on the Android store.

Screenshot of G+ App page

Though we've got to give Jerome Williams props for his one-star review:

Jerome Williams

December 25, 2018

Do not waste your money on this game, it is not what it used to be. At one point, this game use to be very active with frequent updates, new content, and events. Now it rarely gets new content and when it does, it's just old content that has been recolored. The one moderator that keeps the game running, only makes decisions that will benefit Spacetime Studios rather than the community it has built. Not to mention, the extreme unprofessionalism with the way he communicates with the community.

Terrible gameplay, indeed.

Though we'll note another metric of G+ uptake: 5.5 million downloads.

#googlePlus #GplusRefugees #google #plexodus


Originally published at #PlexodusReddit: https://old.reddit.com/r/plexodus/comments/ae5lsv/failure_of_communication_no_mention_of_imminent/

dredmorbius@joindiaspora.com

Plexodus 3 Month Status Update

I'm putting this update out a week early, mostly as things are moving swiftly and I've been busy.

Covered here:

  • Make your final or interim future choices NOW and announce them.
  • I switched recommendations for data export to the Friends+Me Google+ Exporter. It works, it's here, and it's proven.
  • Think of moving this discussion off G+ in a month or two.
  • Google API shutdown starts January 27, completes March 7.
  • 127 days, or less, until Google+ is shut down.

Make your final or interim future choices NOW and announce them.

If you've been delaying making a decision on where to go after G+ is gone, you are now out of time. Make a decision NOW. I recommend picking a platform that is available now, that works now, and that addresses your needs, if not all your wants.

Pay attention to bones, not skin. Strong houses are build on solid foundations: established technology, reliable and proven leadership, a healthy community, and solid principles. New or not-yet-released platforms are an extremely high risk. If you're looking at a Community move, mailing lists, or Yahoo or Google Groups are excellent interim choices. Reddit and Groups.io might also make the cut.

I'm a fan of federated platforms, but these may not be a match for all others. Diaspora, Friendica, and Mastodon are especially reliable at this point. The first two offer much of what Google+ does, Mastodon is a microblogging platform similar to Twitter. For maintaining a reachable presence these are excellent choices.

For others, blogs or major social media platforms may well be your best options. They may have issues, but are a known quantity with established communities. Consider a beachhead on one or more federated platforms, cross-posting or syndicating your content, as a trial run. Take actions to keep your future options open.

I have changed my recommendations for data export: Use the Friends+Me Google+ Exporter if possible. It works, it's here, and it's proven.

Google Data Takeout (GDT) does not work for the purposes of migrating from Google+ to another platform for most users. There are attempts to work with Google on this, they've proceeded slowly at best and there has been NO official communication, or even indication to Google+ Top Contributors and Product Experts serving as the Google+ Help community moderation team as to when such announcements might be made.

My initial estimate was that if Google did not respond by the two-month mark, we'd likely be on our own, and that very much appears to be the case.

You'll be far more likely to succeed in exports using F+MGE.

https://blog.friendsplus.me/export-google-plus-feeds-45926c925891?gi=8990ce9d30d0

What this does is export personal content and communities, directly imports to Wordpress or Blogger, with other targets pending, as well as future incremental updates to that archive. It does not yet have a photos exporter, but I've been in touch with the developer who is working on that.

F+MGE does not and will not support mobile migrations -- users with only mobile devices and no desktop or laptop system. More below.

If you have made a GDT and successfully converted it, you may be able to ignore this advice, though again, F+MGE does incremental updates.

(We're discussing a similar and official recommendation at G+MM as well.)

Mobile-only user data migration

For now, our suggestions are:

  • Borrow or acces a desktop or laptop system to migrate your data, if possible. Libraries may offer laptops to borrow or rent, as may other services.
  • Utilise a server- or cloud-based tool. We're aware of one though it's not yet fully polished.
  • Look for sites which offer direct import of G+ content. These will likely rely on G+ APIs and may not be available after March 7, or as soon as January 27.

We'll provide more information as it's available.

Think of moving discussions off G+ within the next month or two.

G+MM, P:TBiN, and all other Google Communities and content will very likely disappear on the April 2019 shutdown, presumably at the end of the month, although even this is not clear.

The best alternate space I have to offer is #PlexodusReddit:
https://old.reddit.com/r/plexodus

I've been posting content there, much of it from P:TBiN and G+MM, some strictly to the Reddit. Discussions there will survive, discussions here will not. I've yet to decide if I'll close comments here or not, but that's also likely at some point in February or March.

Google API shutdown starts January 27, completes March 7.

That's not a G+ shutdown, but it will affect third-party apps, some websites, and quite probably other tools at least temporarily, including possibly Google tools. Expect to start seeing glitches.

F+MGE does NOT use the API and will NOT be affected by this. Other archival tools, including some mobile-friendly options, will be.

Here's your Exodus Schedule for 2019

January

  • Provide updated status, plans, goals.
  • Commit to new platform(s).
  • Create a full Google+ data archive.
  • Create new accounts as needed.
  • Update your and community members' contact information.
  • Provide breadcrumbs, hashtags, and other discovery beacons.

February

  • Provide updated status, plans, goals.
  • No later than now declare new platform(s) live alpha.
  • Direct Google+ members to new services.
  • Deprecate Google+ services.
  • Publicise new location(s).
  • Update your and community members' contact information.
  • Select material for import.
  • Perform necessary edits and modifications.
  • Import and assess data.
  • Provide breadcrumbs, hashtags, and other discovery beacons.

March

  • Provide updated status, plans, goals.
  • No later than now declare new platform(s) live beta.
  • Direct Google+ members to new services.
  • Deprecate use of Google+ stream / communities, close comments.
  • Publicise new location(s).
  • Import and assess data.
  • Continue content edits and modifications as needed.
  • Update your and community members' contact information.
  • Provide breadcrumbs, hashtags, and other discovery beacons.

April

  • Provide updated status, plans, goals.
  • Update your and community members' contact information.
  • No later than now declare new platform(s) live primary.
  • Disable updates to Google+ services if possible (e.g., no comments, no posts).
  • Directly contact missing members, reach out through members.
  • Provide breadcrumbs, hashtags, and other discovery beacons.
  • Publicise new location(s).
  • 30 April: Presumed public Google+ shutdown date.

May

  • Provide updated status, plans, goals.
  • Direct Google+ members to new services.
  • Provide breadcrumbs, hashtags, and other discovery beacons.
  • Directly contact missing members, reach out through members.
  • Publicise new location(s).
  • Assess content integrity.
  • Assess community integrity.
  • Address content / community as necessary.

127 days, or less, until Google+ is shut down.

Google changed plans without warning once. They may well do it again.

#plexodus #googleplus #gplusrefugees #plexodusReddit


Originally posted to #PlexodusReddit: https://old.reddit.com/r/plexodus/comments/ac89wl/plexodus_3_month_status_update/