Browse Source

Moar cache

master
David Larlet 1 year ago
parent
commit
7028afa6f7
No known key found for this signature in database

+ 67
- 0
cache/2020/3146f1a5743de3217adc3bc854897aaf/index.html View File

@@ -0,0 +1,67 @@
<!doctype html><!-- This is a valid HTML5 document. -->
<!-- Screen readers, SEO, extensions and so on. -->
<html lang="fr">
<!-- Has to be within the first 1024 bytes, hence before the <title>
See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
<meta charset="utf-8">
<!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
<!-- The viewport meta is quite crowded and we are responsible for that.
See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
<meta name="viewport" content="width=device-width,initial-scale=1">
<!-- Required to make a valid HTML5 document. -->
<title>Google: Oops, we may have sent your private Google Photos videos to strangers (archive) — David Larlet</title>
<!-- Generated from https://realfavicongenerator.net/ such a mess. -->
<link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
<link rel="manifest" href="/static/david/icons2/site.webmanifest">
<link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
<link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
<meta name="msapplication-TileColor" content="#f0f0ea">
<meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
<meta name="theme-color" content="#f0f0ea">
<!-- Thank you Florens! -->
<link rel="stylesheet" href="/static/david/css/style_2020-01-24.css">
<!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" crossorigin>

<meta name="robots" content="noindex, nofollow">
<meta content="origin-when-cross-origin" name="referrer">
<!-- Canonical URL for SEO purposes -->
<link rel="canonical" href="https://mashable.com/article/google-photos-videos-glitch/">

<body class="remarkdown h1-underline h2-underline hr-center ul-star pre-tick">

<article>
<h1>Google: Oops, we may have sent your private Google Photos videos to strangers</h1>
<h2><a href="https://mashable.com/article/google-photos-videos-glitch/">Source originale du contenu</a></h2>
<p>Well, this is awkward. </p>

<p>Google has recently notified Google Photos users that due to a "technical issue," in Google Photos, some users' private videos were "incorrectly exported to unrelated users' archives," <a href="https://9to5google.com/2020/02/03/google-photos-video-strangers/" target="_blank">9to5Google</a> reported Monday. </p>

<p>The technical glitch happened on Nov. 21, 2019, and was fixed four days later, on Nov. 25, and it apparently only affected users who used Google Takeout to request a "Download your data" export, which included content stored in Google Photos. </p>

<p>On the flipside, users who downloaded their data now possibly have someone else's videos in their archive (which, by the way, may be incomplete). </p>

<p>The number of users who used Google Takeout to download their data in that five-day period is relatively small; Google told 9to5Google that only 0.01 percent of Photos users attempting Takeouts were affected. Still, with Google Photos being near omnipresent on Android phones — Google <a href="https://9to5google.com/2019/07/24/google-photos-billion-users/" target="_blank">said</a> it had over a billion users last July — even that number isn't negligible. </p>

<p>Google says the issue is fixed and that it "conducted an in-depth analysis to help prevent this from ever happening again." Affected users were notified of the glitch, together with an apology from Google, and a suggestion to "perform another export of your content and delete your prior export at this time."</p>
</article>


<hr>

<footer>
<p>
<a href="/david/" title="Aller à l’accueil">🏠</a> •
<a href="/david/log/" title="Accès au flux RSS">🤖</a> •
<a href="http://larlet.com" title="Go to my English profile" data-instant>🇨🇦</a> •
<a href="mailto:david%40larlet.fr" title="Envoyer un courriel">📮</a> •
<abbr title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340">🧚</abbr>
</p>
</footer>
<script src="/static/david/js/instantpage-3.0.0.min.js" type="module" defer></script>
</body>
</html>

+ 11
- 0
cache/2020/3146f1a5743de3217adc3bc854897aaf/index.md View File

@@ -0,0 +1,11 @@
title: Google: Oops, we may have sent your private Google Photos videos to strangers
url: https://mashable.com/article/google-photos-videos-glitch/
hash_url: 3146f1a5743de3217adc3bc854897aaf

