I'm thinking of creating a website for a friend. This includes registering a domain name and setting up a couple email addresses (myfriend@myfriend.com, etc.)
If the friend doesn't maintain the domain registration, and the domain falls into the hands of a nefarious actor, how can I protect my friends email addresses?
If I'm not mistaken, it is a common tactic to register a defunct domain name and impersonate the associated email addresses.
Maintain the domain registration indefinitely on behalf of your friend. You could register it for ten years and renew it yearly so the risk is always ten years out, and hope that by the time they stop using it, whatever systems they authenticated with it are also defunct within ten years. You could also retain a company like MarkMonitor, which does domain management as part of trademark and other IP management.
But there's no way to control it after it lapses. It's an implicit risk for any system that relies on email for authentication.
Hm. This means that any domain name registered for a friend, client, project, etc. must be registered indefinitely IF a domain email address was used (and said email address is deemed to be "important").
- ...a text editor (VS Code)
- ...with Dendron (Outfitted with custom kb schemas and snippets, etc)
- ...a browser (Chrome, Firefox, etc.)
- ...a new diagram (Drawio only)
Example: I want to learn about and become fluent in the topic of X.509 certificates.
1. Open VS Code (Dendron extension starts)
2. CTRL+l and type `crypto.x.509`. This creates a `.md` file in my knowledge base
a. Because I have a "Crypto" schema setup in Dendron, upon creating the new document under `crypto.`, a markdown template is applied with the following headings:
i. ### Acronyms / Definitions
ii. ### Questions
iii.### Resources
iv. ### Footnotes
3. Open Firefox and DuckDuckGo "X.509 standards"
a. Points to the [ITU-T website](https://www.itu.int/t/aap/recdetails/8529)
4. Find the spec website and download the PDF, save to my `dendron\assets\pdf` directory
5. In a new `crypto.x.509.drawio` file, draw box "ITU-T" on the diagram
6. Copy the spec URL to my `crypto.x.509.md` file under the `### Resources` heading (add some alt text)
7. Read the PDF spec VERY CAREFULLY; creating a box on the diagram _for each noun_ I come across.
a. Once boxes appear to either work together in a process or are part of the same concept, I contain them in a larger "parent" box
b. This is good for determining hierarchy and peer relationships
Benefits:
- Its fairly quit to get "a sheet of music" in front of all concerned parties (if you're working on a team)
- I like seeing the diagram and *easily* manipulate thoughts (boxes) and move them into combinations
- Writing everything in Markdown basically creates a website of your notes
