Delete unnecessary notes (at least for now).

I also deleted the database which is now stored in the Emacs config
directory.

2020-06-12-19-20-15.org

@@ -1,47 +0,0 @@
-#+title: File encryption with GPG
-#+author: "Gabriel Arazas"
-#+email: "foo.dogsquared@gmail.com"
-#+date: "2020-06-12 19:20:15 +08:00"
-#+date_modified: "2021-04-05 15:40:10 +08:00"
-#+language: en
-#+options: toc:t
-#+property: header-args  :exports both
-#+tags: tools.security
-
-
-GPG is mostly used for public-key cryptography, allowing you to publicly communicate with the recipient.
-Using GPG boils to generating a key-pair, managing them, and signing and receiving encrypted messages from others and/or to yourself for security purposes.
-
-
-
-
-* Basic usage
-
-A GPG key-pair is made up of two things: the public key and the private key.
-The public key can be shared... to the public while the private key should be guarded in secret.
-
-#+begin_src shell  :results silent
-# List out the available keys.
-gpg --list-keys
-
-# Generate a new key-pair.
-gpg --full-gen-key
-#+end_src
-
-
-
-
-* Encrypting and decrypting files
-
-Encrypting and decrypting files are one of the main points of GPG.
-
-#+begin_src shell  :results silent
-# This will encrypt a file and generate an obscured version of it at <FILE>.gpg.
-gpg --recipient <EMAIL> --encrypt <FILE>
-
-# Decrypting is almost the same process.
-gpg --recipient <EMAIL> --output <FILE> --decrypt <FILE>.gpg
-#+end_src
-
-You can make more secured versions of encrypted file especially when you intended it to send it to a particular recipient.
-For example, you can encrypt your file with your private key and the public key of your recipient and only both of you know how to receive the file.

2020-06-19-20-30-23.org

@@ -1,22 +0,0 @@
-#+title: Writing clean code
-#+author: "Gabriel Arazas"
-#+email: "foo.dogsquared@gmail.com"
-#+date: "2020-06-19 20:30:23 +08:00"
-#+date_modified: "2020-09-09 05:19:39 +08:00"
-#+language: en
-#+options: toc:t
-#+property: header-args  :exports both
-
-
-Code should be readable, simple, and concise.
-There are a few things to consider when writing code.
-
-- When naming stuff like variables and functions, be clear and concise.
-  Furthermore, if applicable, imply its type.
-  For example, when the variable holds an array, you can append ~_list~ to its name (e.g., ~grade_list~ vs ~grades~).
-  If it's a boolean, you can prepend the name with ~is_~ or ~has_~.
-
-- Use whitespace properly and consistently.
-  For example, in Python, spaces are preferred to tabs and a "tab" is made up of 4 spaces following [[https://www.python.org/dev/peps/pep-0008/][PEP 8 standard]] which is a style guide for Python.
-
-This could be inapplicable if you're worrying about how to create the code that works so be sure to apply it when refactoring.

2020-09-14-05-54-45.org

@@ -1,12 +0,0 @@
-#+title: Linked data
-#+author: "Gabriel Arazas"
-#+email: "foo.dogsquared@gmail.com"
-#+date: "2020-09-14 05:54:45 +08:00"
-#+date_modified: "2020-09-14 05:55:52 +08:00"
-#+language: en
-#+options: toc:t
-#+property: header-args  :exports both
-
-
-- [[http://lab.cccb.org/en/wikidata-the-new-rosetta-stone/][Wikidata is the new Rosetta Stone]]
-- [[https://github.com/Chocobozzz/PeerTube/issues/352][This discussion over at PeerTube]]

2020-10-30-00-49-22.org

@@ -1,12 +0,0 @@
-#+title: Web annotations
-#+author: "Gabriel Arazas"
-#+email: "foo.dogsquared@gmail.com"
-#+date: "2020-10-30 00:49:22 +08:00"
-#+date_modified: "2020-10-30 01:04:35 +08:00"
-#+language: en
-#+options: toc:t
-#+property: header-args  :exports both
-
-
-- https://beepb00p.xyz/annotating.html
-- https://beepb00p.xyz/pkm-setup.html

2020-12-05-19-37-40.org

@@ -1,14 +0,0 @@
-#+title: When beginning with 3D modelling, start with low-poly style
-#+author: "Gabriel Arazas"
-#+email: "foo.dogsquared@gmail.com"
-#+date: "2020-12-05 19:37:40 +08:00"
-#+date_modified: "2020-12-05 21:38:07 +08:00"
-#+language: en
-#+options: toc:t
-#+property: header-args  :exports both
-
-
-When you start with 3D modelling, you can start with low-poly style since it has the least amount of detail required thus get you efficient.
-The skills to create 3D illustrations are mostly the same with drawing: observation, spatial reasoning, compositions, and a sense of detail.
-
-Once you're familiar with the low-poly style, you can then add more details to move into a realistic style or exaggerate them to create a stylized version of the model.

2020-12-13-20-18-44.org

@@ -1,13 +0,0 @@
-#+title: Graphic design
-#+author: "Gabriel Arazas"
-#+email: "foo.dogsquared@gmail.com"
-#+date: "2020-12-13 20:18:44 +08:00"
-#+date_modified: "2020-12-13 20:26:04 +08:00"
-#+language: en
-#+options: toc:t
-#+property: header-args  :exports both
-
-
-You see graphic design being used everywhere including in websites, movie posters, books (covers and everything), chocolate boxes, and glass cases.
-The common ground between the listed items are about presenting an idea or a product.
-Some of the designs revolve around text (e.g., typography), shapely forms (e.g., visual design), and composition (e.g., web design) which then may be used exclusively or any of the combination.