Comments by "Lepus Felix" (@MasticinaAkicta) on "The Dreaded 404 - Computerphile" video.

  1. Let me share my theory about this C:\Users\Masticina\Documents\404Theory.rtf
    2
  2. Sure you can create a script that goes through all links, looks for error messages, logs them. Then have a second script/part of the script that searches that log and uses said information. How? Well you either directly mark the broken link or you only mark them broken after 3 days. And of course you still would keep checking them for if the website returns after a few days. After all, servers migrate, webhosts migrate, it is possible that a website/server is offline or not accessible for a while. You can. But should you? How much work is it? How costly will this be? Is it worth the time [people you put to work] and money to do this? Or do you accept that the web sometimes has a 404 error! You can code for almost everything. But does it makes sense time and money wise. Fixing this problem with a $20 000,- project if you don't make that money back is meaningless. And don't forget the CPU time the script will take up. I know that modern servers are powerful but again CPU/Server time costs money! Indirectly it does! But it does!
    1