diff --git a/README.md b/README.md
index b66107d..1fe2e82 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,6 @@
 [@matthewzring]: https://github.com/matthewzring
 [101 Guide]: https://gist.github.com/matthewzring/9f7bbfd102003963f9be7dbcf7d40e51
 
-
 # Discord Markdown 201
 
 Wanna inject some flavor into your everyday text chat? You’re in luck!
@@ -18,6 +17,7 @@ Just add a few ornaments around your text to change it!
 > 
 > ![shruggie](images/markdown0.png)
 
+
 ## Sweet Styles
 
 | Style | Markdown |
@@ -45,7 +45,10 @@ You can even mix n’ match formatting options into more powerful ones, such as
 
 Just dropping a web address without the `[]()` markdown also *links* it up,
 which you’ve probably done several times. Note that a “plain” link isn’t based on Markdown, so `\` won’t “unlink” it.
+
 Both “plain” and “masked” links also supports previews if the linked site has them set up.
+To preëmptively squelch the preview, surround the web address with `<…>`, e.g.,
+`[Rick Roll](<https://www.youtube.com/watch?v=dQw4w9WgXcQ>)`
 
 ![Two formats of links and their previews](images/link1.png)
 
@@ -54,7 +57,6 @@ By the way, Discord found a way to stop you from hiding rickrolls or malware beh
 ![Cannot format a link with a link](images/link2.png)
 
 
-
 ## Code Blocks
 
 Markdown also has code formatting. In addition to making your text stubby and nerdy,
@@ -201,21 +203,33 @@ It’s like an anti-heading, just also not **Bold** by default, and also gray.
 
 ## Discord Tags
 
-While not Markdown, Discord also uses some special syntaxes for things like mentions and channel tags:
+While not Markdown, Discord’s things like mentions and channel tags are also text-based structures internally:
 https://discord.com/developers/docs/reference#message-formatting
 
+Timestamp Generator: https://hammertime.cyou
+
 Backslashes can also escape those, but effects are a bit inconsistent. For consistent results:
 * `<\@USER_ID>`, `<\#CHANNEL_ID>`, `<\@&ROLE_ID>`, etc.
 * alternatively: `<@USER_ID\>`, `<#CHANNEL_ID\>`, `<@&ROLE_ID\>`, etc.
 * `:100\:`
 * `\<:NAME:ID>`, `\<a:NAME:ID>`, `\<t:TIMESTAMP>`, etc.
 
+### More Fun Stuff
+
+* On Desktop/Web, you can bring out a flyout to tag non-text channels (Voice, Guide, etc.) with `#!channel`
+  
+  ![non-text channels flyout](images/shebang.png)
+  
+* If you start your message with `@silent` (followed by space or newline), that message won’t push device notifications.
+(Explicit `@`pings are still highlighted and counted). See: https://github.com/discord/discord-api-docs/commit/b7d6467
+  
+  ![This is a @silent message.](images/silent.png)
+  
 
 ---
 
 > And now you’re a **Discord text Markdown super-expert**. Go out there and highlight your accomplishments!
 
-
 [^x]: This does not apply on Desktop/Web if a space follows the first `*` (i.e., `* text*` or `* text *`)
   [tested Web 198920, Desktop PTB 198953]; it also does not apply on Mobile if a space precedes the second `*`
   (i.e., `*text *` or `* text *`) [tested Mobile 178.19].
diff --git a/images/shebang.png b/images/shebang.png
new file mode 100644
index 0000000..8f9acbb
Binary files /dev/null and b/images/shebang.png differ
diff --git a/images/silent.png b/images/silent.png
new file mode 100644
index 0000000..a40c365
Binary files /dev/null and b/images/silent.png differ