A place to cache linked articles (think custom and personal wayback machine)
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.

index.html 4.6KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. <!doctype html><!-- This is a valid HTML5 document. -->
  2. <!-- Screen readers, SEO, extensions and so on. -->
  3. <html lang="fr">
  4. <!-- Has to be within the first 1024 bytes, hence before the <title>
  5. See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
  6. <meta charset="utf-8">
  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
  8. <!-- The viewport meta is quite crowded and we are responsible for that.
  9. See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
  10. <meta name="viewport" content="width=device-width,initial-scale=1">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>Google: Oops, we may have sent your private Google Photos videos to strangers (archive) — David Larlet</title>
  13. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
  14. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
  15. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
  16. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
  17. <link rel="manifest" href="/static/david/icons2/site.webmanifest">
  18. <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
  19. <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
  20. <meta name="msapplication-TileColor" content="#f0f0ea">
  21. <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
  22. <meta name="theme-color" content="#f0f0ea">
  23. <!-- Thank you Florens! -->
  24. <link rel="stylesheet" href="/static/david/css/style_2020-02-16.css">
  25. <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
  26. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" crossorigin>
  27. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" crossorigin>
  28. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" crossorigin>
  29. <meta name="robots" content="noindex, nofollow">
  30. <meta content="origin-when-cross-origin" name="referrer">
  31. <!-- Canonical URL for SEO purposes -->
  32. <link rel="canonical" href="https://mashable.com/article/google-photos-videos-glitch/">
  33. <body class="remarkdown h1-underline h2-underline hr-center ul-star pre-tick">
  34. <article>
  35. <h1>Google: Oops, we may have sent your private Google Photos videos to strangers</h1>
  36. <h2><a href="https://mashable.com/article/google-photos-videos-glitch/">Source originale du contenu</a></h2>
  37. <p>Well, this is awkward. </p>
  38. <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>
  39. <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>
  40. <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>
  41. <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>
  42. <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>
  43. </article>
  44. <hr>
  45. <footer>
  46. <p>
  47. <a href="/david/" title="Aller à l’accueil">🏠</a> •
  48. <a href="/david/log/" title="Accès au flux RSS">🤖</a> •
  49. <a href="http://larlet.com" title="Go to my English profile" data-instant>🇨🇦</a> •
  50. <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">📮</a> •
  51. <abbr title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340">🧚</abbr>
  52. </p>
  53. </footer>
  54. <script src="/static/david/js/instantpage-3.0.0.min.js" type="module" defer></script>
  55. </body>
  56. </html>