Wayback Machine: How to close your blog the right way!

As we as a whole know there is this new security creature in Europe: GDPR. Xohop – Jasa Pembuatan Toko Online

For all us content makers/bloggers out there giving their administrations to Europeans a hustle started: We needed to adjust to the new administrative. Continuously in light of the dread, that on the off chance that we fuck it up we will be Xohop – Jasa Pembuatan Toko Online looked with tremendous punishments.

So I looked trough my sites: Remove Facebook Like Button, Remove examination, Add protection articulation, Add treat select in/out … . the rundown goes on.

I wound up at a point where I got so frantic that I was near taking the greater part of my stuff disconnected :/

In any case, at last I didn’t. I chose for the center path: Xohop – Jasa Pembuatan Toko Online For a few activities it’s justified regardless of the hustle and for others not.

Xohop – Jasa Pembuatan Toko Online Website

 

Source: https://en.wikipedia.org/wiki/Schr%C3%B6dinger%27s_ca

One anticipate I jettisoned was datenschutzhelden.org. You currently perhaps pondering: Why is he connecting to a dead page?

In reality the page isn’t totally dead! I don’t have it any longer and it just lives in the wayback machine (WBM). Every one of the solicitations to the space get sent to the WBM.

As I don’t claim the WBM and none of the substance is served from my servers I see myself being agreeable with the GDPR by giving the hazard over to another person. (On account of the Internet Archive <3)

By being disconnected and online in the meantime we have the Schrödingers site conundrum 😛

Yet, fun aside: I’m not an attorney and do not understand if that truly tackles my issues with the GDPR as regardless I claim the space. So observe this article as a thought for yourself and not as lawful restricting articulation.

The initial segment revealed to you why I chose to go that way and what the final product will resemble. In the second part you will become more acquainted with how you can do likewise.

Step by step instructions to file your site yourself


Since the WBM just spares the pages that are asked for straightforwardly through their inquiry, normaly just the principle few pages of your blog get spared. (Or then again you have very some manual work to do via looking through the entirety of your subpages).

That resembles an issue one could computerize 😀

As I would not like to include all my subpages physically I made an apparatus for doing as such:

The ‘Save to web.archive.org’-Tool

By following a simple set of instructions (next block) Xohop – Jasa Pembuatan Toko Online you can automatically scrape your page for all subpages and add them to the WBM. (With all request being proxied to circumvent rate limits).

Using the ‘Save to web.archive.org’-Tool

Installation

I assume you have already installed go. (Go installation manual)

Dependencies

Download the dependencies via go get

Execute the following two commands:

go get -u github.com/simonfrey/proxyfy
go get -u github.com/PuerkitoBio/goquery
Download tool

Just clone the git repo

git clone https://github.com/simonfrey/save_to_web.archive.org.git

Execution

Navigate into the directory of the git repo.

Run with go run:

Please Replace http[s]://[yourwebsite.com] with the url of the website you want to scrape and save.

go run main.go http[s]://[yourwebsite.com]

[NGINX] Redirecting your domain Xohop – Jasa Pembuatan Toko Online

It’s as simple as adding a single magic line to your site config:

Please replace http[s]://[yourwebsite.com] with your own website

return 301 https://web.archive.org/web/http[s]://[yourwebsite.com]$request_uri;

Now all the request to your website get forwarded to the WBM. It even keeps your old links alive.


Hope I was able to help you a bit with this article. See your pages soon in the WBM 😀

  • Simon Frey

Feedback is very welcome via HackerNews <3


Updates

12.06.2018 – 11:50

Because of a discussion on HN I want to clarify: Xohop – Jasa Pembuatan Toko Online datenschutzhelden.org was NOT closed because of GDPR. We already closed it earlier (february 2018), mostly because of time issues.

But after the end of the project, the page was still up and running as archive on my server. (And me still being fully responsible for it).

In march I decided to move it into the WBM to don’t have it on my servers anymore.(And hopefully keep legal issues away)

Leave a Reply

Your email address will not be published. Required fields are marked *