-The private account owner should be notified of the follow request
-The owner should be able accept or reject the request
-If accepted, the requestee should be notified that their request has been accepted

Remaining

• Hide comments that the user has reported.
• Hide all comments which do not meet the users abuse filtering settings.

When deleting a post from the discover page it redirects you to the url rather than processing the request

Should be able to post image without text. The image name is no longer displayed when it is selected

Create a modal that shows a full post thread when a comment is clicked on by a user.

TODO:
Design modal for viewing post thread
Populate view with thread content

At the moment, blocking a user works. However, there are some parts of it that need to be improved.

• Once user A has blocked user B, they should not be able to follow them again until unblocking them.
• Once user A has blocked user B, neither should see the other persons content on their timeline.
• Once user A has blocked user B, any notifications from user A to user B should be hidden.

• More.

UI

• Nicer widget design, ensure the photos are laid out nicely in a grid inside the widget.
• A UI for viewing the photos.

Functionality

• Load all undeleted photos, order of date posted descending. Should see the most recent in the widget.
• Need a way to enlarge a photo, potentially a model?
• Need a way to go through all photos ever... Potentially a next and previous arrow on the modal to keep going through photos or even a page with all the photos.

Improve UI

• The search is a bit clunky and big atm. We Don't need borders and shadows, make it a nice small text box that blends into the Nav bar.

Functionality

• Make sure search includes hashtags, users, etc.
• If possible, add an Ajax search dropdown.

Similar to subscriptions, we need to create a REST API for Voting on posts so we can call it via AJAX.

Methods Required:

• Store (Pass type(up/down) as a param)
• Delete (Delete a vote).
• Get all votes for a post.

Unauthorised users can only access the Discover page by searching for a specific category, instead of directly navigation to the page using the navigation bar icon

Due to changes made on how posts are categorised, recommendations must now use categories instead of tags

The page should just say that there are no posts for this tag if the user goes to a tag that doesn't exist. Probably should create the tag.

-Users should be taken to post thread, similarly as they would do if they click the comments button

The notification system was setup to store a sender, receiver and a comment that a notification is related to. However notifications may be triggered through other events, such as a follow, in which there is no associated comment.

This page is essentially the core of the machine learning section and should contain almost every settings concerning the algorithms.

UI

• Improve the design of the page, primarily the two safety and privacy group headings.
• Incorporate easy UI components such as the slider and toggle switch to make turning settings on and off easy.

Functionality

• Abuse detection
  • Algorithm type (Binary or Threshold).
  • Threshold adjustment if threshold method is chosen.
• Content Recommendation (DONE)
• Content Filtering
• Reputation Scoring

Currently users are not able to change their password

Update voting controller to check whether the post being voted on is a recommendation. If it is, update the response field in the content_recommendations table.

Please setup a REST API for subscriptions. Have a look at the post example. You would need to validate all requests!

Ideally you'd only need the following methods:

• Store (Subscribe)
• Delete (Unsubscribe)