hoodedice/notes

Hi there 👋

notes's Issues

minify html

right now the way ejs is written is easy to read and easy to modify.
html-minifier is probably the best way to go about it.

Remove ID columns from MySQL and use public keys on UNIQUE columns

Remove all unnecessary npm packages (without making much change to the code)

eg: 'passport'

Minor: Parallelize generateUUID()

Notice that getCurrentDate() and getRandomIdentifier() are independent of each other. They aren't very expensive functions, so doing this fix won't give a huge performance gain but would still be a nice to have in the long run /shrug

Use toISOString() for Date

toISOString() along with string.slice will get rid of the convoluted code in getCurrentDateTime() and getCurrentDate()

add a routine for getting a note from the database

Rewrite the database

So the database needs to be rewritten to provide for some extra features that will be implemented later on. For now the design calls for

• A Trigger that runs a Stored Procedure that updates latest_version_id with the number of the latest revision.
• Connect to the database from within the application.
• Use environment variables.
• test the database (this can happen after I set up more of the routes in the application)

"module" that can generate random strings to be used as UIDs

Since every note has a unique author, we don't need our UIDs to be GUIDs, so to say. They just need to be unique vs the other UIDs by the same author.
Thus, my first attempt will be to make the UID as small as possible in terms of chars. I think 6 (42,180,533,641 possibilities per user) should be a fine length (imgur manages fine with 7)
As for uniqueness, I realized that copying twitter's snowflake system (" The full ID is composed of a timestamp, a worker number, and a sequence number") might be best. Instead, I will just affix a YYMMDD to the start of the UID, bringing the char length to 12

add a routine for inserting notes into the database

Check if passwords match

JavaScript code (or see if possible without) that checks if both the passwords on the registration page match.

Move to Apache Cassandra

Moving from mysql to cassandra because performance (not like I have that many consumers of this anyway)

server timeout

Increase time of response after 5 login attempts for a client. See into doing this in such a way that doesn't stall the server.

Make application run at all (after npm packages were removed).

as long as it runs locally that is fine for now

split concerns across files

New Express-Session with redis backend for sessions

Add sessions support via connect-redis and express-session