Add example posts

.drone.yml

@@ -1,41 +0,0 @@
----
-kind: pipeline
-type: docker
-name: Deploy to bbaovanc.com
-
-trigger:
-    branch:
-        - master
-    event:
-        exclude:
-            - pull_request
-
-steps:
-    - name: submodules
-      image: alpine/git
-      commands:
-          - git submodule update --init --recursive
-
-    - name: build
-      image: bbaovanc/hugo
-      commands:
-          - hugo version
-          - hugo --minify
-
-    - name: list files
-      image: alpine:latest
-      commands:
-          - find public/
-
-    - name: upload
-      image: appleboy/drone-scp
-      settings:
-          host: bbaovanc.com
-          port: 2222
-          username: droneci
-          key:
-              from_secret: SSH_KEY
-          target: /var/www/bbaovanc/blog/
-          rm: true
-          source: public/
-          strip_components: 1

.editorconfig

@@ -1,11 +0,0 @@
-root = true
-
-[*.{md,toml}]
-end_of_line = lf
-insert_final_newline = true
-indent_style = space
-indent_size = 2
-trim_trailing_whitespace = true
-
-[*.md]
-max_line_length = 80

Makefile

@@ -1,12 +0,0 @@
-all: public
-
-public:
-	hugo
-
-clean:
-	rm -rf public
-
-push: clean public
-	rsync -arvz -e 'ssh -p 2222' --progress --delete public/ bbaovanc.com:/var/www/bbaovanc/blog/
-
-.PHONY: all clean push

assets/css/comments.css

@@ -1,22 +0,0 @@
-.commento-root * {
-    color: white;
-}
-
-.commento-root .commento-logged-container .commento-logged-in-as .commento-name,
-.commento-root .commento-anonymous-checkbox-container input[type="checkbox"] + label {
-    color: rgb(134, 142, 150);
-}
-
-.commento-root textarea {
-    border-color: rgba(255, 255, 255, 0.1);
-    background-color: rgba(0, 0, 0, 0);
-    color: white;
-}
-
-.commento-root .commento-card {
-    border-top-color: rgba(255, 255, 255, 0.1);
-}
-
-.commento-root .commento-dark-card {
-    background-color: rgb(64, 64, 64);
-}

config.toml

@@ -2,7 +2,6 @@ baseURL = "https://bbaovanc.com/blog/"
 languageCode = "en-us"
 theme = "terminal"
 paginate = 5
-enableGitInfo = true
 
 # [permalinks]
 #     posts = "/:year/:month/:title/"
@@ -16,7 +15,7 @@ enableGitInfo = true
     themeColor = "blue"
 
     # if you set this to 0, only submenu trigger will be visible
-  showMenuItems = 6
+    showMenuItems = 2
 
     # show selector to switch language
     showLanguageSelector = false
@@ -32,7 +31,7 @@ enableGitInfo = true
 
     # set post to show the last updated
     # If you use git, you can set `enableGitInfo` to `true` and then post will automatically get the last updated
-  showLastUpdated = true
+    showLastUpdated = false
     # Provide a string as a prefix for the last update date. By default, it looks like this: 2020-xx-xx [Updated: 2020-xx-xx] :: Author
     # updatedDatePrefix = "Updated"
 
@@ -69,37 +68,6 @@ enableGitInfo = true
 
         [languages.en.menu]
             [[languages.en.menu.main]]
-        identifier = "tags"
+                identifier = "other-sites"
-        name = "Tags"
+                name = "Other Sites"
-        url = "/tags"
+                url = "/other-sites"
-        weight = 10
-
-      [[languages.en.menu.main]]
-        identifier = "links"
-        name = "Links"
-        url = "/links"
-        weight = 20
-
-      [[languages.en.menu.main]]
-        identifier = "rss"
-        name = "RSS Feed"
-        url = "/posts/index.xml"
-        weight = 30
-
-      [[languages.en.menu.main]]
-        identifier = "email-me"
-        name = "Email Me"
-        url = "mailto:contact@bbaovanc.com"
-        weight = 40
-
-      [[languages.en.menu.main]]
-        identifier = "main-website"
-        name = "Main Website"
-        url = "https://bbaovanc.com/"
-        weight = 50
-
-      [[languages.en.menu.main]]
-        identifier = "source-code"
-        name = "Source Code"
-        url = "https://git.bbaovanc.com/bbaovanc.com/blog"
-        weight = 60

