stupid lil thhing

rn

server

get mechanism

• close to close
• get specific pages to get specific pages,
• get the same page (endp) to view all,
• get match name to get keyword in plain text => so no viewing html (NO XSS)
  • name is filtered from select all (select three columns)

post mech

• post in either key: value or from: ldlda data: one two three four
  • post in json (stricter than your dict or obj)
• funny insert query builder
• at least automatically retrieve column names, not used much besides safety (cant trust myself type shi)

common:

• process db info funnily (and badly): get all of them every time, still have to find right key (ineff)

db

• just a lil table
• server connects to the table, then NEVER disconnects.
• autocommit

client

• form with a lot of new tech used wrongly
  • four fields. url, textbox, two numbers
• table that formats get endp
• div beside form that displays rendered markdown (using micromark) automatically = spam them every 240ms
• other stuctures outside main (FOR NOTHING)
• most terrifying stylesheet and script file ever seen

issues:

• div has to limit size with px otherwise it grows and grows

markdown:

• import with import (esm)
• lightweight(?) until i use it every 240ms
• bad frontend, no styling

desired outcome

server

• handle requests better, with pictures and all
• more modular, use more http methods
• upload documents with stuff: trees
• refactor into shorter code blocks
• use more python technologies

db

• use the linking tably to handle trees
• do more processing here too

client

• split into 4 pages:

• about where theres just info

• write page where i write

  • application looks like stackedit
  • use contenteditable divs, probably with styling
  • use md engine skillfully

• read page where i read

  • apply custom stylesheets

• view page where i view

  • use custom queries
  • search

what i can do rn

• refactor server handler, so it just do ifs then send code to other functions
• fix layout