Project Phase 3 Tasks

[ncumbo]

Functionality

• User Accounts [WILL CHECK] Users must be able to register accounts and log into their account. Once logged in, each user must see at least some content and functionality that is specific to them and cannot be accessed by other users The actions taken by the user must persist with their account. For example, if a user logs in and follows another user, they must still be following that other user when they log off and log back in from a different device OAuth is allowed (Report required!)
• Live sharing of multimedia content between users [NICK CHECK] When content is shared, that content is associated with the user who posted it This can be as simple as adding their username next to the post
• Users can "vote" and comment on user-submitted content [TIM] Each user can only vote on a piece of content once Comments must be associated with the user who made the comment
• Users can friend or follow other users [WILL] There is a way for users to mark other users and have something different happen based on this marking This functionality must be specific to each user and it must change their experience when visiting your site Example, all posts from users you follow are displayed before all other posts
• Users can send direct messages to other users [NICK] Direct messages (DMs) must be private and only accessible to the 2 users involved in the communication Direct message must be received in real time if the recipient is currently online (Eg. they should get a notification that they have a DM as soon as it is sent) If the recipient is not online when the DM is sent, they must be able to view the DM the next time they log into the app

Security

• HTML/JS Injection (This is considered a severe vulnerability!)
• SQL Injection (Use prepared statements)
• Securing user accounts (If passwords are stored they must be salted and hashed properly. There must not exist a practical way for a user to authenticate as another user)
• Private content must be private (Do not assume users are using your site as intended. You server must check that the user is authenticated before sending them private content even if your site doesn’t offer a way to request that content without being authenticated)

[willlenore]

Will Tasks:

• Look into OAuth
• Add specific users posts to their profile page
• Add dropdown for edit profile options (instead of always displayed)

[ncumbo]

Everyone needs to download and set up redis (steps 1-3)

• https://www.digitalocean.com/community/tutorials/how-to-install-and-secure-redis-on-ubuntu-18-04
• passwd - foobared

chat css & html structure:

• https://bootsnipp.com/snippets/1ea0N

New Documentation:

• Redis (WebSockets on Chat Server)
• Django Channels
• Reconnection WebSockets js file (MIT License)

We will use a channel layer that uses Redis as its backing store. To start a Redis server on port 6379, run the following command:

• docker run -p 6379:6379 -d redis:5

[ncumbo]

1. User Accounts [100% COMPLETED]:

• Login/Logout
• Specific functionality only accessed by them: User edit account page

2. Live sharing of multimedia content between users: [90% COMPLETED]
   • Share text/photo to all accounts on feed page
   • Associates username of person for each post

MISSING: NOT WS based

3. Users can "vote" and comment on user-submitted content [100% COMPLETED]:

4. Users can friend or follow other users [100% COMPLETED]:

   • Follow/Unfollow functionality
   • You can see who your following and go to that persons profile

5. Users can send direct messages to other users [80% COMPLETED]:

   • DM system works via WS
   • Read receipt functionality
   • Stored in DB and persists after close

MISSING: Same conversation per all accounts

6. Security [100% COMPLETED]

   • HTML/JS Injection
   • SQL Injection [DJANGO]
   • Secure user acts [DJANGO]
   • Private content being private

7. Docker-Compose [100% COMPLETED]

   • Tested and Works