10/14/16: New feature: Added ability to submit new novels not tracked on Reddit to Novel Trackr database. Novels will need to be approved by admins.

10/13/16: New feature: Can now leave personal notes on a novel for future reference. Also users can submit new release information that isn't available on Reddit on the View Novel screen.

9/26/16: New feature: Can now set novel status in reading list to dropped/on hold/finished. Can also filter personal novel list by these statuses.

6/16/16: New feature: Email updates can now be set to Immediate delivery instead of Daily Digest on the Settings screen. When the Immediate setting is selected, you will be notified via email instantly when a new chapter comes out.

5/24/16: New feature: When re-adding a novel that was previously dropped, the Last Read Chapter information will be retrieved.

4/13/16: Moved site to noveltrackr.com. The old URL will still continue working.

4/10/16: Added 'Your Novels Default Sort Order' option to User Settings screen. Added 'Latest Release Date' to User Novel List table and adjusted mobile view. Added origin tag to View Novel screen. Added latest 5 users display box on home screen.

3/17/16: Readded 'mark last read' button to view novel releases page

2/22/16: Optimized view novel releases page. Removed 'mark last read' button temporarily on view novel releases page

2/16/16: Fixed pagination issue on mobile devices where table was jumping to page 1 automatically

1/11/16: Fixed daily email update feature.

1/5/16: Added logout button to regular menu (previously hidden on mobile devices)

11/21/15: Added green highlight on User Novels screen when the most recent chapter available is not the same as the user's last read chapter. Added Mark Read button to User Novels screen. Modified daily update emails to include links to view novel screen.

11/14/15: Thanks to a very helpful email from raishuu, a very important bug has been fixed. The daily email updates were being sent to the wrong users on the list. For example, the system was generating a list for user 1 and sending it to user 2, then user 2's list was being sent to user 3. Whoops! All fixed, sorry for the inconvenience!