#gplusrefugees

dredmorbius@joindiaspora.com

Signal Flare

In the event you've missed it, I'm Edward Morbius at Google+, and you can find my Forwarding Address post, listing this Diaspora profile, there.

Additionally, you can find all your Space Alien Cat needs served at:

Sites I will not use

I am not:

  • "dredmorbius" on Twitter
  • "dredmorbius" at ZeroHedge
  • Anything on Facebook.

Organising the Exodus on G+

See the following communities:

#signalflare #gplusRefugees #googleplus #plexodus

dredmorbius@joindiaspora.com

G+ Communities Activity Analysis: It's the Posts, Stupid

Over the past few weeks I've been ploughing through a web-scraping pull of the landing pages of 36,000 randomly-selected G+ Communities conducted 20-21 Dec 2018. I've been seeking answers to a few questions:

  • How many G+ Communities are there? (A: 8.1 million, growing at a net of about 1%/month.)
  • How large are they? (A: For communities w/ >0 members: Median size 2, mean about 90, 95%ile: 113, 99%ile: 837)
  • How many are recently active? (A: Observed: <1m: 1, <1h: 29, <1d: 164, <1w: 310, <1mo: 639, <6mo: 1286. Actual is ~223 * observed, so ~ 142,497 between 1 week and 1 month, a total of ~255,800 active within the past month.)
  • How many G+ users are present and active? (A: Can't say.)
  • What characteristics seem to distinguish active communities? (A: Comments)
  • How do you find active communities? (A: See below.)

I'm still working with the data, but the plot above seems to tell a very significant story.

An explanation of what is being shown here:

  • This is a plot grid showing the relationship between multiple variables, a standard R graphics output.
  • Data are from G+ communities with more than 10 members. This removes some low-membership noise without changing fundamental data relationships.
  • All data are plotted as log10 values, that is logarithm base ten of the observed value. Actual data range from ~0.01 (-2 as scaled) to ~100,000 (5 as scaled).
  • Selected fields are members (community membership), posts/wk, plus-ones/wk, comments/wk, reshares/wk, and most recent activity in seconds, as "members", "post_wk", "plus_wk", "com_wk", "share_wk", and "recent_sec", respectively.

Members tells us how many profiles are subscribed to a community.

The activity/wk values give us a measure of activity. From the scraped pages, there are up to ten posts visible, representing surviving and recent posts on communities. Only 4,500 of the 36,000 communities sampled have a full 10-post history, and about half have no visible posts. Since this gives us at best a very partial view of community activity, I instead computed the number of observed activities over the elapsed time interval, expressed as activity/wk, for posts, plus-ones, comments, and reshares. In aggregate, the large observation count should make these values robust.

The recent activity is the time between the start of the data pull and the most recently-visible post. This ranged from about 2 minutes to the first communities created in December 2012. There's a sharp discontinuity about 160 weeks prior to the pull (late November, 2015), which seems to reflect some sort of either purge of old, or creation of new, communities. I'd be interested in any history of this that people are aware of. The relationship of recency to other variables is inverted, so recent activity is less frequent, but also generally higher.

The plots use a partially-transparent symbol such that more observations produce darker regions. It's actually mostly the lighter regions which are of more interest -- these are the high-activity communities.

That's the background.

Graph interpretation

Reading across the top or down the right of the graphic we have relationships between members and other variables. There is a positive relationship (more members == more activity, or more recent activity), but it's ... pretty scattershot. If you look at the 4th plot from left, members vs. comments/wk, and follow the line down from 2 (~100 comments/wk), we seek that there are datapoints from '1' to '5' on the members scale -- that's 10 - 100,000 members. Having lots of members does not necessarily get you more commenting activity.

Similar patterns are seen for other relationships. For recency, 10^4^ seconds (about 2.2 hours) activity is found across all membership classes. 100+ reshares ('2' as scaled), 100+ pluses, and 100+ posts, similarly.

If we bump over one column to the right, for plus_wk, the story changes. The plot is far more compact and linear. If you post 100x weekly, you get ... reasonably close to 100 plus-ones (a bit over) per week. Similarly comments and reshares. And for recency, virtually all 100+ posts/wk communities have activity within 10^5^ seconds -- about 1.15 days.

For causality, I'd tend to attribute posts rather than other activity (comments, plusses, comments), as you need posts in order to have other activity occurring. This is a reiteration of an observation I'd made long ago about Google+: The basic unit of interaction is the post, not communities, collections, or other units. That is, it is on a post with traction and engagement that further activities occur.

If you want an active community, post content, reasonably frequently.

How do you find active Communities?

This has been a major frustration as I've been trying to reach out to and determine where community activity is. What I'm leaning toward is **use G+ search with filters for in:community and after:<date>. A date about 1 week to 1 month ago should be appropriate. For finding any activity, a fairly generic non-stopword (something that's filtered out of search, like "the" or "a") typically works well. For English, "this" is often a good choice.

What other characteristics are there?

I'm limited by the information I can access from Communities. In general, these are:

  • Community ID
  • Community URL
  • Name
  • Description
  • Membership status (public vs. private) (about 91%/9%).
  • Members (for public communities only)
  • Membership policy ("Join" vs. "Ask to join) (about 55%/45%).
  • "About" text -- a long community description
  • "Links". Any linked URLs, with URL and name.
  • "Classifications". Any indicated filters within the community.
  • Posts: up to 10 recent and surviving posts.
  • Post activities: plus ones, reshares, and comments.
  • Post properties: author, date, is-pinned status, attachments, photos, photo description.
  • Post contents: text of actual posts.
  • Comment contents: text of actual comments.

What is not available are:

  • Community creation date.
  • Membership lists.
  • Moderator lists.
  • Deep community content (though this might be further scraped).
  • Content that's been deleted by the author, removed by moderators, or by G+ filters or abuse systems.

We might be able to conduct some analysis based on the language and topics of communities.

Informally:

  • Increased membership doesn't buy much buy way of more or more recent activity, especially above about 100 members, but does tend to sharply reduce the amount of no-post / no-activity communities.
  • Requiring "ask to join" seems to sharply limit community size. About half of communities from 0-9 members have "Ask to join" policy. This is about 1/3 for 100+ member communities.
  • Of engagements, reshares seem to be the least common. People will happily +1 or comment, but reshare (very) roughly 1/10 as often.
  • There are numerous languages present, including Arabic, Japanese, Korean, Malay/Indonesian, Thai, Vietnamese, Arabic, Hebrew, Spanish, Russian/Cyrillic, and more.
  • Popular communities tend to be focused around celebrities, photography, religious, or technology topics.
  • There are a large number of porn and sex-related communities, though these seem frequently empty, and in many cases have no visible activity, suggesting they were purged. Many of these have large memberships but no activity.
  • It appears that there is a fall-off in per-member engagement for groups above about 2,000 - 3,000 members. That is, looking at comments/member-week and similar measures, high values above the low-to-zero-engagement baseline fall off almost completely. This does not appear to be a sampling artifact, though this requires further investigation.

Sampling methods mean that large G+ communities are poorly represented. The sample draws about 1:223 communities, and correspondingly there is only one community represented from about the top-200 size class, weighing in at 291,025 members. Analysis of very large communities should be based on a dedicated list of these. I plan to do this shortly.

What this is not: The analysis is not claiming G+ communities activity or engagement is higher than or lower than other online communities. I've no basis on which to make such claims (though data on this would be of interest). The answers sought simply concern properties and characteristics of observable communities. I do suspect that the lessons here are fairly globally applicable, particularly as concerns the relationships between post and other activity, and the maximum size of cohesive communities.

Methods

Community lists are available from Google+ sitemaps, listed at https://plus.google.com/robots.txt. The 100 community sitemaps were pulled, listing 8,055,611 communities. This is about a 1% increase since an earlier analysis in November based on 12,000 communities.

A random seed was used to pre-filter about a 2% sample of candidate communities, which were sorted randomly and the first 36,000 records saved as the sample. This two-pass method is significantly faster than sorting the entire set. The 36,000 observations is 1:223.76697 of all extant communities.

Testing against the earlier 12,000 sample set, we would expect about 12,000 / 223.76697, or 53.627218 communities to be in common between the two samples. The actual match is 53 communities in common. This test of sample validity succeeded.

The community homepages were retrieved using curl, saving both the HTML and the HEAD request. The download took ~16 hours.

An error caused 8 retrieved records to be deleted. These were re-downloaded approximately 24h after the initial data pull. Influence on results is negligible.

Of the 36,000 communities, 13 were no longer retrievable (HTTP 302 errors) when fetched. This suggests a community deletion rate of about 4,348/day, or 132,000/mo. Note that with a net increase of 1% over a month, the raw creation rate is even higher.

Data extraction from raw HTML was performed using the html-xml-utils package, notably hxextract. This took ~18 hours over all 36,000 files. Parsing HTML DOMs, especially repeatedly, is slow work.

Further data massaging was conducted in awk to produce a 35,986 record CSV file fed to R for data analysis and graphing.

Further planned activities

As noted:

  • There is more analysis forthcoming, including CAN HAZ MOAR GRAFFIX.
  • Data processing needs validation, though it smells pretty good.
  • A large-group analysis based on CircleCount's April 2016 (last available data) set of top-200 G+ communities is planned.
  • Further thoughts on what to look at and questions to explore are appreciated.

#googlePlus #gplusRefugees #RStats #dataVis #statistics #socialMedia

dredmorbius@joindiaspora.com

Announcing G+MM AMA: Cake.co founder Chris MacAskill, Thursday 1 November 2018 at 5 pm US/Eastern

Chris MacAskill, has agreed to participate in an AMA on G+MM at 9 PM UCT (5 PM US/Eastern, 2 PM US/Pacific), on Thursday 1 November 2018, in the Google+ Mass Migration community on Google+.

Cake.co is a topic-centered microblogging service with excellent image support. For a good overview, see: "Welcome to Cake, Google+ refugees! Here’s how to get started using Cake".

This is the third in a series of AMAs, we have other guests invited and candidates and contacts are welcomed!

Guidelines, requests, scheduled AMAs, and more:
https://social.antefriguserat.de/index.php/Ask_Me_Anything

(Also in the G+MM sidebar links.)

#googleplus #gmmAmas #ama #gplusrefugees #gmm #plexodus #CakeCo

https://plus.google.com/communities/112164273001338979772

dredmorbius@joindiaspora.com

AMA: Hello, my name is Jason and I am the author of Socialhome. Ask me Anything!

I would describe Socialhome as a social networking server with rich profiles. I kind of see it as a cross between Twitter, Tumblr and Pinterest. You can do statuses like Twitter, longer form posts like Tumblr and it has the visual layout more like Pinterest.

At Google+ now: https://plus.google.com/+JasonRobinsonJaywink/posts/aeHxmc6tZAR

#ama #googleplus #socialhome #gplusrefugees

dredmorbius@joindiaspora.com

Current G+MM AMA status

Colour-coding[1]:

  • Red: Not yet contacted
  • Yellow: Attempting, no address
  • Blue: Contacted
  • Green: Booked/scheduled.

Solid have replied (within minutes).

Google have not.

table


Notes:

1. I'm aware of R-G blindness. The coding is additional signal to the displayed information, not required ;-)

#googleplus #gplusrefugees #gmm #ama

https://social.antefriguserat.de/index.php/Ask_Me_Anything#Requested_AMA_subjects_.2F_topics
Photo

dredmorbius@joindiaspora.com

Announcing G+MM AMA: Socialhome creator Jason "jaywink" Robinson, Tuesday 30 October 3pm US/Eastern

Jason Robinson, the creator of the Socialhome federated social networking server , has agreed to participate in an AMA on G+MM at 8pm UCT (3PM US/Eastern, 12 noon US/Pacific), on Tuesday 30 October 2018, in the Google+ Mass Migration community on Google+.

Socialhome is similar to a Diaspora or Mastodon server, but with a different UI. Unlike Diaspora or Mastodon it will speak multiple protocols so will simultaneously be able to talk to any other server that talks Diaspora or ActivityPub protocols. It's still in early alpha state.

This is the second in a series of AMAs, we have other guests invited and candidates and contacts are welcomed!

Guidelines, requests, scheduled AMAs, and more:
https://social.antefriguserat.de/index.php/Ask_Me_Anything

(Also in the G+MM sidebar links.)

#googleplus #gmmAmas #ama #mastodon #gplusrefugees #gmm #plexodus

https://plus.google.com/communities/112164273001338979772

dredmorbius@joindiaspora.com

A reminder: REQUEST JSON FORMAT for Google Data Takeout

Google HTML is absolutely worthless.

The instructions don't make this clear, but you're going to see this advice repeated repeatedly and repetitiously. With great frequency. Repeatedly.

Distracted JSON

REQUEST JSON FORMAT for Google Data Takeout

Why? Because the JSON format can be used by tools for extraction and import. Tim Berners-Lee is building one for Solid, there will be others.
https://github.com/solid/solid-takeout-import (not yet usable, but in process).

REQUEST JSON FORMAT for Google Data Takeout

Why? Because the JSON format contains additional, useful, and critical fields for extraction and import to other sites and tools.

REQUEST JSON FORMAT for Google Data Takeout

Why? Because Google's generated HTML is an ugly bastard stepchild of HTML that's not actually useful even as HTML.

REQUEST JSON FORMAT for Google Data Takeout

Why? Because you'll give yourself far more options and far fewer headaches down the road.

REQUEST JSON FORMAT for Google Data Takeout

Why? Because even if you can't make heads or tails of the output, the tools likely to be developed for intake to where you want the data to go will.

REQUEST JSON FORMAT for Google Data Takeout

Why? Because your friendly neighborhood hackers (and Space Alien Cats) can hack something together using 'jq' and 'awk' (or Python, Ruby, Perl, Go, ...) if all else fails.

REQUEST JSON FORMAT for Google Data Takeout

Why? Because it's what you actually want.

REQUEST JSON FORMAT for Google Data Takeout

REQUEST JSON FORMAT for Google Data Takeout

REQUEST JSON FORMAT for Google Data Takeout

PS: We now know the boyfriend's name: JSON.

#googleplus #gplusrefugees #JustSayJSON #GoogleTakeOut #DataMigration

https://plus.google.com/104092656004159577193/posts/itsbPERaapX

dredmorbius@joindiaspora.com

Announcing: G+MM AMAs

The Google+ Mass Migration forum (at G+) will be running a set of AMAs -- ask me anything interviews -- focusing on sites and platforms under consideration by present G+ members seeking to move elsewhere.

We're compiling a set of candidates, the first invitations have been sent out and accepted!!

Eugen Rochko, (@Gargron@mastodon.social), the creator of the Mastodon microblogging platform, has agreed to participate in an AMA on G+MM at 5pm Central European Time (1PM US/Eastern, 10AM US/Pacific), on Monday 22 October 2018.

Mastodon is a distributed, federated social network that forms part of the Fediverse, an interconnected and decentralized network of independently operated servers.

Mastodon has microblogging features similar to Twitter. Each user is a member of a specific Mastodon server, known as an "instance" of the software, but can connect and communicate with users on other instances as well. Users post short messages called "toots" for others to see, subject to the adjustable privacy settings of the user and their particular instance. The platform includes artists, writers and entrepreneurs such as Chuck Wendig, John Scalzi, Melanie Gillman and later John O'Nolan joined in, while Mastodon had reached 1 million accounts on December 1, 2017.

(from Wikipedia)

#googleplus #gmmAmas #ama #mastodon #gplusrefugees

dredmorbius@joindiaspora.com

Status: Updates, plans, news

  • There's a subreddit for the Plexodus, r/Plexodus. It's an off-site hub for discussion and information, in addition to the G+MM community on G+.
  • I'm planning on contacting other G+ community owners and members over the next few days. Steeling up to do this. Much appreciate others doing likewise. Intent is to direct them to Google+ Mass Migration.
  • The #PlexodusWiki got hit by spammers last night, so I've got to unwind some damage and learn the abuse / spam tools there. @Thom Thomas if you have any experience that'd be a huge help. Comment here or email dredmorbius protonmail com
  • Quite a bit of activity on G+MM as well as moderator discussions on direction. No big shifts, but some re-eval and focusing. This is all evolving quickly.
  • The Markdown quick-ref got a lot more play than I'd expected, glad that was helpful.

#googleplus #gplusrefugees

dredmorbius@joindiaspora.com

The Plexodus Subreddit: Off-site informational and discussion forum

As there didn't seem to be a discoverable G+ Exodus forum on Reddit, I've created one as of the past day, here:

https://reddit.com/r/plexodus

Why?

  • Because two holes are better than one.
  • Because Reddit offers some tools (moderation capabilities, wiki, sidebar) that G+ communities don't.
  • Because the G+MM (Google+) community won't be available after August 2019.

There's a FAQ detailing more of the whys and wherefores: \
https://old.reddit.com/r/plexodus/wiki/index

You can also follow the subreddit's post and comments activity in a feedreader, or create a bot on other channels based on RSS:

Introductory post:

https://old.reddit.com/r/plexodus/comments/9owxc1/plexodus_the_google_exodus_subreddit/


From the Dept. of I have More Fingers than Pies so What the Heck.

#googleplus #reddit #gplusrefugees #RPlexodus

dredmorbius@joindiaspora.com

Google+ Exodus Recommended Practices

What you should be doing now:

As of October, 2018, given the announced shutdown of Google+ effective August 2019, you and/or your community should:

  • Exchange permanent contact information with contacts and groups. A pinned Profile post is easiest to find. Update your profile "About" page with forwarding addresses. Any addresses you don't want public can be shared in private Circles or Communities, or directly.
  • Talk over and decide on your online/social-media presence after August 2019. Your closest relationships, family, friends, work, professional, or other immediate community will likely be your biggest influence.
  • Start thinking about data: what you want to keep, what you can delete, and how you want to use it.
  • Make a Google Data Takeout Archive. Not because this is the last time you'll need to do this, but because it's likely the first and you should familiarise yourself with the process and its limitations.
  • Start assessing Google+ alternatives.
  • Start developing a goal-directed plan, timeline, and actions to achieve it.

Each of these steps may involve far more detail, this is just a basic outline. Other planning sections of the Plexodus Wiki address activities and aspects in more detail and should be helpful.

#googleplus #gplusrefugees #PlexodusWiki

https://social.antefriguserat.de/index.php/Recommended_Practices

dredmorbius@joindiaspora.com

Data Migration Process and Considerations

Making use of Google+ data take out can be more complicated than it first appears, particularly for a large archive with contributions from many people or organisations. You'll want to consider:

  • What to archive
  • What you want to use from it.
  • How you plan to use the data.
  • What portions of the archive you want to, can be, and you have permissions to make public.
  • Where you plan to publish it, and what tools exist to import the selections you publish.

A practical guide.

#PlexodusWiki #googleplus #gplusrefugees #DataMigration

https://social.antefriguserat.de/index.php/Data_Migration_Process_and_Considerations

dredmorbius@joindiaspora.com

A Practical Guide to Planning and Scheduling your Next Exodus

The Google+ sunset was announced 8 October 2018, and will take effect in August 2019, though a precise date has not yet been set.

This is a timeline for planning which you may adapt to your needs.

Exodus Planning and Scheduling

As an initial approach, consider a four-phase process, on roughly the following schedule:

  • Oct 2018 - Dec 2018: Coordination, Planning, and assessment.
  • Jan 2019 - Apr 2019: Execution.
  • May 2019 - Jul 2019: Re-establishing community.
  • Aug 2019 - ∞: Assess and rebuild.

Groups, sizes, aims, goals, and capabilities vary greatly. We're looking to help everyone from small groups of friends to 100,000+ strong Google Communities, and between.

The schedule is a suggestion, not a requirement, though August 2019 is Google's final service date for public Google+ activity.

#PlexodusWiki #googleplus #gplusexodus #gplusrefugees

Exodus Planning and Scheduling

dredmorbius@joindiaspora.com

PlexodusWiki: Risks and Threat Models

First draft of an article, intent is to consider the issues, risks, and mitigations in various potential online service offerings.

  • Self-hosted.
  • Community- or volunteer-hosted, and hosting.
  • Commercial sites and services.

Both user and host / adminstrator perspectives should be addressed (they are not yet filled out).

Additional resources should be recommended.

I am looking for specific guidance on risks of self-hosting, p2p hosting, and federated hosting situations, a fairly new development and a rapidly changing landscape.

#plexodusWiki #googleplus #gplusrefugees #wiki #securiity #risk #references

https://social.antefriguserat.de/index.php/Risks_and_Threat_Models

dredmorbius@joindiaspora.com

Established G+ Diaspora Communities

As of 13 October 2018, pluspora.com - increased membership from perhaps 100 before the G+ termination announcement (October 9?) to 5500 within a few days afterward .

The MeWe community "Google Plus Refugees" has 124 members. community "Google+" has 20 members.

The Cake interest category "Google" has 189 followers. Recent posts address the demise of G+. The category also tracks other Google-related matters including related consumer devices and working at Google, and others.

I'd like Facebook, Twitter, Reddit, and any other relevant stats as well.

#googleplus #gplusrefugees #PlexodusWiki

https://social.antefriguserat.de/index.php/Established_G%2B_Diaspora_Communities

dredmorbius@joindiaspora.com

Back in the saddle, October 14, 2018. What's on fire?

I'm bandwidth-challenged, will be watching this and my immediate prior Hubzilla/Friendica planning post.

General status:

  • Google+ Mass Migration is getting large and a bit noisy, we're discussing that among mods. I don't want to discourage interest, but do want to keep focus.
  • The #PlexodusWiki is up and running and getting contributions, thanks all who've stepped up: https://social.antefriguserat.de
  • There are concerns over Diaspora hub capacity, scaling, numbers, costs, and features. Hubzilla and Friendica may be better long-term options, and play well with Diaspora. See and discuss on other post.
  • I want to build out the Risks and Concerns wiki section, currently does not exist, brief notes on What's Needed.
  • There are numerous TODO items. It's a target-rich environment, fire at will.
  • I'll set up some sort of logbook and planning pages, also an Editors Lounge, for discussions. Cluebyfour me if I don't get to that soonish.
  • Experienced MediaWiki types very much appreciated. I did learn Transclusion yesterday ("TODO"), which is fucking awesome. Some templates would help.

Thanks!

Be excellent to each other!

#googleplus #gplusrefugees #PlexodusWiki #GoogleMassMigration #TheNewBeginning #PlexodusPlanning #GettingAMoveOn

dredmorbius@joindiaspora.com

The G+ Exodus should start assessing Hubzilla and Friendica for capacity purposes

The reports on scalability, costs, and hub needs from Diaspora pod admins including @Di Cleverly and @David Thiery are suggesting we may need a more scalable solution in the near term.

At the Google+ Mass Migration and The Beginning Is Near communities on G+, Hubzilla and Friendica seem to be promising at scale, though we have thin data on this.

Of the open alternatives, these three are the most developed that I'm aware. Tim Berners-Lee's #Solid and #Irupt are very interesting, but are mostly vapourware at present. If you're interested in exploring them (and I certainly am) do, but for a mass movement, that's likely not where we're going to end up initially.

Friendica and Hubzilla are compatible with existing Diaspora pods, so those on Diaspora can still interact. There are also some sought-after features.

I am reporting information second-hand. What I'd like to see is a concerted effort to investigate and explore this and report back results. @woozle@hey.iseeamess.com is running https://hub.toot.cat, a Hubzilla instance, and I've got a rudimentary presence there: dr@hub.toot.cat (the "edmorbius" got lost, I am now officially The Doctor, the truth is known...) and I've been checking that out as I can. A Hubzilla instance at scale talking to Diaspora would be a great thing to have for performance/cost data. Also Friendica. Please mention any in comments.

A reminder that this is a multi-stage process, and what's happening now is that explorers are evaluating remote lands to see what is suitable, in the long term, or if necessary, the short. There's a lot of agitation at G+ to declare some decision made. Group decisions have not been made, and likely won't for some time. It's been days, we have months. Hammering out a reasonable timetable is something I have in mind.

I'm fairly swamped with G+ notifs, two communities I'm moderating, and getting the PlexodusWiki in shape which (quick look) ... seems to have had a bunch of activity while I was away, a Good Thing. That's Good Trouble, but some independent assessment of other options is needed.

If you can keep discussion in this thread it'll be easier for me to monitor, I'll have another in a moment for more general stuff. I plan to not watch notifications closely today except for fires.

Hope all are well, thanks.

#googleplus #gplusrefugees #PlexodusPlanning #PlexodusWiki #GettingAMoveOn