👓 The breach that killed Google+ wasn’t a breach at all | The Verge

Read The breach that killed Google+ wasn’t a breach at all by Russell Brandom (The Verge)
A bug in the rarely used Google+ network has exposed private information for as many as 500,000 users. Should Google have shared more sooner?
Syndicated copies to:

👓 Project Strobe: Protecting your data, improving our third-party APIs, and sunsetting consumer Google+ | Google

Read Project Strobe: Protecting your data, improving our third-party APIs, and sunsetting consumer Google+ (Google)
Findings and actions from Project Strobe—a root-and-branch review of third-party developer access to Google account and Android device data and of our philosophy around apps’ data access.
Syndicated copies to:

👓 Google+ to shut down after coverup of data-exposing bug | Tech Crunch

Read Google+ to shut down after coverup of data-exposing bug (TechCrunch)
Google is about to have its Cambridge Analytica moment. A security bug allowed third-party developers to access Google+ user profile data since 2015 until Google discovered and patched it in March, but decided not to inform the world. When a user gave permission to an app to access their public pro…
Syndicated copies to:

👓 The Last Goodbye | Path: Simple, Personal Social Networking

Read The Last Goodbye (path.com)

It is with deep regret that we announce that we will stop providing our beloved service, Path.

We started Path in 2010 as a small team of passionate and experienced designers and engineers. Over the years we have tried to lay out our mission: through technology and design we aim to be a source of happiness, meaning, and connection to our users. Along our journey we have laughed and cried with you, and learned valuable lessons. And it is now inevitable to wind down the service to prioritize our work to serve you with better products and services. It has been a long journey and we sincerely thank each one of you for your years of love and support for Path.

The specific shutdown schedule is as below:
- 9.17.2018 : Notice on Path service discontinuation
- 10.1.2018: Unable to download/update the app in iTunes and Google Play
- 10.18.2018: Termination of the Service (Unable to access to Path)
- 11.15.2018: Path related customer service will be closed

The Path service and Terms of Use governing your use of Path will terminate on [10.18.2018].

Prior to [10.18.2018], you can restore retrieve a copy of your data (i.e. your images, text, videos) by following below steps:
1. Visit https://path.com/settings/backups
2. Log in with your Path account
3. Click the button and enter email address that you wish to receive the backup files
OR
1. Open your Path app and go to Setting
2. Click the button and enter your email address that you would like to receive the backup files.
*Please make sure that your Path app is the latest ver.

Please note that you will not be able to access the backup service site after [10.18.2018]. We may not retain copies of any of your data on and from that date. Accordingly, you are encouraged to download and keep copies of your data if you wish to have access from [10.18.2018].

The last time I’d used (read syndicated to via POSSE) Path was about 2 years ago on June 7, 2016. Prior to that, most of my posting to it was by automatic syndication from my website, so I’m glad to see that a large portion of my personal data on the service is already backed up on my own personal website! Hooray!

I do notice that because part of the service’s cachet was either private or limited audience posts, that a lot of my early posting (from 11/29/10 to around December 2014) included photographs that I posted directly to Path and didn’t share very widely. As a result, a lot of my early posting wasn’t done from my own website, so I’m requesting a downloadable backup of all my data before the service goes under. If you used the service, I hope you’re requesting your download as well.

It’s kind of sad that amidst the toxicity of Twitter which gamifies following that a service that limited following and focused on the small and personal is collapsing.

Our incredible journey spanned 7 years and 209 precious moments. Somehow it was still listed as “Beta”?!

Thanks for all the laughs and fun Path, and thanks for giving at least some warning before shutting down all your servers with all of that user data.

Mostly I’m glad that I’m able to post most of my content to my own site now without the reliance on third party social networks to save and maintain my data. If you’re worried about how social services use and abuse your data or may disappear with it altogether–Path will not be the last–and want more control over it, stop by IndieWeb.org to see how you can take back your online identity and data. I and many others are always happy to help those who are interested.

Syndicated copies to:

❤️ kevinmarks tweet

Liked a tweet by Kevin MarksKevin Marks (Twitter)
Syndicated copies to:

👓 Upcoming Changes in the Blogs. | Harvard Blogging Platform

Read Upcoming Changes in the Blogs (Weblogs at Harvard)
7/13/2018 In 2003, the Berkman Center for Internet & Society (now the Berkman Klein Center for Internet & Society) began an unusual experiment: we launched a blogging platform. That seems q…
Syndicated copies to:

📺 Another Web Bites the Dust | YouTube

Watched Another Web Bites the Dust by Alan Levine from YouTube

