Anonymous feature:
The anonymous feature was initially planned for sprint 1, but we had issues with integrating the backend changes to the frontend. In sprint 2, these issues were resolved and we have fully integrated this feature. Additionally, the task of adding tests to this issue was moved to sprint 2 and this has been completed successfully.

Emoji reaction feature:
This feature was initially planned for sprint 1, while in print 1 we were able to complete the frontend portion of this feature, there were many issues faced with the backend, haunting us to be able to test. During sprint 2, we re-factored a lot of the codebase, focusing on three main components, (1) successfully re-vamping the front-end design of the emoji implementation, placing it in a more accessible area (before, it was just three buttons in an arbitrary location under the post), while at the same time, changing the styling of the buttons, making them closer to the styling of the rest of the page (2) finalising the back-end and connecting it with the front-end. Unfortunately, on this step, we were unsuccessful in making it work. We followed a number of different approaches, including creating custom javascript files, custom routes, and creating our own plugin which we later installed using the administrative dashboard of NodeBB. Nonetheless, we underestimated the time and resources implementing this feature fully would take, with Talal moving on after helping me with the front-end to working on the back-end of the "Marked as Solved" feature, resulting to me working on the back-end of the emoji feature by myself. While doing so, I made significant progress, but issues with the routing, made it impossible for me to complete it. (3) creating a comprehensive test suite for the back-end. We created a comprehensive test-suite, covering a lot of different scenarios related to the back-end, but the inability to properly setup the routes, makes testing impossible, despite having written the actual test-cases.

Solved feature:
The solved feature was initially planned for sprint 2. The goal was to implement this feature completely. Due to issues we had with delays in our sprint 1 goals, we found that our team had to mainly spend time working on implementing our sprint 1 features. This meant we did not have much time to work on this feature as a time. While we successfully implemented the frontend of this feature, we had many issues with the backend. The backend feature primarily faced issues with the routing. While the logic seemed correct, there may have been minor errors such as syntax that were missed, even with meetings that were conducted with teammates and the professor. Moreover, the task was taken on alone at the start of sprint 2 as focus was also on completing leftover tasks from sprint 1 features, which delayed progress in effectively finishing the backend and then the testing. For reference, PR #29 would show the commits made and the progress in attempting to finish it. Should there be another sprint to complete this, we would redirect the task to two members to foster collaboration and effectively exchange ideas on how to tackle the issues as well as being able to complete it quicker.