Aishwaryasri15
commented
6 months ago Upon further review and discussion, we have realized the necessity of breaking down the implementation of the anonymous posting feature into smaller, more manageable subtasks. This approach will allow us to address the complexities of the feature more effectively and ensure a smoother implementation process.
For that we have created issues to handle front end and back end separately.
Frontend handled in issues #12 and #24 through PR #17 Backend handles in issues #26
Elaboration: Implementing Anonymous Posting Feature
Effort: Hard - 30 hours Implementing the anonymous posting feature involves changes both on the front end and back end. It requires careful consideration of user interface design, data handling, and security implications.
Dependencies The implementation of the anonymous posting feature may depend on existing functionality related to user authentication, post creation, and user profiles. Additionally, it might require modifications to database schemas and API endpoints.
Acceptance Criteria
User Interaction: When creating a new topic, users should have the option to remain anonymous. Anonymous Posting: If a student opts to remain anonymous, their name and profile information should not be displayed in the post. Consistency: The anonymous posting feature should be consistent across all relevant views, including topic lists, individual topic pages, and user profiles. Security: The implementation should ensure that user anonymity is maintained securely, without compromising system integrity or exposing sensitive information. Responsibilities
Front End (Chaitanya): Designing user interface components for selecting anonymity option during topic creation. Implementing client-side logic to handle user interactions related to anonymous posting. Ensuring consistent display of anonymous posts in user interface elements.
Back End (Vamsi): Modifying server-side API endpoints to support anonymous posting. Implementing data validation and processing logic to handle anonymous posts. Updating database schemas to store anonymous post data securely. Implementing backend security measures to protect user anonymity and prevent data leaks.