A salute to just 35 once vibrant free web sites that have bit the dust. Read their names (below) the next time someone raves about some site that will host your content for free.

Syndicated copies to:

👓 Yahoo Messenger is shutting down on July 17, redirects users to group messaging app Squirrel | TechCrunch

Read Yahoo Messenger is shutting down on July 17, redirects users to group messaging app Squirrel (TechCrunch)
It’s the end of an era for Yahoo Messenger, one of the first instant messaging apps on the market that introd. Today, Oath (which also owns TechCrunch) announced that it would be winding down the service on July 17 as it continues to experiment and consider how and if it can have a relevant p…

Interesting, a silo death ostensibly used to do PR for a new app on the same broad platform.

Syndicated copies to:

Reply to Creating an Archive of a Set of Tweets by Aaron Davis

Replied to Creating an Archive of a Set of Tweets by Aaron DavisAaron Davis (collect.readwriterespond.com)
I really like Barnes’ intent to share. I just wonder if there is a means of owning these notes. Ideally, taking a POSSE approach, she might live blog and post this to Twitter. I vaguely remember Chris Aldrich sharing something about this recently, but the reference escapes me. This is also limited with her blog being located at WP.com. I therefore wondered about the option of pasting the content of the tweets into a blog as an archive.

Aaron, the process I use for taking longer streams of Tweets to own them (via PESOS) has Kevin Marks‘ excellent tool Noter Live at its core. Noter Live allows you to log in via Twitter and tweet(storm) from it directly. As its original intent was for live-tweeting at conferences and events, it has some useful built in tools for storing the names of multiple speakers (in advance, or even quickly on the fly) as well as auto-hashtagging your conversation. (I love it so much I took the time to write and contribute a user-manual.)

The best part is that it not only organically threads your tweets together into one continuing conversation, but it also gives you a modified output including the appropriate HTML and microformats classes so that you can cut and paste the entire thread and simply dump it into your favorite CMS and publish it as a standard blog post. (It also strips out the hashtags and repeated speaker references in a nice way.) With a small modification, you can also get your site to add hovercards to your post as well. I’ll also note in passing that it’s also been recently updated to support the longer 280 characters too.

The canonical version I use as an example of what this all looks like is this post: Notes from Day 1 of Dodging the Memory Hole: Saving Online News | Thursday, October 13, 2016.

Another shorter tweetstorm which also has u-syndication links for all of the individual tweets can be found at Indieweb and Education Tweetstorm. This one has the benefit of pulling in all the resultant conversations around my tweetstorm with backfeed from Brid.gy, though they’re not necessarily threaded properly in the comments the way I would ultimately like. As you mention in the last paragraph that having the links to the syndicated copies would be useful, I’ll note that I’ve already submitted it as an issue to Noter Live’s GitHub repo. In some sense, the entire Twitter thread is connected, so having the original tweet URL gives you most of the context, though it isn’t enough for all of the back feed by common methods (Webmentions+Brid.gy) presently.

I’ll also note that I’ve recently heard from a reputable source about a WordPress specific tool called Publishiza that may be useful in this way, but I’ve not had the chance to play with it yet myself.

 

Clearly, you can embed Tweets, often by adding the URL. However, there are more and more people deleting their Tweets and if you embed something that is deleted, this content is then lost. (Not sure where this leaves Storify etc.)

It’s interesting that you ask where this leaves Storify, because literally as I was reading your piece, I got a pop-up notification announcing that Storify was going to be shut down altogether!! (It sounds to me like you may have been unaware when you wrote your note. So Storify and those using it are in more dire circumstances than you had imagined.)

It’s yet another reason in a very long list why one needs to have and own their own digital presence.

As for people deleting their tweets, I’ll note that by doing a full embed (instead of just using a URL) from Twitter to WordPress (or using Noter Live), that the original text is preserved so that even if the original is deleted, a full archival copy of the original still exists.

Also somewhat related in flavor for the mechanism you’re discussing, I also often use Hypothesis to comment on, highlight, and annotate on web pages for academic/research uses. To save these annotations, I’ll add hashtags to the annotations within Hypothesis and then use Kris Shaffer’s excellent Hypothesis Aggregator plugin to parse the data and pull it in the specific parts I want. Though here again, either Hypothesis as a service or the plugin itself may ultimately fail, so I will copy/paste the raw HTML from its output to post onto my site for future safekeeping. In some sense I’m using the plugin as a simple tool to make the transcription and data transport much easier/quicker.

I hope these tips make it easier for you and others to better collect your content and display it for later consumption and archival use.

Syndicated copies to: