anipiano/anipianolist

"ok guys we need to make the myanimelist of all piano arrangements" – fruit 2022

anipianolist's Issues

Views for IAM

To only allow login (and disable db-based signup) via OAuth2 solely, we need to manually set views and URL routing.

Hopefully no forms needed.

Fix environment variable readings

this diff shows I removed the wrong line 😨

33ef4d6

need to fix

Validators for DBMS video IDs

We need custom validators for video IDs in DBMS

• at least one field filled
• alphanumeric/numeric
• exactly n characters

Anime master plan

it is time for a master plan only an anime protagonist could devise as fruit threatens to private 50% of videos

1. Groups - admins, moderators, db staff =>
   a) Badges
   b) Link user to YouTube channel
2. Database management page => CRUD (staff only)
   a) Staff-only: per channel => from YouTube playlist IDs, grab video IDs + metadata => into psql
   b) User-suggestable: per YouTube video ID (11 alphanumeric characters), Bilibili CN video ID (12 alphanumeric characters), Bilibili TV video ID (10 numeric characters) (log in DB management page)
   c) Between the 3 types of video IDs, there can be a linked relation as they are all distinguished by their Entry ID
   d) Stores sheet music, social media locations by relation to channel or video (same integration as platform video IDs)
   e) DB relation between Entry ID and Creator ID such that it can then be subsequently linked to an anipianolist account User ID if that person is on anipianolist
   f) Merge and batch add/delete
3. User reviews and ratings
   a) Basic fields/form setup
   b) Reactions/comments (reddit-style hierarchy)
   c) Review ID with one-to-one relation with Entry ID
4. Search T_T
5. Profile/list
6. DDoS prevention, captcha, ToS ack
7. Knowledge base

PFP upload verification

Django already automatically verifies image mimetype, but does not place a limit on upload size.

Both client-side file limits (5MB) (for user-friendly clientside error handling) and server-side file limits (20MB) (for security) should be implemented.

Enhance Contributor Onboarding and Environment Flexibility

Enhance Contributor Onboarding and Environment Flexibility

Issue Type: Enhancement

Description:
When new contributors join our project, it's crucial to ensure a smooth onboarding experience. Currently, setting up the development environment and configuring necessary environment variables can be a stumbling block for newcomers, leading to frustration and wasted time. Additionally, some contributors might not have immediate access to a specific database system, resulting in unnecessary hurdles.

Proposed Solution:
To address these challenges, we propose implementing the following enhancements:

1. Alternate Environment Values: Provide clear and concise documentation detailing the required environment variables and their alternate values. This will enable contributors to quickly set up their environment without struggling with configuration issues or errors. By having a predefined set of alternate values, contributors can start working on the project faster and concentrate on the actual development tasks.

2. SQLite Integration: Introduce support for SQLite as a fallback database option. In cases where contributors do not have access to specific database credentials, they can opt to use SQLite for local development. This will eliminate the need for immediate external database setup and empower contributors to work on the project right away.

Benefits:

• Smooth Onboarding: New contributors will have a streamlined onboarding process, reducing frustration and ensuring a positive initial experience.
• Time Savings: By providing alternate values for environment variables, contributors can avoid spending unnecessary time on environment configuration, leading to increased productivity.
• Flexibility: The inclusion of SQLite as a database option gives contributors the flexibility to work without external dependencies, promoting a more accessible development environment.
• Higher Contribution Rate: Removing setup barriers and offering a user-friendly environment will likely encourage more contributions, ultimately benefiting the project as a whole.

Tasks:

1. Document the alternate values for environment variables in the project's README.
2. Implement SQLite integration and update relevant parts of the codebase to support this option.
3. Update the project's contribution guidelines to include information about using alternate values and the SQLite option.

Enhance the contributor onboarding experience and making the project more accessible to a wider range of Devlopers

request.get_username

get_username() fetches usernames which have been invalidated. See top-right corner

Low priority and zero impact on services, but good first issue.