Bug    •   5 days ago  # 21 March 2023 + 0 -
Nothing is archiving

Guest    •   9 days ago  # 17 March 2023 + 1 -
★ ★ ☆ ☆ ☆
All of sudden, when I go on the "ask me" page, it says "Login or sign up for Tumblr to ask a question. This blog allows anonymous questions." What the f***? Yeah, no, I'm not creating the 23647380th account I'm never going to use just to be able to do one thing. If this is on Tumblr's end, I sure hope the owner of Archive Today changes the anonymous asking to Google Forms or something.

Oh, also, what I wanted to ask was that NameMC isn't archiving on Archive Today anymore.

,    •   55 days ago  # 30 Jan 2023 + 1 -
Nothing is archiving

fix it    •   57 days ago  # 29 Jan 2023 + 0 -
it keeps randomly giving me a spinning circle

Fixthewebsiteplease    •   172 days ago  # 6 October 2022 + 0 -
The website isn't loading

.    •   192 days ago  # + 0 -
Things are taking forever to archive

.    •   201 days ago  # + 0 -
Getting "problem loading page"

Guest    •   339 days ago  # + 0 -
★ ☆ ☆ ☆ ☆
When I go to the site, all I see is a placeholder page with this message:

"Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required.

For online documentation and support please refer to nginx.org.
Commercial support is available at nginx.com.

Thank you for using nginx."

This has neem the case for over a month, now. I reported the problem to Archive.Today on March 21, it is now April 21, and I had been seeing that placeholder page for a while, at the time.

For a while, I found that I could bypass the problem by using an ip anonymizing proxy, which was semi-convenient, but also a little bit damning. The guy running the archive had a working site. He was just playing games with some of the would-be users. A few hours after I carelessly shared the workaround in public with somebody else who had run into the same problem, I started getting error messages when I used it. All of a sudden, the proxy couldn't connect to the archive.

Gosh, almost as if somebody had read the comment, which was in a discussion started by the owner of the archive, and had decided to have his site being invisible to proxies just to sabotage the workaround. At this point, over a month has passed, the clown running the archive has still not bothered to reply to my problem report, and this doesn't look like mere breakdown. I've long since come to the conclusion that some of us, as users, are being messed with by the owner of Archive.Today, who seems to be getting some sort of twisted amusement out of this.

Even before I started seeing that placeholder page, I had been getting error messages when trying to connect, so this has been going on for a long time.

He might try to defend his failure to respond to the problem report by saying something about DDOS attacks, but that's not going to cut it. The conversation in which I reported the problem (and then made the mistake of sharing that workaround) took place on a social media site that has been working just fine, and loading with no particular delays, ruling out the possibility that its servers have been under any particularly heavy load. The owner saw that report. He just chose to ignore it, apparently because he's having fun by messing with his users.

April 1 was almost three weeks ago, at this point. If this ever had been amusing, it would have ceased to be so, a long time ago. At least two of us have tried to reason with the owner, and were nice and supportive in the beginning, but in the end, there was no way to get around the conclusion that we had been dealing with a jerk, the whole time, and that reason wasn't going to work on him.

My advice to anybody reading this is to not bother with Archive.Today or any future project started by its owner. He has shown what kind of person he is - a man without honor, one in whom one shouldn't put any faith, now or ever. The Internet needs a few good archives, but Archive.Today (also known as Archive.is) isn't one of them, any more.