jason-kuang cse312 issues

jason-kuang / cse312

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

develop -> main

#28 jason-kuang closed 3 years ago
0
Postgresql

#27 jason-kuang closed 3 years ago
0
Coding up the forum

#26 alderon07 opened 3 years ago
0
[Security]

#25 lexianzh opened 3 years ago
1
Check site for Private content must be private (Do not assume users are using your site as intended. Your 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)

#24 lexianzh opened 3 years ago
0
Check site for 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)

#23 lexianzh opened 3 years ago
0
Check site for SQL Injection (Use prepared statements)

#22 lexianzh opened 3 years ago
0
Check site for HTML/JS Injection (This is considered a severe vulnerability!)

#21 lexianzh opened 3 years ago
0
[Requirement 5] Live interactions between users via WebSockets (Cannot be text)

#20 lexianzh opened 3 years ago
1
Users interact in real-time via WebSockets. This cannot be raw text (ie. you can’t build a chat app like we saw in lecture)

#19 lexianzh opened 3 years ago
0
[Requirement 4] Users can share some form of multimedia content which is stored and hosted on your server

#18 lexianzh opened 3 years ago
1
Requires use of a database in Docker to store uploads (Services such as FireBase are not allowed)

#17 lexianzh closed 3 years ago
0
[Requirement 3] Users can send direct messages (DM) to other users with notifications when a DM is received

#16 lexianzh opened 3 years ago
1
When a DM is received, the recipient must be notified in real-time and given an option to reply

#15 lexianzh opened 3 years ago
0
From the previous requirement, each user is able to “see” other users. There must be an option to be able to DM users where you can see them.

#14 lexianzh opened 3 years ago
0
[Requirement 2] Users to see all users who are currently logged in

#13 lexianzh opened 3 years ago
0
[Requirement 1] User Accounts with Secure Authentication

#12 lexianzh opened 3 years ago
0
OAuth is allowed (Report required!), though you still have to store a profile for the user with their setting(s) on your server

#11 lexianzh opened 3 years ago
0
Requires use of a database in Docker to store uploads (Services such as FireBase are not allowed)

#10 lexianzh opened 3 years ago
0
Each user must have at least 1 setting that they can adjust. This setting must persist across sessions. For example, if a user logs in and changes this setting it should still be changed when they log off and log back in from a different device

#9 lexianzh opened 3 years ago
0
Each user must have at least 1 setting that they can adjust. This setting must persist across sessions. For example, if a user logs in and changes this setting it should still be changed when they log off and log back in from a different device

#8 lexianzh opened 3 years ago
0
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 (If you completed DMs then this is covered)

#7 lexianzh opened 3 years ago
0
Lexi's Issue

#6 lexianzh closed 3 years ago
0
Video Presentation

#5 jason-kuang closed 3 years ago
0
Live interactions between users via WebSockets (Cannot be text)

#4 jason-kuang closed 3 years ago
0
Users can share some form of multimedia content which is stored and hosted on your server

#3 jason-kuang closed 3 years ago
0
Users to see all users who are currently logged in

#2 jason-kuang closed 3 years ago
0
Users can send direct messages (DM) to other users with notifications when a DM is received

#1 jason-kuang closed 3 years ago
0