Dear Google+: We're inviting you to comment to the G+MM community on what if any plans, commitments, capabilities,...
Dear Google+: We're inviting you to comment to the G+MM community on what if any plans, commitments, capabilities, migration support, etc., Google are planning.
My view has been that if Google don't provide some clarification within the first month of the announced shutdown, there's likely to be little if any support. There are three days left in that first month. The Google+ profile has not posted in three weeks, and its recent posts are locked against comments.
I've reached out previously to Google directly through its press contact, with follow-up requests, specifically for Ben Smith, VP Engineering, or someone within his group to speak to G+MM. That request stands and is renewed here.
As one of the moderators of this 3,000+ member community (all joined since 8 October 2018), we're very much hoping to hear from you, and soon. Normally our format is an Ask me Anything, but at the very least, and even if you don't have solid plans or schedules, we'd like to know what's in the cards, especially the following:
Information on any features or capabilities of G+ to be disabled in advance of the final shut-down date. Presumably new-account formation will be among these, possibly new Community formation. The former is fairly understandable, the latter might be useful even at a late date in the migration for on-platform planning.
Post-sunset availability of the G+ website itself. Will profiles and content still be Web-accessible? There's a substantial and long-lived set of content here, and a complete shutdown would be highly disruptive.
Post-sunset access to users' Google+ data via Data Takeout. It's quite likely that not all users will have attempted, or succeeded, in creating and offloading their Google+ content. If it will still be able to create archives past the sunset date, this would be exceptionally useful information to have.
Tools for migrating Google+ data to new platform(s). Numerous present G+ users would like to be able to migrate their personal posts, comments, photos, and other content to new platforms, likely to include other major social media platforms (Facebook, Twitter, SmugMug/Flickr, etc.), blogs (Wordpress, Dreamwidth, Blogger, Medium, etc.), and the emerging universe of open and federated platforms. These archives will almost certainly contain non-public data which could be at best embarrassing, and potentially personally catastrophic or worse, if made public. Tools for safely and responsibly handling large data archives are lacking, and the present instructions and data structures within the Google+ elements of Google Data Takeout fail to adequately support this process. We are aware of third-party efforts to create migration tools, including from G+MM members, and Tim Berners-Lee of Solid who has begun work on a G+ Data Takeout migration tool. What specific steps, tools, instructions, and data format changes are Google planning to ensure that this process is effective, efficient, responsible, and respectful of privacy? Further, are Google now taking steps to work with both proprietary and Free Software projects to provide for import tools?
Present G+ users will need to store their G+ data takeouts prior to migration elsewhere as well as for some time afterward to ensure full restoration. One of the available storage options is Google Drive, and at the very least, holding G+ data on Google Drive should not change the security risks appreciably over their initial Google-based storage. The size of some archives will push many users over the free service tier of Google Drive capacity. Will Google commit to providing indefinite free storage of Google+ Data Takeout archives on Google Drive without registering the data storage against other user limits?
Use of Google Drive also presents an opportunity for Google to provide on-system access and management of G+ Data Takeout archives. Given this, will Google commit to providing native tools for viewing, searching, filtering, extracting, and exporting Google+ archives from within Google Drive, including at least post, comment, image, video, collection, and contact data, as well as for distinguishing public from non-public content, and providing for export to leading endpoints including Facebook, Diaspora, Friendica, Markdown, and a standard minimally complex HTML format, with batch-process (rather than individual item) capabilities?
(There are likely other elements I'm omitting from this list and I invite G+MM members to suggest other needs, say, HOA, chat, events, or other G+ features which may be of interest in preserving.)
G+ specialised in image presentation and was immensely popular amonst photographers. Classification of photographs, and in particular, sorting through photographic archives is a challenging task, particularly at volume. Google have considerable experience in image processing and recognition. Will Google commit to providing descriptive search capabilities to photo and image collections, as well as other descriptive characteristics such as date, size, format, and EXIF metadata, for searching, organising, selecting, and exporting image collections? Naturally, the sensitive information which may result from such analysis should be limited in access to the archive's owner only and not be provided or made available to any other parties.
Google Communities were a major feature of Google+ and range in size to millions of members, with over 5 million communities created. There is presently no mechanism for exporting G+ communities as a whole in any format. This might be of value to either community owners in reconstituting the community elsewhere, or to members wishing to retain access to years worth of contributions. Will Google commit to providing tools for Community owners and members to export G+ Community posts and texts in a useful format?
Thank you.
My view has been that if Google don't provide some clarification within the first month of the announced shutdown, there's likely to be little if any support. There are three days left in that first month. The Google+ profile has not posted in three weeks, and its recent posts are locked against comments.
I've reached out previously to Google directly through its press contact, with follow-up requests, specifically for Ben Smith, VP Engineering, or someone within his group to speak to G+MM. That request stands and is renewed here.
As one of the moderators of this 3,000+ member community (all joined since 8 October 2018), we're very much hoping to hear from you, and soon. Normally our format is an Ask me Anything, but at the very least, and even if you don't have solid plans or schedules, we'd like to know what's in the cards, especially the following:
Information on any features or capabilities of G+ to be disabled in advance of the final shut-down date. Presumably new-account formation will be among these, possibly new Community formation. The former is fairly understandable, the latter might be useful even at a late date in the migration for on-platform planning.
Post-sunset availability of the G+ website itself. Will profiles and content still be Web-accessible? There's a substantial and long-lived set of content here, and a complete shutdown would be highly disruptive.
Post-sunset access to users' Google+ data via Data Takeout. It's quite likely that not all users will have attempted, or succeeded, in creating and offloading their Google+ content. If it will still be able to create archives past the sunset date, this would be exceptionally useful information to have.
Tools for migrating Google+ data to new platform(s). Numerous present G+ users would like to be able to migrate their personal posts, comments, photos, and other content to new platforms, likely to include other major social media platforms (Facebook, Twitter, SmugMug/Flickr, etc.), blogs (Wordpress, Dreamwidth, Blogger, Medium, etc.), and the emerging universe of open and federated platforms. These archives will almost certainly contain non-public data which could be at best embarrassing, and potentially personally catastrophic or worse, if made public. Tools for safely and responsibly handling large data archives are lacking, and the present instructions and data structures within the Google+ elements of Google Data Takeout fail to adequately support this process. We are aware of third-party efforts to create migration tools, including from G+MM members, and Tim Berners-Lee of Solid who has begun work on a G+ Data Takeout migration tool. What specific steps, tools, instructions, and data format changes are Google planning to ensure that this process is effective, efficient, responsible, and respectful of privacy? Further, are Google now taking steps to work with both proprietary and Free Software projects to provide for import tools?
Present G+ users will need to store their G+ data takeouts prior to migration elsewhere as well as for some time afterward to ensure full restoration. One of the available storage options is Google Drive, and at the very least, holding G+ data on Google Drive should not change the security risks appreciably over their initial Google-based storage. The size of some archives will push many users over the free service tier of Google Drive capacity. Will Google commit to providing indefinite free storage of Google+ Data Takeout archives on Google Drive without registering the data storage against other user limits?
Use of Google Drive also presents an opportunity for Google to provide on-system access and management of G+ Data Takeout archives. Given this, will Google commit to providing native tools for viewing, searching, filtering, extracting, and exporting Google+ archives from within Google Drive, including at least post, comment, image, video, collection, and contact data, as well as for distinguishing public from non-public content, and providing for export to leading endpoints including Facebook, Diaspora, Friendica, Markdown, and a standard minimally complex HTML format, with batch-process (rather than individual item) capabilities?
(There are likely other elements I'm omitting from this list and I invite G+MM members to suggest other needs, say, HOA, chat, events, or other G+ features which may be of interest in preserving.)
G+ specialised in image presentation and was immensely popular amonst photographers. Classification of photographs, and in particular, sorting through photographic archives is a challenging task, particularly at volume. Google have considerable experience in image processing and recognition. Will Google commit to providing descriptive search capabilities to photo and image collections, as well as other descriptive characteristics such as date, size, format, and EXIF metadata, for searching, organising, selecting, and exporting image collections? Naturally, the sensitive information which may result from such analysis should be limited in access to the archive's owner only and not be provided or made available to any other parties.
Google Communities were a major feature of Google+ and range in size to millions of members, with over 5 million communities created. There is presently no mechanism for exporting G+ communities as a whole in any format. This might be of value to either community owners in reconstituting the community elsewhere, or to members wishing to retain access to years worth of contributions. Will Google commit to providing tools for Community owners and members to export G+ Community posts and texts in a useful format?
Thank you.
If anyone has additional questions they'd like to add to the ask, please feel free. The list I'd started with is one I've 1) previously submitted to Google and/or 2) been thinking about since.
ReplyDeleteCould you +1 this comment do I can read in the morning?
ReplyDelete/sub
ReplyDelete/sub
ReplyDelete/S
ReplyDeleteGoogle+ is #1
ReplyDeleteYour narrated list elaborated, kudos
Good evening I tried twice to download my data with Takeout it was a total effect. Pass a good evening
ReplyDelete/sub
ReplyDelete/sub
ReplyDeleteWhat are post-Sunset plans for Google Profiles?
ReplyDeleteThere are numerous places in the Takeout files that point to the current G+ Profile. Will those links all fail post the G+Sunset?
Will there be a publicly visible version of a Google Account's "About Me" information?
Takeout Enhancements
There are lots of small enhancements needed to the Takeout files. Early adopters have been posting feedback about these. What plans are there for updates to the Takeout files?
/futility
ReplyDelete/sub
ReplyDelete/sub
ReplyDeleteLev Osherovich I've got the matching belt and shoes.
ReplyDeleteJulian Bond Good point. Filip H.F. Slagter: you'd have some better info than me on references in the Takeout set, anything you'd add?
ReplyDelete/sub
ReplyDeleteJulian Bond Hello I try to download my data with Takeout they had a lot of errors in my files that were imported and even the one that was error free was unreadable. They seem to be trying to fix this problem before Google+ closes.
ReplyDeleteNatacha Leriche I think I've done all the takeouts in both JSON and HTML. activitylog was broken to start with but seems better now. They all basically worked for me but they've all got detailed problems.
ReplyDeleteJulian Bond Google are working on improving Takeout.
ReplyDeleteEdward Morbius The G+ Product Experts have collaborated on a comprehensive document raising many questions connected to the sunsetting, which was acknowledged by the engineers we met at last week's Product Experts summit.
We have 10 months until the sunset for a very good reason. It will take a lot longer than a month to unpick all the integrations and plan, much less execute, the sunsetting. There are many decisions to be made, and Google are unlikely to share what they are until they've had time to fully explore what is and isn't achievable.
When Google have something to announce, they will announce it. But until then, we simply have to be patient.
Julie Wills Any public docs or refs from the Summit?
ReplyDeleteAny sense of how organised Google are or aren't? Was the sunset announcement anticipated or not?
Edward Morbius No, nothing public.
ReplyDelete1. Why was 'originalContent' removed from Google+ Stream Posts JSON data, and can it be added back to the Takeout data?
ReplyDeleteEarly on (at least around 2013) Takeout archives had significantly different data in their JSON, in a structure that more closely matched the format documented in the Google+ API and the google-api-client (at least the one written in Ruby).
The current format however differs greatly, especially w.r.t. Access Control Lists (Acl), and especially lacks the 'originalContent' data, which contained the content of the Activity (the generic resource name for Posts and other content on G+) as it was originally submitted, rather than only the HTML-formatted data in the 'content' key.
I understand the need for refactoring the Acl datastructure to account for new Acl settings for for instance Collections, however I don't quite understand why the originalContent data was removed?
I would highly appreciate this data being added back.
Why? Google+'s HTML formatted text didn't always reflect the intended original formatting, especially in the early days. G+'s forced auto-linking of text containing @signs also has a tendency to make non-account references (especially Mastodon profile addresses, e.g. @ FiXato @ mastodon.social (without spaces) would get changed to *****) illegible.
tl/dr (1): please add the unformatted, original source post bodies (originalContent) back to the Google+ Stream Posts Takeout archives data
2. What will happen to other platforms that still offer some form of integration with Google+, Blogger in particular?
Some other platforms still offer integration options with G+, in particular your own blogging platform Blogger/Blogspot comes to mind.
Blogger for instance offers the options to use Google+ for top-level comments and to automatically share the new entries to Google Plus.
Important to note though is that at least 4 of the 'Help' links regarding Google+ Comments inside Blogger are no longer working:
= https://www.blogger.com/go/private-blog-disabled (Help link for Settings/Basic/Blog Readers/"Google+ Comments enabled")
= https://www.blogger.com/go/gpluscommentshelp ("Learn More" link for Settings/Posts, Comments & Sharing/"Use Google+ Comments on this blog")
= https://www.blogger.com/go/gplussharehelp ("Learn More" link for Settings/Posts, Comments & Sharing/"Auto-share new published posts to your Google+ profile")
= https://www.blogger.com/go/gplustabhelp ("Learn More" link for Settings/Posts, Comments & Sharing/Share to Google+/"Associating your blog")
2a. what will happen to comments on Blogger articles that were submitted using the Google+ Comments system?
Will you offer an option to convert them into Blogger-native comments, will they turn into read-only legacy G+ comments, or will they just disappear completely after Google+ has been shutdown?
2b. what will happen to the automatic Share To Google+ option for new Blogger articles?
Will it be replaced with new auto-share options, or just silently disappear?
2c. what will happen to Blogger blogs that currently have Google+ set as User Profile?
(Settings/User Settings/General/User Profile)
tl/dr (2): please allow for conversion of Google+ Comments on Blogger articles to native Blogger Comments, and list other platforms affected by GPlus' shutdown, and fix help links on Blogger.
3. What will happen to Google+ Pages aka sub-account profiles.
ReplyDeleteThis is rather related to the previous section of questions, as it's mostly about integration with other platforms, but due to its potential impact, I decided to list it separately.
Within your Google/Google+ main profile, you were allowed to create Google+ Pages, which were/are basically stand-alone sub profiles which (theoretically) shouldn't be publicly traceable to your main profile. As such, quite some users opted to create one or more of these, to separate their online identities, especially during the early days when the Real Name Policy was still in effect, as Pages were not necessarily affected by the Real Name Policy.
Especially during the forced YouTube/Google+ integration, one of the options was to create a Google+ Page for your YouTube channel, and bind your YouTube account to that, rather than the main Google Profile. Myself, as well as likely a sizeable amount of other YouTube users, picked this option, rather than to bind it to my main Google Profile, or to create a new Google Profile. Currently my main YouTube channel is still linked to my Google+ Page. What will happen to these Pages and YouTube accounts?
Within Blogger as well, you have the option to post from your Google+ Page identities, as well as to auto-share to your Google+ Page identity.
Will you continue to be able to switch to these Pages (sub-)accounts from within your main Google profile, even after Google+ has shut down? Will there be a migration option to turn them into full-blown, stand-alone, Google profiles? Or will they disappear completely?
tl/dr (3): what will happen to Google+ Pages, and their use as login accounts for YouTube and Blogger? Is there a migration path?
4. Why haven't we been contacted by e-mail yet about the upcoming Google+ Sunset?
The Google+ Sunset was first announced as a side-note on the Google Security blog, even before it was announced by the +Google+ Google+ account. Neither of these are sources every Google+ user typically reads. Most of us heard the news through third parties like other Google+ users, or news media outlets. However, this still does not cover all Google+ users. Even yesterday a friend of mine had to hear of the imminent shutdown from me, as it wasn't as widely spread in the news in the Netherlands, as it apparently has been in Google's home, the USA.
So, why haven't Google+ users been shown the courtesy yet of being contacted about this important change via the e-mail account(s) associated with their accounts and Pages?
tl/dr (4): Bring all of your user-base up-to-speed ASAP via a form of contact that is most likely to get their attention: e-mail.
5. Long filenames get cropped in the Google Takeout Archives: please add a metadata file that provides mappings from their shortened filename to their original filename
Currently files with long filenames will get shortened to for instance "Cropped Filena(1).jpeg", resulting in a loss of metadata, as the original filename can no longer be restored.
A simple metadata file which provides the original full filename for each shortened filenames, would solve this issue. It could be as simple as a plain text file with on each line:
/path/to/Cropped Filena(1).jpeg: /path/to/Cropped Filename That Was Too Long.jpeg
Though preferably a JSON file which not only contains the original and cropped filenames, but also an array of the Activity resources and other files in the archive it's associated with (such as relevant photo.metadata.csv and post.json files).
tl/dr (5): provide a file that maps the cropped filepaths to their original filename/-path, and ideally also the other files in the archive it's associated with.
ReplyDelete*6. Provide tools and documentation for the Google+ Takeout Archives
Currently the Google+ Takeout data (and Takeout data in general) is undocumented. (If there actually is documentation, it's too well-hidden). There also are no ready-made tools, such as commandline filter tools or scripting language libraries, available to read in the data for easy filtering and processing.
Providing detailed documentation including what keys are always provided, which ones can optionally be expected (and in which situation), and what data type the values have (String, Integer, Time/Date/DateTime (and which (ISO) format), is paramount.
Providing data model libraries for popular (scripting) languages such as Ruby, Python, Go, JS, C#, which can be used to load in the Takeout archive files, would come a long way towards helping users migrate their data to other alternatives.
tl/dr (6): Please provide documentation and libraries to help process the Takeout data
7. Circles data is very limited
Google+ Circles Export currently only contains:
First Name, Last Name, Nickname, Display Name, and Profile URL
This data is a small fraction of what is available to us currently on Users' profile pages. The Profile URL will likely become useless when Google+ is shutdown.
Ideally this takeout will contain all data that is currently available to you (depending on the target user's visibility settings):
Profile info:
= First
= Surname
= Nickname
= Display name as
= Banner photo
= Profile photo
Personal contact info:
= Phone number(s)
= E-mail address(es)
= Chat contact(s) details
=Address(es)
Work Contact Info
= Phone number(s)
= E-mail address(es)
= Chat contact(s) details
=Address(es)
Work history
= Company listing(s):
== Name
== Title
== Start date
== End date
== Description
Gender, date of birth and more:
= Gender
= Birthday (taking into account whether "Show year" is toggled or not)
= Occupation
Story
=Tag line
= Introduction (retaining rich text formatting)
Skills
= List of skills
Link to album archive
Education:
= School/universities attended:
== Name of school
== Main course/field of study
== Start date
== End date
== Description
Sites:
== Link(s)
=== Title
=== URL
== Other profile(s):
=== Title
=== URL
== Contributor to:
=== Title
=== URL
=== Current? toggle
Especially the Sites data is paramount for users seeking to find their former followers / people they followed on new platforms.
tl/dr (7): Add all missing profile information to Google+ Circles Takeout data
8. List of Followers:
Maybe I've missed it, but I haven't been able to find a list of people who are following me yet, in the Takeout archives. This should ideally contain the same data as the above revised data for Circles.
tl/dr (8): Add list of Followers along with their metadata, to the Takeout archive.
9. Why was the shutdown announced before the implications of it were clearly mapped out, and could be announced publicly?
The way this was announced as side-note in a security blog, makes me wonder if this announcement was perhaps premature, and that not all implications w.r.t. integrations were actually clear yet. It would've been nice if there was more information to us from the start, as it would've resulted in less fear, uncertainty and doubt.
ReplyDeleteRegardless, I'd like to at least express my heartfelt thanks especially to the Googlers who made Google Plus a reality and whose early work truly made Plus a unique platform and experience. Especially during the early days and the heydays before the majority of useful integrations were abstracted out again. But also to those who fought to keep the platform alive.
ReplyDeleteLast but not least, to my fellow Plussers who kept 'haunting the ghost town'.
Here's hoping to more information, and clarification of the info we've already received.
Some public clarification about what Google+ Enterprise for G Suite users means, would also be appreciated, as a lot of users seem to think it's about businesses still being able to use (the same, public) Google+ after the sunset.
ReplyDeleteWhereas how I understand it, it rather means an internal-only, stand-alone Google+ for each G Suite domain, where only users within the same G Suite domain can communicate to each other.
sub
ReplyDeleteregarding the +**** thing in one of my posts: this seems to be a broken auto-mention feature which is meant to hide (I suspect) e-mail addresses, or accounts of people who have blocked you. Not a bad feature by itself, just annoying when it gets triggered when it shouldn't.
ReplyDeleteThe latter is the case in my post above, where it interprets a Mastodon account name in the form of `@ username @ mastodon instance`, as an internal G+ account reference (which is stupid imho, as G+ originally decided to use plus-mentioning rather than at-mentioning), or as an e-mail address (which is also illogical, as it starts with an @, rather than having just a single @-sign). Adding support for wrapping text in some kind of "don't parse" markup, such as commonly used backticks, would fix that issue.
Google+'s formatting has always been a tad broken, and I never understood why they didn't just adopt actual Markdown, rather than their own Markdown AsciiDoc-inspired format.
/sub
ReplyDeleteFilip H.F. Slagter I'm deleting OT and derisive commentary, including the reference of your long comment immediately above..
ReplyDeleteFlagging and pinging mods is preferred.
Filip H.F. Slagter G+ markup is AsciiDoc inspired, though it's a broken form of that, too.
ReplyDeleteEdward Morbius I've edited my comment accordingly to reflect the cleaned-up topic.
ReplyDelete/sub
ReplyDelete/sub
ReplyDeleteShared to Google Plus Meetup
ReplyDeleteal m URL?
ReplyDeleteGoogle Plus Meetup on Facebook.
ReplyDeletefacebook.com - Log into Facebook | Facebook
There's some (current) information on Blogger connections at
ReplyDeletehttps://support.google.com/blogger/answer/187141
and
Google+ Profiles in Blogger is here: https://support.google.com/blogger/answer/41375
support.google.com - Manage your comments - Blogger Help
Julie Wills that doesn't fix the fact though that Blogger's interface is riddled with dead links / linkrot.
ReplyDeleteYou'd expect better from a Search company that offers tools to detect dead links (https://support.google.com/webmasters/answer/35120?hl=en)...
Update: I've used the Feedback tool on Blogger's Settings page to at least report the broken links that way. If other Blogger users could do the same, it would help to bring the issue to their attention.
support.google.com - Crawl Errors report (websites) - Search Console Help
sub
ReplyDeleteneed to follow this thread, sadly no “subscribe” option here, sry.
ReplyDeleteThomas Rohde yeah, we've only been asking for it since the beginning ;) that and permalinks to comments.
ReplyDeleteFilip H.F. Slagter and we HAD permalinks to comments using DoShare! It was possible. It CAN be done. Could be.
ReplyDeleteplus.google.com - Plussers...Are We Really as Smart as We Think We Are? Or Is It Just Me? Lege...
Well, the very first mistake here was to treat comments differently from posts.
ReplyDeleteBack in the old days of Usenet, everything was a post. And posts dependant on each other were linked via a chain of reference pointers. Even if parts of a thread got lost, it was possible to keep the structure alive.
Gerhard Torges Posts are unparented comments.
ReplyDeleteIn (on, at?) Usenet discussions, the "comments" would survive if you'd deleted a post.
ReplyDelete/sub
ReplyDeleteNot sure if this data was added to Takeout recently, or if I just missed it when I looked at all the options earlier, but there's quite complete profile information in Takeout/Profile/Profile.json. Similar to what I requested for each G+ Contact, but then only for your own profile. This is the info I'd like to see for all of my Google+ Contacts though.
ReplyDeleteYeah, the shutdown was so sudden, they haven't announced where we can EXACTLY migrate to.
ReplyDeleteHi itz Alice to be honest, it's not Google's responsibility to find us new homes.
ReplyDeleteHi itz Alice It's not sudden. It's not going away until next August - over 10 months after the initial announcement.
ReplyDeleteFilip H.F. Slagter They can assist with transition tools, however.
ReplyDeleteAn addendum to my AMA questions to Google:
ReplyDelete10: Add 'activityId' data to Takeout data
Currently there seems to be no easy way to query the API for additional data based solely on the data in the Google+ Stream Posts Takeout archive, because the JSON data structure does not include unique IDs for the Activities (i.e. activityId). Nor does the API allow for looking up an activityId for any of the resourceName data in the Takeout archives.
tl/dr 10: Add activityId to Takeout data, and add support for resourceName or Permalink lookups to the API
What kind of data are you referring to by the term "activityId", Filip H.F. Slagter?
ReplyDeleteGerhard Torges the Activity#id defined by and required by the Google+ API: https://developers.google.com/+/web/api/rest/latest/activities#resource
ReplyDeleteNone of the values in the Google+ Stream/Posts/yyyymmdd-post.json files match this unique identifier, which makes it impossible to look up additional information for a post through the API.
developers.google.com - Activities | Google+ Platform for Web | Google Developers
Edward Morbius we may have a solution.
ReplyDeleteWe've released Google+ Exporter, an application that helps you to export your Google+ feeds (profile, pages, collections, communities, including all comments) to Wordpress eXtended RSS file.
Another available option is to export all posts published to profile, pages, collections, and communities to JSON file, including all comments!
Transform exported JSON data can into imports for other services, or you can use JSON export as a full generic backup of your posts.
The free version of the application enables you to export up to 3000 posts. You can buy a license key to get unlimited experience.
I would love to know your opinion, suggestions or requests. Thank you!
You can find more detailed info in the blog post
blog.friendsplus.me - Export Google+ feeds to Wordpress or JSON file – Friends+Me
Friends+Me I've seen that announcement, looks interesting, have not yet explored it myelf.
ReplyDeleteCommunities export is a remaining chalenge.
There's an obvious set of privacy concerns here as well that should be addressed, with several dimensions.
Archive storage (say, to some service: Google Drive, Dropbox, or NextCloud, say) wuld be interesting.
Also the ability to make incremental future updates: save now, get more later, not have to re-fetch everything, not lose content from deleted profiles, communities, and pages.
You may be interested in my ongoing analysis of Google Communities number and membership (though not activity -- that's harder to get at).
https://old.reddit.com/r/plexodus/comments/9zx67d/google_communities_membership_analysis_preview/
old.reddit.com - Google+ Communities Membership Analysis Preview • r/plexodus
Edward Morbius I'm interesting in paying you and Alex Kudlick to build the best open source tools for exporting G+ content. You've already done the competitive analysis and identified all the must-haves and the relative strengths and weaknesses of the competition.
ReplyDeleteInteresting. I will have some free time coming up since I have every Thursday off. I have some projects on my plate, one of which could end up being a replacement for g+ for me.
ReplyDeleteAlex Kudlick Edward Morbius , let's discuss in separate thread.
ReplyDeleteLev Osherovich I'm the wrong person to ask, but thanks.
ReplyDeleteEdward Morbius au contraire, you have the knowledge of what is wrong and right about data migration and have exacting standards. You are the perfect person to architect this.
ReplyDeleteLev Osherovich Ping me in from the new thread.
ReplyDelete