Hello Hexdee, greetings to you. I have added the following improvements

• Added comments in the code to improve readability
• Added more logic in the like function
• Added disLike function to allow viewers to downvote the post
• Added getAllPostsByUser` function to retrieve all posts created by a specific user
• Added SerachPost function to allow viewers to search for posts using their title or content
• Added getStatistics function that returns the overall statistics of the posts in the canister such as total number of posts, total unique authors, most liked post, and the most disliked post.

Below is my PR, have a great day

I have added a few changes to your project

• added init function to allow deployer to initialize the admin on deployment

• added the isAdmin function to check whether the caller is an admin

• added checks in the addLanguage, changeLanguageTitle, deleteLanguage, addTopic, updateTopic deleteTopic, updateTopicStatus functions to only allow the owner to call these functions

Hello Galien, great implementation of your project, I have added a few changes to your project.

• Modified the userStorageProfile map to use Principal IDs as the keys. This brings in a unique way to let users create accounts using their Principal IDs, which is a unique way to identify users on the Internet Computer

• Modified the createUserProfile function to only restrict any user with the anonymous Principal ID 2vxsx-fae from creating an account. This ensures that every user has a valid and unique principal ID before creating an account.

• Modified the deleteUserProfile and updateUserProfile functions to allow only the owner of the account to delete and update the account respectively. this brings in some sort of decentralization where a user has full control over their information

• Modified the unfollowProfile and followProfile functions to implement the new logic of Principal IDs for identifying user accounts.

Below is my PR. Feel free to check it out. Wish you a great weekend.

Hello chigozie, great implementation of your project. I have made the following changes.

• Added checks in the updateEvent function to allow only the owner of the event to update its details
• Added a check in the attendEvent to allow attendance only if the maximum number has not been reached.
• Added getMyAttendedEvents function. This returns all the events that have been attended by the caller of this function.
• getSpecificEvents function that returns either events that have passed or those that are still running depending on the condition supplied
• Added add Review function that allows the user to leave a review on an event only if they attended it
• Added getAllEventsByOrganizer function that returns all the events that a certain organizer registered

i made the following changes.

• added comments to improve the readability

• add init to initalize some parameters on canister deployment

• added checks in the deleteSaving , withdrawSaving functions to only allow the admin to call these functions

• added a functionality to allow the owner to add a list of whitelsited Principal IDs that are allowed to withdraw the savings other than the admin.

• added a timelock functionality in the withdrawSaving function. This restricts withdraw until the time specified has elapsed

Hello, I have made a few changes to you code in the index.ts file

• added comments to improve the readability
• added init function to initialize the admin on deployment
• Emails and passwords are common login methods in web2, in web2 there is a notion of logging in with addresses and IDs, I have modified the login function to let the user login with their Principal ID, which is a unique identifier for every user on the Internet Computer.
• added checks in the deleteUser function to allow only the admin to delete accounts
• added a new function reclaimAccount. This allows the user to reclaim their old account by providing the secret associated with the old account. Once they have reclaimed the account, they will be able to login with their new Principal ID
• modified the userStorage map to use the Principal IDs as the key. this provides a unique and scallable method to identify user accounts

Hello JoeEdoh, I have made a few changes to your codebase.

• Edited the constructor function to allow the deployer to specify the id of the lottery canister admin. This id will be stored in the lotteryAdmin variable

• Added checks in the startLottery, endLottery,deleteLottery,payWinner functions to only be called by the admin of the lottery canister

• Added a variable previousWinners to store information about all the previous lottery winners, like their principal IDs and the amount that they won.

• Edited the payWinner function to also record the principal Id of the winner and the amount in the previousWinners array

• Added the getAllPreviousWinners function to retrieve all the previous winners of the lottery and the amounts that they won.

Below is my PR.

Hello hiatus, I have made a few changes to your project.

• Modified the userStore map to use Pricncipal IDs of users as keys. This provides a more secure and unique way to store user accounts

• Modified the createUser function to allow users create accounts using their Principal IDs rather than random Ids. This removes the need for the user to supply the username and password. Also Users that call this function anonymously with the Principal ID 2vxsx-fae wont be able to create accounts.

• Modified the topUpUserBalance function to automatically track the user account that wants to top up their balance. Another function can be written to allow users to top up balances for other users

• Modified the createEvent,deleteEvent, topUpEventTickets,purchaseTicket,getTicketsOrganizer,getTicketsAttendee functions to automatically track the user account of the Principal ID calling these functions, and thus removes the need for the user to supply their password and username every time.

• Added migrateAccount template function. When the user calls this function, they need to specify the Principal ID of the old account and the password associated with it. Once they are verified, user details of the old account will be migrated to a new account that is accessed by the Principal ID that called this function.

Below is my PR, feel free to check it out. Have a nice weekend

Hello bezat, great implementation of the project. I have made a few changes to your codebase in the index.ts file

• added comments to improve the readability

• added the init function to allow the deployer to specify the owner principal on deployment

• added several functions addSpender and deleteSpender that allow the owner to specify Principal IDs that are allowed to create payments

• added some helper functions isAdmin and isSpender

• added checks in the setBudget function to only the owner to set the budget

• added checks in the create payment function to allow only the owner and the spenders to create payments

• added checks in the deletePayment function to only allow the owner to delete a payment

• added checks in the updatePayment function to only allow the owner to update a payment

• added checks in the setBudget function to only allow the owner to set the budget

• Deleted the function that was not used in the codebase

Hello, Mujhtech, here are the few changes and functions that I have added to your codebase in the index.ts file

• init function to allow the deployer to specify the owner of the contract on deployment
• addOrganizer function allows the admin to add more event organizers
• deleteOrganizer function allows the admin to delete an event organizer from the app
• isOrganizer function to check whether the caller of the function is among the event organizers or an admin
• Added checks in the createEventTicket function to only allow the admin and event organizers to create tickets
• Added checks in the deleteEventTicket function to only allow the admin and event organizers to delete tickets
• Added checks in the buyTicket so that event organizers and admins cant buy the tickets they are selling
• Improved the documentation of the whole codebase

Hello Ubinix, I have added the following functions and changes to your project

• init function to allow the deployer to initialize the admin of the app on deployment
• addMember function allows the admin to add a new trusted member. These trusted members will help the admin to manage the app and ensure that only the trusted entities can update information in the app
• deleteMember function allows the admin to remove member from the trusted members
• getAllTrustedMembers function returns an array of the Principal IDs of the trusted members
• Modified the deleteTuna, recordTuna, and chnageTunaHolder functions to only allow either the admin or trusted members to call them successfully. Below is my PR. Have a nice weekend.