aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael McVady <femtonaut@gmail.com>2023-10-26 23:38:13 -0500
committerMichael McVady <femtonaut@gmail.com>2023-10-26 23:38:13 -0500
commitf4ee41187b5940b62b84de7430ae49a68f5e546f (patch)
tree893ed0a2b272cdd7c29df0d69fc1cb3386405618
parenta997ec6727b467fd72510a56bfe7a67eb04dbcf9 (diff)
Update `README.md`
-rw-r--r--README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index bbe943a..e207f02 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
# clog
-An attempt to reimplement flog, using the [kore.io](https://kore.io) framework.
+An attempt to implement a blog in C, using the [kore.io](https://kore.io) framework.
## Running
@@ -43,14 +43,14 @@ Use `psql` and load `db/db.sql` for models,
3. pagination
4. HTML form for edits
5. Make <h1> first class markdown citizen
-6. Remove JSON API?
+6. ~Remove JSON API?~
7. ~use sha256 hash to check kore blob~
8. Have `tests.py` load and drop database.
9. ~Refactor URLs and HTTP calls in tests `tests.py` to reduce copy-pasta~
10. Get rid of `requests` dependency in `tests.py`
11. Fix `PATCH` redirects?
-## C?
+## But using C in 2023 is dangerous?
* https://chromium.googlesource.com/chromium/src/+/master/docs/security/rule-of-2.md
* https://verdagon.dev/blog/when-to-use-memory-safe-part-1