so now how do you upload a photo to your blog??
Google Is Shutting Down Album Archive
71–75 of 75 posts
Re: Google Is Shutting Down Album Archive
#72This appears to be NEITHER your "Archive" NOR your albums in Google Photos. This is basically a collection of media you uploaded to Blogger, Hangouts, and Picasa Web Albums. Still, doesn't hurt to Takeout your Google Photos every ~6 months. (I am working on an app that will help you organize and view them, together with your text messages, location history, and other online-only data.)
Does that mean that all the images in my blog posts on blogger will disappear? So troubled to hear that a product I never used might disappear and that the impact might be massive for me... or not.
it appears that way
what a mess!!
Re: Google Is Shutting Down Album Archive
#73Earlier quoted context omitted.
I got the email, thought, “huh, never heard of it.” Wasn’t curious enough to find out until I saw this post. Still didn’t understand what exactly this was or how I used it, so I clicked. 30% of the screen (on mobile) is a banner telling me I should be using chrome. Another 40% banner is telling me the site is going away soon soon soon. Another 10% is exhorting me to make connections with my account so others can see…
sounds nightmarish Though I’m not seeing what you describe on Safari with iOS 16.5
Ah, I guess I had to request the desktop site to be able to upload to imgur. If you still care, this is what I saw when I clicked the link in the email.
For some reason, you may get a sensitive media age gate on that link? No idea why, it is entirely innocuous.
Re: Google Is Shutting Down Album Archive
#74Earlier quoted context omitted.
What is the correct tool to properly merge a large set of tar.gz files for which may have an enormous overlap of similar files, and some that have been altered just slightly? Git plus some parsing seems close in that space, as analyzing the files to create a dendrogram like tree of potential alterations to files over time by levenstein distance may be useful to approximate commit history. However, this doesn't seem t…
> What is the correct tool to properly merge a large set of tar.gz files for which may have an enormous overlap of similar files, and some that have been altered just slightly? Can you elaborate on this? My understanding is that they should all extract into the same target folder without issues because each archive's set of files is distinct. But maybe I'm just assuming wrongly? What exactly is your goal, too? It sou…
The problem isn't one takeout overlapping (multiple zips from one date) it's many takeouts over the years (full history).
So for example in 2001, you make a takeout with 30 zips, and then delete half of your photos off of Google. Then in 2007, you have another 20 zips, and delete 25% of your emails and photos to make more room, 2008 again, on up to now.
So now you have a big folder with many zips, and maybe some extracted folders, because things happen over the years, etc.
What's the best tool to merge all of this into one directory?
Got can help for the notes from Google keep that may have had things appended to or removed, photos can be overlapping a bit so really a set union is all that's required for many files, but some will be slightly different like the Google keep notes.
My best thought is to make some git repo and add things in, but to do a levenstein distance on the bits of each file to check if there is overlap in content and to estimate the 'lineage' of a file if there is significant overlap with another. Effectively you reconstruct the git commit tree with the set of all files over all histories. Then you build the git repo history from all of the files.
This would likely just be a local git repo since it would likely be several terabytes of info, but that would be the general idea I guess.
I just haven't found a good tool to actually do this easily unfortunately, but it seems like it would be a very basic , or commonly used scenario (especially for those 'should-be-a-git-repo' directories that everyone made before knowing about git. You know the ones: 'myfile.v1.doc', myfile.v2.doc', 'myfile.final.doc', myfile.reallyfinal.doc', myfile.finalfinal.doc')
Re: Google Is Shutting Down Album Archive
#75Earlier quoted context omitted.
> What is the correct tool to properly merge a large set of tar.gz files for which may have an enormous overlap of similar files, and some that have been altered just slightly? Can you elaborate on this? My understanding is that they should all extract into the same target folder without issues because each archive's set of files is distinct. But maybe I'm just assuming wrongly? What exactly is your goal, too? It sou…
The problem isn't one takeout overlapping (multiple zips from one date) it's many takeouts over the years (full history). So for example in 2001, you make a takeout with 30 zips, and then delete half of your photos off of Google. Then in 2007, you have another 20 zips, and delete 25% of your emails and photos to make more room, 2008 again, on up to now. So now you have a big folder with many zips, and maybe some extr…
_> So now you have a big folder with many zips, and maybe some extracted folders, because things happen over the years, etc._
Oh, right.
Timelinize can do that. Takeout all your data, then import it into Timelinize. Then delete your Takeout (after Timelinize is finished and stable, of course, heh). Then next time you Takeout, just import it all into Timelinize again. (It de-dupes!) Then delete the Takeout, etc. (Maybe Timelinize can do the cleanup for you someday.)
The de-duping depends on the item being recognizable. Best if the data source provides an ID. Otherwise, things like certain metadata and content can be used to determine duplicates.