about summary refs log tree commit diff
diff options
context:
space:
mode:
authorNgô Ngọc Đức Huy <huyngo@disroot.org>2021-02-06 16:37:59 +0700
committerNgô Ngọc Đức Huy <huyngo@disroot.org>2021-02-06 16:37:59 +0700
commitf866c9bd9d3fc46d7ea98463b4003dc231fdcccd (patch)
tree21a09498ac15616bf95445997aeffa9d29604ced
parent9885eb6a0347e4db74be8457f7742e5508a53df1 (diff)
downloadblog-f866c9bd9d3fc46d7ea98463b4003dc231fdcccd.tar.gz
Simplify stuffs
-rw-r--r--about.markdown31
-rw-r--r--contact.md50
-rw-r--r--mail-etiquette.md147
3 files changed, 55 insertions, 173 deletions
diff --git a/about.markdown b/about.markdown
index c1a34a3..3ecc7c7 100644
--- a/about.markdown
+++ b/about.markdown
@@ -32,37 +32,21 @@ It's about various things:
 - Digital freedom
 - Books or fiction in general
 
+But it's primarily about technology in general.
+
 # Projects
 
 Some projects I proudly contributed to or authored:
 
 - [~cnx/palace][palace], a 3D audio library in Python
 - [acanban], an in-development academic-oriented project management system
-- [YAltaCV], a Python script that generate AltaCV-theme from YAML
 - [discord-meme-bot], a meme bot for discord
 - [wikt-cli], a CLI tool to search Wiktionary using its API
+- [YAltaCV], a Python script that generate AltaCV-theme from YAML
 
-# Translation
-
-I translate some of my posts to some languages other than English. If you're a native
-speaker or are proficient in the respective languages, feel free to help me improve
-my writing and correct my grammar or vocabulary mistake.
-
-Improvement for my English writing is also appreciated. I usually don't proofread
-my writing, thus it may contain some grammar, spelling error. The writing can also
-be bad due to repetitive vocabulary or lack of logical arrangement between sections.
-
-Please send me correction via email (see the contact below)
-and write in the corresponding language (e.g. write in French if you find a grammar
-mistake in French).
-
-# Contact
-
-Feel free to contact me via:
+# Correct mistakes
 
-- Mastodon: [@huy_ngo@fosstodon][fosstodon]
-- Matrix: [@xarvos:matrix.org][matrix]
-- Email: [Gmail][gmail] or [Disroot mail][disroot] (see [email ettiquette][mail-etiq])
+Any correction is appreciated, whether I state a wrong fact or make a grammar mistake.
 
 # Copying
 
@@ -83,10 +67,6 @@ I receive donate on [liberapay]/huy.ngo and [patreon]/\_\_huy_ngo\_\_.
 The source code for generating this website can be found on [GitHub][gh-blog], [Disroot][disroot-blog], and [source hut][srht-blog].
 
 [cv]: https://raw.githubusercontent.com/Huy-Ngo/my-cv/master/huy-cv.pdf
-[fosstodon]: https://fosstodon.org/@huy_ngo
-[matrix]: https://matrix.to/#/@xarvos:matrix.org
-[gmail]: mailto:duchuy29092000@gmail.com
-[disroot]: mailto:huyngo@disroot.org
 [jekyll]: https://github.com/jekyll/jekyll
 [minima]: https://github.com/jekyll/minima
 [palace]: https://git.sr.ht/~cnx/palace
