Internet Archive: Difference between revisions

(4 intermediate revisions by 2 users not shown)

Line 1:

{{InfoboxCompany

| Name = Netflix, Inc.

Line 10:

Line 11:

https://archive.org/

==Consumer-impact summary==

[TBA]

==Incidents==

===Login-only items for legally dubious content (2016-present)===

On January 13, 2016, Hank Bromley (hank_b) of the Internet Archive created a collection of uploads considered legally dubious and only viewable with an account.<ref>{{Cite web |title=Download & Streaming : Log In Required : Internet Archive |url=https://archive.org/details/loggedin?tab=about |url-status=live |archive-url=https://archive.ph/rSKdG |archive-date=2025-08-16 |access-date=2025-08-16 |website=[[Internet Archive]]}}</ref>

https://~~web~~.archive.~~org~~/

These uploads cannot be viewed by logged-out users and cannot be downloaded by anyone except the admins, making any of these pieces of content inaccessible.<ref>{{Cite web |title=Internet Archive Forums: Log In Required, after logging in. |url=https://archive.org/post/1092552/log-in-required-after-logging-in |url-status=live |archive-url=https://archive.ph/fFVg6 |archive-date=2025-08-16 |access-date=2025-08-16 |website=[[Internet Archive]]}}</ref>

===Archived Website Censorship===

The Internet Archive retroactively removes or hides material covered by robots.txt restrictions.{{Citation needed}}

==~~Censorship~~==

===Data Breaches (2012-2024)===

~~Topics~~:

On May 19, 2017, The Archive's Development Manager Katie Barrett made a blog post detailing that anyone who had created their account before 2012 had to change their password as the site had been breached with user's public information and lightly encrypted passwords being leaked.<ref>{{Cite web |last=Barrett |first=Katie |date=2017-05-19 |title=Re: User account breach {{!}} Internet Archive Blogs |url=https://blog.archive.org/2017/05/19/re-user-account-breach/ |url-status=live |archive-url=https://web.archive.org/web/20250520030556/https://blog.archive.org/2017/05/19/re-user-account-breach/ |archive-date=2025-05-20 |access-date=2025-08-16 |website=[[Internet Archive]]}}</ref>

~~Login~~-~~only items for legally dubious content~~,

On October 9, 2024, users on the Internet Archive got pop-ups that the website had been hacked with notifications appearing from the perpetrators at around 9PM CST,<ref>{{Cite web |date=2024-10-09 |title=Dark Web Informer on X |url=https://x.com/DarkWebInformer/status/1844123206413943274 |url-status=live |archive-url=https://ghostarchive.org/archive/ADnLW |archive-date=2024-10-12 |access-date=2025-08-16 |website=[[Twitter]]}}</ref> and an hour later Troy Hunt of HaveIBeenPwned confirmed the breach.<ref>{{Cite web |last=Hunt |first=Troy |date=2024-10-09 |title=Troy Hunt on X: "Hi folks, yes, I'm aware of this. I've been in communication with the Internet Archive over the last few days re the data breach, didn't know the site was defaced until people started flagging it with me just now. More soon." / X |url=https://x.com/troyhunt/status/1844136762727448644 |url-status=live |archive-url=https://ghostarchive.org/archive/R8bRB |archive-date=2024-08-10 |access-date=2025-08-16 |website=[[Twitter]]}}</ref>

~~Obeys removal requests~~ by ~~site owners sometimes of entire domains,~~

Around 31 million users were affected with their user IDs, Emails, encrypted passwords and usernames being leaked.<ref>{{Cite news |last=LeClair |first=Dave |date=2024-10-11 |title=31 million users impacted by Internet Archive data breach — what we know |url=https://www.tomsguide.com/computing/online-security/31-million-users-impacted-by-internet-archive-data-breach-what-we-know |url-status=live |archive-url=https://web.archive.org/web/20241109231711/https://www.tomsguide.com/computing/online-security/31-million-users-impacted-by-internet-archive-data-breach-what-we-know |archive-date=2024-11-09 |access-date=2025-08-16 |work=Tom's Guide}}</ref>

~~Retroactively removes (hides) material covered by robots.txt restrictions (They may have stopped doing this - also don't confuse this for the [https:~~//blog.archive.org/2017/04/17/robots-txt-meant-for-search-engines-dont-work-well-for-web-archives/ criteria for actually saving/archiving a page], I am talking about end user access to saved/archived content)

==References==

@@ Line 1: / Line 1: @@
+{{StubNotice}}
 {{InfoboxCompany
 | Name = Netflix, Inc.
@@ Line 10: / Line 11: @@
-https://archive.org/
+==Consumer-impact summary==
+[TBA]
+==Incidents==
+===Login-only items for legally dubious content (2016-present)===
+On January 13, 2016, Hank Bromley (hank_b) of the Internet Archive created a collection of uploads considered legally dubious and only viewable with an account.<ref>{{Cite web |title=Download & Streaming : Log In Required : Internet Archive |url=https://archive.org/details/loggedin?tab=about |url-status=live |archive-url=https://archive.ph/rSKdG |archive-date=2025-08-16 |access-date=2025-08-16 |website=[[Internet Archive]]}}</ref>
-https://web.archive.org/
+These uploads cannot be viewed by logged-out users and cannot be downloaded by anyone except the admins, making any of these pieces of content inaccessible.<ref>{{Cite web |title=Internet Archive Forums: Log In Required, after logging in. |url=https://archive.org/post/1092552/log-in-required-after-logging-in |url-status=live |archive-url=https://archive.ph/fFVg6 |archive-date=2025-08-16 |access-date=2025-08-16 |website=[[Internet Archive]]}}</ref>
-{{StubNotice}}
+===Archived Website Censorship===
+The Internet Archive retroactively removes or hides material covered by robots.txt restrictions.{{Citation needed}}<!--(They may have stopped doing this - also don't confuse this for the [https://blog.archive.org/2017/04/17/robots-txt-meant-for-search-engines-dont-work-well-for-web-archives/ criteria for actually saving/archiving a page], I am talking about end user access to saved/archived content).-->
-==Censorship==
+===Data Breaches (2012-2024)===
-Topics:
+On May 19, 2017, The Archive's Development Manager Katie Barrett made a blog post detailing that anyone who had created their account before 2012 had to change their password as the site had been breached with user's public information and lightly encrypted passwords being leaked.<ref>{{Cite web |last=Barrett |first=Katie |date=2017-05-19 |title=Re: User account breach {{!}} Internet Archive Blogs |url=https://blog.archive.org/2017/05/19/re-user-account-breach/ |url-status=live |archive-url=https://web.archive.org/web/20250520030556/https://blog.archive.org/2017/05/19/re-user-account-breach/ |archive-date=2025-05-20 |access-date=2025-08-16 |website=[[Internet Archive]]}}</ref>
-Login-only items for legally dubious content,
+On October 9, 2024, users on the Internet Archive got pop-ups that the website had been hacked with notifications appearing from the perpetrators at around 9PM CST,<ref>{{Cite web |date=2024-10-09 |title=Dark Web Informer on X |url=https://x.com/DarkWebInformer/status/1844123206413943274 |url-status=live |archive-url=https://ghostarchive.org/archive/ADnLW |archive-date=2024-10-12 |access-date=2025-08-16 |website=[[Twitter]]}}</ref> and an hour later Troy Hunt of HaveIBeenPwned confirmed the breach.<ref>{{Cite web |last=Hunt |first=Troy |date=2024-10-09 |title=Troy Hunt on X: "Hi folks, yes, I'm aware of this. I've been in communication with the Internet Archive over the last few days re the data breach, didn't know the site was defaced until people started flagging it with me just now. More soon." / X |url=https://x.com/troyhunt/status/1844136762727448644 |url-status=live |archive-url=https://ghostarchive.org/archive/R8bRB |archive-date=2024-08-10 |access-date=2025-08-16 |website=[[Twitter]]}}</ref>
-Obeys removal requests by site owners sometimes of entire domains,
+Around 31 million users were affected with their user IDs, Emails, encrypted passwords and usernames being leaked.<ref>{{Cite news |last=LeClair |first=Dave |date=2024-10-11 |title=31 million users impacted by Internet Archive data breach — what we know |url=https://www.tomsguide.com/computing/online-security/31-million-users-impacted-by-internet-archive-data-breach-what-we-know |url-status=live |archive-url=https://web.archive.org/web/20241109231711/https://www.tomsguide.com/computing/online-security/31-million-users-impacted-by-internet-archive-data-breach-what-we-know |archive-date=2024-11-09 |access-date=2025-08-16 |work=Tom's Guide}}</ref>
-Retroactively removes (hides) material covered by robots.txt restrictions (They may have stopped doing this - also don't confuse this for the [https://blog.archive.org/2017/04/17/robots-txt-meant-for-search-engines-dont-work-well-for-web-archives/ criteria for actually saving/archiving a page], I am talking about end user access to saved/archived content)
+==References==
+<references />