Opened 3 years ago

Closed 3 years ago

#23548 closed enhancement (implemented)

Remove Onionoo's placeholder page on index.html

Reported by: karsten Owned by: metrics-team
Priority: Medium Milestone: Onionoo-1.6.0
Component: Metrics/Onionoo Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Two months ago, on July 6, we reduced Onionoo's big index.html page to a simple placeholder page pointing to the Onionoo page on Tor Metrics which basically contains a copy of Onionoo's former index.html page.

We said on that placeholder page that it will be removed in the future. We didn't say how long in the future, but I believe that most visitors of Onionoo's homepage are developers who will be able to recover from not finding the protocol there anymore.

I'm posting a branch in a bit with a commit that removes this placeholder page and replaces it with just a blank page. (Note that it doesn't just remove the index.html file, because then Jetty provides a directory listing which is not what we want.) That commit also removes all the style files, fonts, images, JavaScript files, etc. that we kept only for this placeholder page.

If two months is too soon for removing the placeholder page, let's try to schedule a better time. The branch will probably not age so quickly. We can still merge it in one month or four, if that's a better time than now.

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by karsten

Status: newneeds_review

Please find my task-23548 branch for this change. Requires not only a quick review (it's really simple, 99.99% removing stuff), but also a decision whether now is a good time to merge or not.

comment:2 Changed 3 years ago by cypherpunks

Is there a specific reason for not just redirecting users to the new page?

comment:3 Changed 3 years ago by karsten

Fine question.

There's no technical reasons against redirects.

It's just that in the past we have avoided (permanent) redirects, because we wanted people to update their bookmarks or remember the new URL. Leaving redirects in place would mean that they don't have to do that. That's why we put in placeholder pages for a limited time and hoped that most visitors would either bookmark/remember the new page or at least remember that they failed to do so when returning after the placeholder page had been gone.

But I could as well see us using a permanent redirect, maybe for another couple of months. Not sure if that helps. I wouldn't want to maintain redirects forever, though.

Open for suggestions!

comment:4 Changed 3 years ago by iwakeh

Status: needs_reviewmerge_ready

I think it's time to remove the placeholder without redirecting.

As pointed out above the usual reader of the Onionoo's protocol page should simply update their link list (they probably did already as there was never a placeholder for the old protocol.html link).
(Maybe, the 404 NotFound page should in general contain a link to

comment:5 Changed 3 years ago by karsten

Milestone: Onionoo-1.6.0
Resolution: implemented
Status: merge_readyclosed

Agreed. Merged, scheduled for deployment with the next release.

Regarding a custom 404 page, I think that goes into the same direction as putting in a manual or automatic redirect. New users will find Onionoo via Tor Metrics, and existing users will either have found the placeholder page in the past two months or recover pretty quickly and go to Tor Metrics.

Closing. Thanks for the input here!

Note: See TracTickets for help on using tickets.