content/links.md

@@ -1,41 +0,0 @@
----
-title: "Links"
-toc: true
----
-
----
-
-## Other
-
-- [GitHub](https://github.com/BBaoVanC/)
-
-## My Website
-
-- [Main Site](https://bbaovanc.com/)
-- [Blog](https://bbaovanc.com/blog/)
-- [Status Page](https://status.bbaovanc.com/)
-- [Searx Instance](https://search.bbaovanc.com/) -
-  [source code](https://github.com/BBaoVanC/searx)
-- [Gitea Instance](https://git.bbaovanc.com/)
-
-## My Software
-
-- [imgupload.py](https://github.com/imgupload-py/imgupload.py)
-- [pynamegen](https://git.bbaovanc.com/bbaovanc/pynamegen)
-  - [libnamegen](https://git.bbaovanc.com/bbaovanc/libnamegen)
-  - [liblistloader](https://git.bbaovanc.com/bbaovanc/liblistloader)
-  - [libprogress](https://git.bbaovanc.com/bbaovanc/libprogress)
-
-## My Configurations
-
-- [dotfiles](https://github.com/BBaoVanC/dotfiles)
-- [dwm](https://github.com/BBaoVanC/.dwm)
-  - [st](https://github.com/BBaoVanC/st)
-  - [dwm-flexipatch](https://github.com/BBaoVanC/dwm-flexipatch)
-  - [dwmblocks](https://github.com/BBaoVanC/dwmblocks)
-  - [dmenu](https://github.com/BBaoVanC/dmenu)
-
-### Old Configurations
-
-- [dwm](https://github.com/BBaoVanC/dwm)
-- [xmonad](https://github.com/BBaoVanC/.xmonad)

content/other-sites.md

@@ -0,0 +1,7 @@
+---
+title: "Other Sites"
+draft: false
+---
+
+- [GitHub](https://github.com/BBaoVanC)
+- [Gitea](https://git.bbaovanc.com)

content/posts/allow-non-root-processes-to-bind-to-privileged-ports.md

@@ -1,68 +0,0 @@
-+++
-title = "Allow Non Root Processes to Bind to Privileged Ports"
-date = "2021-03-28T20:03:16-05:00"
-author = "bbaovanc"
-tags = ["guide", "linux"]
-keywords = ["linux", "privileged", "ports", "tutorial", "guide", "gitea",
-"systemd"]
-
-description = """
-In Linux, processes cannot bind to privileged ports (<=1024) unless they are
-running as root. Here's how to allow any process to bind to privileged ports.
-"""
-
-showFullContent = false
-toc = true
-+++
-
-## Introduction
-
-In Linux, processes cannot bind to privileged ports (<=1024) unless they are
-running as root. I learned about this when I was trying to add SSH cloning to my
-[Gitea](https://gitea.io) instance. This can be bypassed by giving
-`CAP_NET_BIND_SERVICE` capabilities to either the systemd service, or the
-executable itself.
-
-## Giving `CAP_NET_BIND_SERVICE` capabilities
-
-### Using systemd (preferred)
-
-The best way is to tell systemd to give `CAP_NET_BIND_SERVICE`
-capabilities to the service. In fact, the Gitea systemd service has two
-lines[^1] that are commented out:
-
-```systemd
-CapabilityBoundingSet=CAP_NET_BIND_SERVICE
-AmbientCapabilities=CAP_NET_BIND_SERVICE
-```
-
-Uncommenting these two lines was all I had to do for Gitea.
-
-### Using `setcap`
-
-You can add `CAP_NET_BIND_SERVICE` to the executable directly using `setcap`,
-allowing it to bind to any port. Run the following command[^2]:
-
-```bash
-setcap 'cap_net_bind_service=+ep' /path/to/program
-```
-
-Note that this means that anyone with permission to run this program will be
-able to run it and bind to any privileged ports.
-
-Other caveats[^2]:
-
-> 1. You will need at least a 2.6.24 kernel
-> 2. This won't work if your file is a script. (ie, uses a #! line to launch an
->    interpreter). In this case, as far I as understand, you'd have to apply the
->    capability to the interpreter executable itself, which of course is a
->    security nightmare, since any program using that interpreter will have the
->    capability. I wasn't able to find any clean, easy way to work around this
->    problem.
-> 3. Linux will disable LD\_LIBRARY\_PATH on any program that has elevated
->    privileges like setcap or suid. So if your program uses its own .../lib/,
->    you might have to look into another option like port forwarding.
-
-[^1]: https://github.com/go-gitea/gitea/blob/3416e2a82586fca4cd452b93237b979300f55d62/contrib/systemd/gitea.service#L69
-      and https://stackoverflow.com/a/47065825
-[^2]: https://stackoverflow.com/a/414258

content/posts/checkra1n-gui-on-other-distros.md

@@ -1,49 +0,0 @@
-+++
-title = "Checkra1n GUI on Other Distros"
-date = "2021-03-25T21:19:51-05:00"
-author = "bbaovanc"
-cover = "media/checkra1n-gui-on-arch-linux.webp"
-tags = ["guide", "linux", "archlinux", "jailbreak", "checkra1n"]
-keywords = ["checkra1n", "gui", "linux", "arch linux"]
-
-description = """
-You can run the GUI version of checkra1n on non Debian-based distributions.
-"""
-
-showFullContent = false
-toc = true
-+++
-
-## Introduction
-
-The official cross-distribution build of checkra1n only contains a CLI and TUI.
-However, the version available in the
-[checkra1n APT repository](https://checkra.in/linux) also contains a GTK-based
-GUI which can be accessed using the `--gui` flag, or the included
-`checkra1n.desktop` file.
-
-## Other Distributions
-
-First, download the Debian package available at
-`https://assets.checkra.in/debian/checkra1n_VERSION_amd64.deb` (as of writing,
-`VERSION` is currently `0.12.2`). Then, extract the `checkra1n` executable from
-the package, and install the correct shared libraries. Here are the most
-important ones, and their corresponding package names on Arch Linux:
-
-- libimobiledevice-1.0.so.6 (`libimobiledevice`)
-- libirecovery-1.0.so.3 (`libirecovery`)
-- libtvcontrol.so (`libtvcontrol`)
-- libplist-2.0.so.3 (`libplist`)
-- libncurses.so.5 (`ncurses5-compat-libs`)
-
-I found these by running the binary and then finding and installing the package
-that contained the shared object I was missing.
-
-I also made an AUR package named
-[`checkra1n-gui`](https://aur.archlinux.org/packages/checkra1n-gui),
-which does all this automatically.
-
-## Conclusion
-
-As I expected, there is nothing preventing the checkra1n GUI from working on non
-Debian-based distributions (as far as I can tell).

content/posts/edited-in-middle-of-message-discord.md

@@ -1,29 +0,0 @@
-+++
-title = "Put (edited) in the middle of a message in Discord"
-date = "2021-03-25T18:48:34-05:00"
-author = "bbaovanc"
-cover = "media/discord-tricks/edited-in-middle-of-message.webp"
-tags = ["tutorial", "discord", "discord-tricks"]
-keywords = ["discord", "edited"]
-
-description = """
-With a bit of trickery using the RLE character (U+202B), you can get the
-(edited) text on a message to be somewhere other than at the end of the message.
-"""
-
-showFullContent = false
-+++
-
-## Tutorial
-
-1. Copy the "right-to-left embedding" character (U+202A) to your clipboard.
-2. Open editing box of a message
-3. Delete all text inside
-4. Paste the character
-5. Type the text you want on the right of `(edited)`
-6. Press space and paste the character
-7. Type the text you want on the left of `(edited)`
-
-*This post was adapted from [gitea:bbaovanc/discord-tricks][1]*
-
-[1]: https://git.bbaovanc.com/bbaovanc/discord-tricks

content/posts/first.md

@@ -0,0 +1,19 @@
++++
+title = "First Post"
+date = "2021-03-25T18:00:53-05:00"
+author = "bbaovanc"
+authorTwitter = "" #do not include @
+cover = ""
+tags = ["example"]
+keywords = ["first"]
+description = "First article"
+showFullContent = false
++++
+
+Hello, world!
+
+This is another paragraph!
+
+<!--more-->
+
+This is some more!

content/posts/lorem-ipsum.md

@@ -0,0 +1,25 @@
++++
+title = "Lorem Ipsum"
+date = "2021-03-25T18:00:55-05:00"
+author = "Lorem"
+authorTwitter = "" #do not include @
+cover = ""
+tags = ["example", "lorem"]
+showFullContent = false
++++
+
+## Lorem
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Aliquam malesuada bibendum arcu vitae. Suspendisse ultrices gravida dictum fusce ut placerat. Volutpat est velit egestas dui id ornare arcu. Quisque egestas diam in arcu. Augue lacus viverra vitae congue eu consequat ac. Tortor at auctor urna nunc id. Eu consequat ac felis donec. Nulla aliquet porttitor lacus luctus accumsan tortor. Justo nec ultrices dui sapien. Nec ullamcorper sit amet risus. Eleifend quam adipiscing vitae proin sagittis nisl rhoncus mattis rhoncus. Risus nullam eget felis eget nunc. Ut placerat orci nulla pellentesque dignissim enim sit amet.
+
+<!--more-->
+
+## Ipsum
+
+At varius vel pharetra vel turpis nunc eget. Dolor morbi non arcu risus quis varius. Suspendisse potenti nullam ac tortor vitae purus faucibus ornare suspendisse. Sit amet facilisis magna etiam tempor orci eu. Nulla porttitor massa id neque. Volutpat consequat mauris nunc congue nisi vitae suscipit. Aliquet risus feugiat in ante. Lacus laoreet non curabitur gravida. Diam donec adipiscing tristique risus nec feugiat. Pharetra magna ac placerat vestibulum lectus mauris ultrices eros. Sed arcu non odio euismod lacinia at quis. Aliquam ultrices sagittis orci a. Libero nunc consequat interdum varius sit amet. Donec ultrices tincidunt arcu non sodales neque. Metus dictum at tempor commodo ullamcorper a lacus vestibulum.
+
+Amet consectetur adipiscing elit pellentesque habitant. Dignissim convallis aenean et tortor at risus viverra adipiscing. Odio aenean sed adipiscing diam. Sociis natoque penatibus et magnis dis parturient montes nascetur. Eget mauris pharetra et ultrices. Neque sodales ut etiam sit amet nisl. Consequat ac felis donec et odio pellentesque. Morbi non arcu risus quis varius quam quisque. Sit amet facilisis magna etiam tempor orci. Augue mauris augue neque gravida in fermentum et sollicitudin. Eget nullam non nisi est sit. Nunc eget lorem dolor sed viverra ipsum nunc. Vulputate sapien nec sagittis aliquam malesuada bibendum arcu vitae. Sed vulputate odio ut enim blandit volutpat. Turpis nunc eget lorem dolor sed viverra ipsum nunc. Fermentum posuere urna nec tincidunt. Malesuada pellentesque elit eget gravida cum sociis. Interdum velit euismod in pellentesque massa placerat duis ultricies lacus.
+
+Tempor id eu nisl nunc. Et egestas quis ipsum suspendisse. Consectetur adipiscing elit ut aliquam purus sit amet luctus. Adipiscing tristique risus nec feugiat in. Nibh tellus molestie nunc non blandit massa enim. Cras fermentum odio eu feugiat. Urna id volutpat lacus laoreet non curabitur gravida arcu ac. Quis commodo odio aenean sed adipiscing diam. Vel fringilla est ullamcorper eget nulla facilisi etiam dignissim diam. Netus et malesuada fames ac turpis. Nunc scelerisque viverra mauris in aliquam. Ut porttitor leo a diam sollicitudin tempor id eu nisl. Facilisis magna etiam tempor orci eu lobortis elementum. Vitae semper quis lectus nulla at volutpat diam ut. Pellentesque adipiscing commodo elit at imperdiet dui accumsan. Risus nullam eget felis eget. Neque volutpat ac tincidunt vitae semper quis lectus. Neque egestas congue quisque egestas diam in. Egestas quis ipsum suspendisse ultrices gravida dictum fusce. A iaculis at erat pellentesque adipiscing commodo elit at imperdiet.
+
+Amet aliquam id diam maecenas ultricies mi eget mauris. Est placerat in egestas erat imperdiet sed euismod. Vel quam elementum pulvinar etiam non. Eros donec ac odio tempor orci dapibus ultrices in. Sagittis nisl rhoncus mattis rhoncus urna neque. Quam viverra orci sagittis eu volutpat odio facilisis. Maecenas pharetra convallis posuere morbi leo urna molestie. Mauris pellentesque pulvinar pellentesque habitant. Cursus in hac habitasse platea dictumst quisque. Nibh venenatis cras sed felis eget velit aliquet sagittis id.

content/posts/new-comment-system-again.md

@@ -1,36 +0,0 @@
-+++
-title = "New Comment System (again)"
-date = "2021-04-17T00:08:30-05:00"
-author = "bbaovanc"
-tags = ["announcement", "hugo", "blog"]
-keywords = ["hugo", "comment system", "blog", "commento"]
-
-description = """
-I decided to switch my comment system from Isso to
-[Commento](https://www.commento.io/)
-"""
-
-showFullContent = false
-+++
-
-## Isso vs Commento
-
-I know it's only been six days since I added Isso, but I decided to switch to a
-better comment system. Isso is meant to be simple, which means that it's missing
-a lot of features. Commento has a lot of features such as sticky (pinned)
-comments, spam detection, thread locking, email notifications (I couldn't get
-this working on Isso), and a nicer design. I also was able to write some
-[custom CSS rules][1] which make it look alright on my blog's theme. It also
-supports SSO, so I might add support for signing up with GitHub, and possibly
-GitLab.
-
-## Summary of the [first post]({{< ref "/posts/new-comment-system" >}})
-
-If you haven't read the
-[New Comment System]({{< ref "/posts/new-comment-system" >}}) post, here's the
-most important information. There's a comment section at the bottom of each post
-where you can view and post comments. You can post anonymously, or create an
-account so you can show your username and get email notifications. You can also
-upvote, downvote, and reply to other comments.
-
-[1]: https://git.bbaovanc.com/bbaovanc.com/blog/src/commit/478e15218313a33216d361de387b3bd878cd0ba6/assets/css/comments.css

content/posts/new-comment-system.md

@@ -1,39 +0,0 @@
-+++
-title = "New Comment System"
-date = "2021-04-11T00:17:13-05:00"
-author = "bbaovanc"
-tags = ["announcement", "hugo", "blog"]
-keywords = ["hugo", "comment system", "blog", "isso"]
-
-description = """
-I added a comment system to my blog, using [Isso](https://posativ.org/isso/).
-"""
-
-showFullContent = false
-toc = true
-+++
-
-## About
-
-I set up a comment system named [Isso](https://posativ.org/isso/) on my blog
-today. At the bottom of each blog post, there's a comment section. You don't
-need to sign up with an account or sign in with Google, Facebook, none of that
-junk. You can comment anonymously, or provide any of the following three fields:
-name, email address, and website, which will be shown to other people viewing
-your comment. I'm going off of the assumption that no one cares/is malicious
-enough to spam my comment sections.
-
-## Known Issues
-
-### Editing and deleting not working
-
-You're supposed to be able to edit and delete comments up to 15 minutes after
-posting them. As of now, that doesn't seem to be working; the request just
-returns 403 (forbidden).
-
-### White text on white background when previewing comment
-
-This is a CSS related issue. This was also happening when editing/writing a
-comment, but I edited it so the edit box has black text. I think a better fix is
-to make the new comment form have a dark background, but I'll deal with that
-later.

content/posts/sed-text-substitution-in-discord.md

@@ -1,29 +0,0 @@
-+++
-title = "Text Substitution in Discord using `sed`"
-date = "2021-03-25T18:48:15-05:00"
-author = "bbaovanc"
-tags = ["tutorial", "discord", "discord-tricks"]
-keywords = ["discord", "sed", "text", "replacement"]
-
-description = """
-Discord has (very primitive) support for text replacement using `sed` syntax.
-"""
-
-showFullContent = false
-+++
-
-## Tutorial
-
-[Example Video](/blog/media/discord-tricks/sed-text-replacement.mov)
-
-If you send a message using `sed` substitution format (`s/old text/new text`),
-Discord will execute it on the message you've last sent.
-
-## Caveats
-
-- Regex is not supported
-- Global substitution is not supported
-
-*This post was adapted from [gitea:bbaovanc/discord-tricks][1]*
-
-[1]: https://git.bbaovanc.com/bbaovanc/discord-tricks

layouts/partials/comments.html

@@ -1,15 +0,0 @@
-{{ $css := resources.Get "css/comments.css" }}
-{{ $style := $css | resources.Minify }}
-
-<script defer
-    src="https://commento.bbaovanc.com/js/commento.js"
-    data-page-id="{{ .RelPermalink }}"
-    data-no-fonts="true"
-    data-css-override="{{ $style.Permalink }}">
-</script>
-<div id="commento"></div>
-
-<noscript>
-    <br />
-    <b>Comments are not available when JavaScript is disabled.</b>
-</noscript>