<p>Well, this is awkward. </p>
<p>Google has recently notified Google Photos users that due to a "technical issue," in Google Photos, some users' private videos were "incorrectly exported to unrelated users' archives," <a href="https://9to5google.com/2020/02/03/google-photos-video-strangers/" target="_blank">9to5Google</a> reported Monday. </p>
<p>The technical glitch happened on Nov. 21, 2019, and was fixed four days later, on Nov. 25, and it apparently only affected users who used Google Takeout to request a "Download your data" export, which included content stored in Google Photos. </p>
<p>On the flipside, users who downloaded their data now possibly have someone else's videos in their archive (which, by the way, may be incomplete). </p>
<p>The number of users who used Google Takeout to download their data in that five-day period is relatively small; Google told 9to5Google that only 0.01 percent of Photos users attempting Takeouts were affected. Still, with Google Photos being near omnipresent on Android phones — Google <a href="https://9to5google.com/2019/07/24/google-photos-billion-users/" target="_blank">said</a> it had over a billion users last July — even that number isn't negligible. </p>

<p>Google says the issue is fixed and that it "conducted an in-depth analysis to help prevent this from ever happening again." Affected users were notified of the glitch, together with an apology from Google, and a suggestion to "perform another export of your content and delete your prior export at this time."</p>

+ 59
- 0
cache/2020/efc69100e48d4016a6e167797da7ee13/index.html
File diff suppressed because it is too large
View File


+ 5
- 0
cache/2020/efc69100e48d4016a6e167797da7ee13/index.md
File diff suppressed because it is too large
View File


+ 101
- 0
cache/2020/f45cdbe527b4c4acead78cef9e4d533f/index.html
File diff suppressed because it is too large
View File


+ 45
- 0
cache/2020/f45cdbe527b4c4acead78cef9e4d533f/index.md
File diff suppressed because it is too large
View File


+ 6
- 0
cache/2020/index.html View File

@@ -47,6 +47,10 @@
<li><a href="/david/cache/2020/2390380d879c04ee56baf320b6f7e681/" title="Accès à l'article caché">Twelve Million Phones, One Dataset, Zero Privacy</a> (<a href="https://www.nytimes.com/interactive/2019/12/19/opinion/location-tracking-cell-phone.html" title="Accès à l'article original">original</a>)</li>
<li><a href="/david/cache/2020/3146f1a5743de3217adc3bc854897aaf/" title="Accès à l'article caché">Google: Oops, we may have sent your private Google Photos videos to strangers</a> (<a href="https://mashable.com/article/google-photos-videos-glitch/" title="Accès à l'article original">original</a>)</li>
<li><a href="/david/cache/2020/f45cdbe527b4c4acead78cef9e4d533f/" title="Accès à l'article caché">You Are Now Remotely Controlled</a> (<a href="https://www.nytimes.com/2020/01/24/opinion/sunday/surveillance-capitalism.html" title="Accès à l'article original">original</a>)</li>
<li><a href="/david/cache/2020/662f4136a25b828f662a6e822d85575d/" title="Accès à l'article caché">Who Listens to the Listeners?</a> (<a href="https://librarianshipwreck.wordpress.com/2019/12/06/who-listens-to-the-listeners/" title="Accès à l'article original">original</a>)</li>
<li><a href="/david/cache/2020/4d81a301bbb7936312cd16e6674f3ff6/" title="Accès à l'article caché">A Group Is Its Own Worst Enemy</a> (<a href="http://shirky.com/writings/group_enemy.html" title="Accès à l'article original">original</a>)</li>
@@ -97,6 +101,8 @@
<li><a href="/david/cache/2020/322e7a8997c732a5fdca0baaea7b9ede/" title="Accès à l'article caché">Guide to Internal Communication, the Basecamp Way</a> (<a href="https://basecamp.com/guides/how-we-communicate" title="Accès à l'article original">original</a>)</li>
<li><a href="/david/cache/2020/efc69100e48d4016a6e167797da7ee13/" title="Accès à l'article caché">Researchers Find 'Anonymized' Data Is Even Less Anonymous Than We Thought</a> (<a href="https://www.vice.com/en_us/article/dygy8k/researchers-find-anonymized-data-is-even-less-anonymous-than-we-thought" title="Accès à l'article original">original</a>)</li>
<li><a href="/david/cache/2020/566b71b4e3a0217d7a224f71aa255a35/" title="Accès à l'article caché">Which tech companies are doing the most harm?</a> (<a href="https://slate.com/technology/2020/01/evil-list-tech-companies-dangerous-amazon-facebook-google-palantir.html" title="Accès à l'article original">original</a>)</li>
<li><a href="/david/cache/2020/1d190443e06aa99b44dd2a4d55b1b58e/" title="Accès à l'article caché">The Secretive Company That Might End Privacy as We Know It</a> (<a href="https://www.nytimes.com/2020/01/18/technology/clearview-privacy-facial-recognition.html" title="Accès à l'article original">original</a>)</li>

Loading…
Cancel
Save