• Support older browsers by using XMLHttpRequests
• Create one method for api calls

An user should be redirected to the page they wanted to go to after logging in

There aren't yet any events for:

• Site Deleted
• Title Updated

This software is

1. quite old (especially regarding TypeScript/JS coding conventions)
2. not well suited for larger collections (no search, no tagging etc.)
3. barely updated (dependencies are out of date, some of them no longer supported etc)
   • I think this server doesn't work with newer versions of the website-scraper node module, so it's still on an older version

While it still works (I've had it running for 4+ years), it feels like it's time for an overhaul. The following could be good steps:

1. Creating a better frontend (the code in browser.js works, but is a mess)
2. Creating a docker (compose) configuration that just works to simplify installation
3. Maybe switch to a database instead of just storing everything in a JSON file (not sure I'll do this, as it complicates setup etc.)
4. Updating the downloader code to use newer website-scraper versions

2 & 4 should be possible without major rewrites, the others are somewhat more involved.

Maybe it also makes sense to rewrite the server in Go because I like it better, but I'm not sure if there's a good website-scraper-like module for Go. I actually tried writing something like that that started a chromium browser and used SingleFile to download pages, but it didn't work that well.

I'm not sure when (or if) I'll work on this.

Since this isn't done in the class, it is done individually by all routes that need it.
This redundant code should be refactored

When clicking on the title in the table view, redirect to a site with an iframe so that the header is still displayed

Add an option to use the website-scraper-phantom module to download pages.

This can might be accomplished by using the module if it is installed (users just have to install the module & the normal install doesn't fail if their platform is not supported by PhantomJS)

Have you considered using webarchive format and or pdf for archiving? .war is pretty standard now

Improve the "details" page:

• Link to the original url instead of displaying it in an input box
• Link to the saved page instead of just displaying it

Right now, any client can connect to the server to receive events. This should be restricted to people who have an api token or the right cookie.

How to reproduce: register events and enter io.connect() in your browser console

There is no api route for changing the title of a site

Add an option to use cookies. They should be added to the request option in the website function in tools/download.ts.

This would also require to change the 'New Entry' form and the files that accept input from this form.

Add an editor(link to it from the details page) for html pages so they can be edited from the webinterface

I am not sure what you what to know so:

I get this:

Error 500
ENOENT: no such file or directory, open 'public/s/content.json'

Have this installed:

npm -v
5.8.0
nodejs -v
v8.11.4

and run this to start

sudo npm start production

A route that deletes a saved site

Use the API to delete & update sites with client side javascript

If an operation is running, the title on initial page load is "(1) (1) Title", while it should be "(1) Title"

The layout of the details page looks horrible in mobile browsers.

As this server is for archiving all types of websites, it should also support downloading only videos. To specify whether to download only the video or the website with the video, the url could be given as video:https://youtube.com/watch?v=..... or with another option on the new page.

This features would use youtube-dl because it supports a wide range of sites.

I would be great to have an option (either global or by site) to allow unauthentified acces to website (and also potentially list of website)

Main problem is that this would need to distribute the call to the auth middleware to the url handlers or another equivalent solution

When visiting a downloaded website that has HTML content but a .php or .md extension, the server assumes the wrong content type. Browsers usually display the file wrong.