@@ -100,4 +80,3 @@ The source code for generating this website can be found on [GitHub][gh-blog], [
 [srht-blog]: https://git.sr.ht/~huyngo/blog
 [liberapay]: https://liberapay.com/huy.ngo/
 [patreon]: https://www.patreon.com/__huy_ngo__
-[mail-etiq]: /mail-ettiquette
diff --git a/contact.md b/contact.md
new file mode 100644
index 0000000..d49c18f
--- /dev/null
+++ b/contact.md
@@ -0,0 +1,50 @@
+---
+layout: page
+title: Contact
+language: en
+ref: contact
+---
+
+If you don't know me, it's probably best to contact me via [email][email].
+Please follow this guidelines for any other contact method:
+
+- Mastodon: [@huy_ngo@fosstodon][fosstodon]
+- Matrix: [@xarvos:matrix.org][matrix]
+
+# Language
+
+- I prefer English as my working language, but feel free to use any other if it's relevant.
+- Call me Huy, not Ngo. Vietnamese people don't refer to each other by family name.
+- No need for Mr., just the name is fine.
+
+# Attachment
+
+- [Don't send Word documents][no-word], and don't tell me to use it.
+- Similarly, don't send RAR archive. Maybe avoid sending archive in general.
+- Avoid sending
+
+# Send in plain text
+
+I probably would not read HTML emails, which is problematic.
+Read [this page][useplaintext] to see how to write mail in plain text file.
+
+## What if I want to include an image?
+
+Attach it as a file and refer to that. Maybe avoid images as a whole
+
+## Links are usually long and I'm afraid it can be disruptive
+
+You can use reference, like this:
+
+	Please read the post [1] for more information.
+	...
+
+	[1]: https://example.org/this-link-is-long-and-disruptive
+
+[disroot]: mailto:huyngo@disroot.org
+[email]: mailto:huyngo@disroot.org
+[fosstodon]: https://fosstodon.org/@huy_ngo
+[gmail]: mailto:duchuy29092000@gmail.com
+[matrix]: https://matrix.to/#/@xarvos:matrix.org
+[no-word]: https://www.gnu.org/philosophy/no-word-attachments.html
+[useplaintext]: https://useplaintext.email
diff --git a/mail-etiquette.md b/mail-etiquette.md
deleted file mode 100644
index 5c98fbe..0000000
--- a/mail-etiquette.md
+++ /dev/null
@@ -1,147 +0,0 @@
----
-layout: page
-title: Email
-language: en
-ref: mail-etiquette
----
-I have seen many people having problem with using email, especially from my classmates.
-Writing email is an important skill, and knowing how to write email properly is respecting
-the recipient.
-
-In this article I am writing about how to write a proper mail,
-my email preferences, and some technical issues related to email.
-If you violate too many red flags I stated here I probably won't read your mail.
-
-### Contents
-* Table of contents
-{:toc}
-
-# Email Structure
-
-Here is a generic email structure:
-
-	[Tag] Subject
-
-	Greeting: Hi/Dear [name]/Sir/Madame/To whom it may concern,
-
-	Introduction
-
-	Elaboration
-
-	Regards
-
-	Signature
-
-## Subject
-
-Some people find it hard to come up with a good email subject.
-
-You can (and should) include a short tag to let the recipient know about the topic
-before reading the whole subject line, unless they requested otherwise.
-
-## Greeting
-
-It's not a problem for most people, though I have personally received many emails without greeting.
-An email is not a private message, and even for private message you probably should do a greeting
-before a conversation as well.
-
-Note:
-
-- Hi/Hello is informal, so you probably should avoid it if you don't know the person.
-- You could include the person's title (e.g., Dr.) if you like and the other person is comfortable, but for me personally, don't use Mr.
-- Refer to the person with their preferred name. For me, this means don't use my family name[^1]. Also, don't deadname trans people.
-
-## Introduction
-
-It is necessary to introduce yourself if you and the other person don't know each other. Start with
-
-	My name is... I am ...
-	I am writing this mail to ...
-
-If you know the person, you can just come to the reason you're writing this mail.
-
-## Regards and Signature
-
-To close an email, you should end it with:
-
-- Sincerely,
-- Regards,
-- Yours cordially,
-- Best,
-
-... followed by your name. 
-
-# Language
-
-This should go without saying, but when someone sends you an email in a language,
-don't reply in another, unless you're asked to.
-
-## Pronoun
-
-Pronoun is a sensitive topic, and mispronoun someone can make [zem]
-feel very uncomfortable.
-
-In English, this is not very a common problem, since first and second pronouns
-are neutral. In other languages, such as French or German, it is not. Using "tu"
-or "du/ihr" in a formal email (i.e. not with your friends) will make you look
-very unprofessional. Choosing pronouns is a difficult problem in a deeper level,
-since the pronouns depend on age, gender, social status, job, etc and not
-just the formalness. That's why I don't like writing in Vietnamese.
-
-# Attachment
-
-This is a rather technical topic, but it's simple to follow.
-
-[Don't send Word documents][no-word]. Words are not only bloated and inefficient,
-it also poses malware and virus threats. Of course, you wouldn't attach those, but for
-safety many people including me would not take the risk.
-
-Instead, just include the text inside the email if it is not long, export the document
-as pdf, HTML, or plain text file.
-
-Similarly, don't send RAR archive. RAR is a proprietary archive format, which means
-free software cannot open it. Please use an open format like ZIP instead, or better yet,
-just attach individual files in the email - I can preview without download that way.
-
-# Send in plain text
-
-This is a rather technical topic, but it's simple to follow.
-I'm not dictating which format you should use when emailing someone else, but please do
-this when you send me an email.
-
-HTML text is preferred by marketers, since they can embed bloated images and GIFs in the
-email, which can assist their intended purpose.
-
-However, I recommend writing mails only in plain text for following reason:
-
-- HTML allows phishing
-- HTML makes tracking possible, which doesn't respect recipient's privacy
-- HTML emails are less accessible (I will make a post about accessibility and link here)
-
-In fact, many mail clients only display plain text and not HTML. On the other hand, all
-mail clients can display plain text.
-Many mailing list blocks HTML. HTML is for the web, which email is not[^2].
-
-Read [this page][useplaintext] to see how to write mail in plain text file.
-
-## What if I want to include an image?
-
-Attach it as a file and refer to that.
-
-## Links are usually long and I'm afraid it can be disruptive
-
-You can use reference, like this:
-
-	Please read the post [1] for more information.
-	...
-
-	[1]: https://example.org/this-link-is-long-and-disruptive
-
-[^1]: I would say it's the same for all other Vietnamese people. Vietnamese people currently has quite few family name,
-and most of them are "Nguyễn", therefore we never refer to one another as family name. This could be different for other Asian culture,
-e.g. Chinese or Japanese people may use family name in formal situation.
-[^2]: They work on entirely different protocols, with different formats.
-
-[useplaintext]: https://useplaintext.email
-[zem]: /menglish.html
-[no-word]: https://www.gnu.org/philosophy/no-word-attachments.html