writing.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small, intentional community for poets, authors, and every kind of writer.

Administered by:

Server stats:

322
active users

#ArchiveToday

0 posts0 participants0 posts today

Posted about it yesterday already. But it looks like archive.today shows the default page of #Apache #webserver on #Ubuntu. The alternative domain name archive.is instead redirects with a 301 - Moved Permanently to a new domain krola.org, a website apparently comparing pet rabbit species?? It's also interesting, that the redirect to the new domain responds with an #HTTP header server: nginx/1.18 (Ubuntu). Apparently, the default Apache landing page also returns the same HTTP header information on the server. Perhaps the landing page is a decoy/deflection?

Anyone on #infosecexchange has any speculations on the website?

So...For the past few days, I have been unable to use archive.today from my home internet. Loading any page on any of its domains presents me with a captcha, and solving the captcha results in me immediately being asked for another captcha in a seemingly endless loop. It's Google's ReCaptcha. I am not having issues solving ReCaptcha on any other site.

The issue seems to affect all browsers and devices on my home internet connection (Comcast, no VPN). It does
not affect my phone or laptop using cellular data.

I got the same result on my desktop and laptop using the latest versions of:
Firefox (flatpak)
Chromium (Mint deb)
Gnome Web (flatpak)
Pale Moon (tarball)

And on my phone (when connected to my home wifi) using Chrome, Firefox, and Kiwi for Android. No issue when using cellular data.

Anyone know what might be wrong?
#ArchiveToday #Captcha #ReCaptcha

Replied in thread

Continued Community Migration tips:

  • The #InternetArchive, and the independent though closely-working #ArchiveTeam are a blessing if you want your content permanently archived online. (And if you don't, they'll disable public access on request, easily, email info@archive.org) This can be self-service or through an Archive Team Project, see: wiki.archiveteam.org/

  • To save any one page at the Wayback Machine, use a URL of the form web.archive.org/save/<ORIGI;. This can be scripted or automated if you have a list of URLs, say, from a downloaded archive. I've saved many thousands of my own pages across multiple sites this way.

  • There's also #ArchiveToday, which is not a charity, is pretty opaque about operations, operators, financing, and goals, but does do a good job of capturing today's Web as it exists (IA can have ... issues with this). There is also no automated bulk-save option. You can streamline the process by generating sets of URLs to save, and clicking through those one-by-one. Depending on what you're trying to save and how motivated you are, this is also an option (and yes, I've also saved a few thousand of my own pages this way).

Keep in mind that archive sites may not be as accessible or functional as the original. For example, Google+ URLs archived at the Internet Archive carry only a subset of comments, and profile pages don't allow the listed posts to be opened.

For example, this G+ post shows only 6 of 82 comments:

web.archive.org/web/2019031921plus.google.com/10409265600415

And my G+ profile page shows posts but those cannot be opened through the Wayback Machine. Heck, you can't even determine the URLs to request archived copies:

web.archive.org/web/2019033109plus.google.com/10409265600415

What's most useful is if you can indicate on a profile / landing page where you've gone off to and people might be able to, with luck, track you down there. My G+ profile page above does so.

@jerry @evacide @micahflee

wiki.archiveteam.orgArchiveteam