From 639b183f87c6c74ca10f6b06589a0c475e7944a2 Mon Sep 17 00:00:00 2001 From: rainbow napkin Date: Wed, 21 May 2025 02:42:53 +0000 Subject: [PATCH] Edit README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0af0b45..50008d8 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ This new codebase intends to solve the following issues with the current CyTube - General Clunk - Less Unique Community Identity -Canopy intends to be a simple node/express.js app. It leverages the piped and the internet archive REST api's, as well as yt-dlp, for metadata gathering. Persistant storage is handled by mongodb, as it's document based nature inherintly works well for cleanly storing large config documents for user/channel settings, and the low use of inter-collection references within the canopy software. All hardcore security functions like session handling, CSRF mitigation, and password hashing are handled by industry-standard open source libraries such as express-sessions, csrf-sync, and bcrypt, however it IS hobbiest software, and it should be treated as such. +Canopy intends to be a simple node/express.js app. It leverages yt-dlp and the internet archive REST api, for metadata gathering. Persistant storage is handled by mongodb, as it's document based nature inherintly works well for cleanly storing large config documents for user/channel settings, and the low use of inter-collection references within the canopy software. All hardcore security functions like server-side input sanatization, session handling, CSRF mitigation, and password hashing are handled by industry-standard open source libraries such as express-sessions, validator/express-validator, csrf-sync, and bcrypt, however it IS hobbiest software, and it should be treated as such. The Canopy codebase does not, nor will it ever contain: - Advertisements (targetted or otherwise)