Compare commits
250 Commits
es/new-com
...
5b067faf53
Author | SHA1 | Date | |
---|---|---|---|
5b067faf53
|
|||
3776ece6c7
|
|||
7f6ef16d4a
|
|||
bad8875a9e
|
|||
3aacbe59b0
|
|||
e7351e8aa8
|
|||
2ec910bdde
|
|||
e077f1348e
|
|||
b4c695aeb4
|
|||
cdfcf3c372
|
|||
6d7dfa6c5d
|
|||
ef8dda9657
|
|||
f6b27235f3
|
|||
1ce61b8260
|
|||
f719cadd1e
|
|||
43d4f47e29
|
|||
510e3e9bf9
|
|||
685a9ed8f4
|
|||
66fac8058f
|
|||
e93871c923
|
|||
07f586e5b0
|
|||
d21feef5b9
|
|||
e49b0aa583
|
|||
91bc38bdd4
|
|||
b80bd5732d
|
|||
b863f577ae
|
|||
c1806338e5
|
|||
f9c4fd8a9a
|
|||
fb0e45d7cd
|
|||
a0165e8569
|
|||
100a86b85f
|
|||
8321945015
|
|||
48ed6eae21
|
|||
795be223eb
|
|||
0e2a26fe56
|
|||
c228d5c903
|
|||
f2494e515f
|
|||
4cd6632799
|
|||
bde9df2aa6
|
|||
87c5d4f1b3
|
|||
31a72c92fa
|
|||
bc76fb5458
|
|||
ddb0045088
|
|||
2fb0d17df1
|
|||
060d3ecd84
|
|||
fd6eb50399
|
|||
87688ef6b3
|
|||
01c2b34920
|
|||
c014da3fe3
|
|||
7d5309862e
|
|||
cef5fe28dc
|
|||
7a529fb1ac
|
|||
852aafb2e7
|
|||
c50d3fda88
|
|||
6f1c5a883f
|
|||
6a941cef7c
|
|||
44c1291fa4
|
|||
dba36c5105
|
|||
6145d4e8d7
|
|||
c5a2e84050
|
|||
94a2404a83
|
|||
fec8bd1933
|
|||
27bc4e28a8
|
|||
e9ad2abd55
|
|||
f0036f20b9
|
|||
2fc8e4646e
|
|||
da8dc12957
|
|||
86f4b102d7
|
|||
d7e219d331 | |||
5b0c092bc0
|
|||
2ce66a14d4 | |||
8a330b59b0
|
|||
de888c1adc
|
|||
927e775439
|
|||
9c572a706b
|
|||
05c8e0da9d
|
|||
191c9a5185
|
|||
c11c9178e0
|
|||
5719a11e8b
|
|||
bacddbfe42
|
|||
4e6f0c7614
|
|||
20abaffc3a
|
|||
3668b6cfb1
|
|||
f3cf22ae33
|
|||
dde5162907
|
|||
90d640bd12
|
|||
904d8928b7
|
|||
827a049946
|
|||
db65e9fc23
|
|||
bd9d294fc1
|
|||
9de4d26b6a
|
|||
f14c1568f7 | |||
1e650ed79b
|
|||
ba9c62ed4f
|
|||
c3632c40ce | |||
02201e806f
|
|||
d27f095c1a
|
|||
2b38b143b1
|
|||
26ccc90cff
|
|||
d5ef788e78
|
|||
8e2673b4ff
|
|||
c58164f1f2
|
|||
4fb9dbaa30
|
|||
359bfbf1b6
|
|||
d011efd2a1
|
|||
98ef3386f5
|
|||
a170885ff8
|
|||
17af722f4d
|
|||
62c62b344c
|
|||
f50665786b
|
|||
57fac4d945
|
|||
f6602dfff0
|
|||
db6fc9e977
|
|||
86a90f907a
|
|||
3838d2d44a
|
|||
ac05117647
|
|||
355d180f6c
|
|||
0bc3f3145e
|
|||
cbe6a1e12a
|
|||
e1dd193bf1
|
|||
0bb3dce6e9
|
|||
6ad002b319
|
|||
1e20d0e943
|
|||
375b90fb07
|
|||
81fa2f6b41
|
|||
fb7b5913c0
|
|||
d8134587e9
|
|||
4db3d24349
|
|||
4017855c29
|
|||
859537be01
|
|||
164565cecb
|
|||
5d08b75f71
|
|||
5782a6a002
|
|||
e21a4b948e
|
|||
9de124a586
|
|||
4a4361dcb5
|
|||
a449933ffe
|
|||
a57715c4fa
|
|||
3ec98f019c
|
|||
fd4a7a7bc2
|
|||
1f263b3a3a
|
|||
c24cdee46c
|
|||
2a79a86fd6
|
|||
97bc1980eb
|
|||
cef1103070
|
|||
1332c16841
|
|||
b124d89391
|
|||
0d432e200c
|
|||
5286bb029f | |||
31e25c2578
|
|||
1033b84687
|
|||
b9a95983b9
|
|||
b14a46d48b
|
|||
99b03ea7ba
|
|||
9c6a2a059d | |||
e10c3a1150
|
|||
9e0d2a9d8f
|
|||
576124d42d
|
|||
7b8f47b56b
|
|||
cab56bd859
|
|||
672bfae812
|
|||
ca40973701 | |||
b2d3bd99f3
|
|||
beb1faf3a8
|
|||
088a52aa96
|
|||
941bb5ce9e
|
|||
a628829bec
|
|||
83cd00078f
|
|||
8207535dca
|
|||
2aec5d33b3
|
|||
11f8115735
|
|||
46af6d4de2
|
|||
efdc6364de
|
|||
5260ca987c
|
|||
8f0b1d4952
|
|||
75f0038a37
|
|||
4d64d0ab0b
|
|||
45d26b2f9f
|
|||
cb02d6f586
|
|||
00a84889b0
|
|||
a4e5997b47
|
|||
1b09947ee6
|
|||
282a5319cc
|
|||
5cc3102deb
|
|||
8c1ee6efe9
|
|||
8a96465a20
|
|||
e3d77d6f60
|
|||
49b7a3a8a1
|
|||
c08d6a927f
|
|||
b23760585d
|
|||
95695e1187
|
|||
4a1d52e11b
|
|||
77731aacb8
|
|||
2dd9928654
|
|||
83f0c77d8d
|
|||
6a1760e3a0
|
|||
2a9af4d89e
|
|||
5250eb5b1d
|
|||
c12fe39134
|
|||
78b7b78e0a
|
|||
37e3442b39
|
|||
f7e2098020
|
|||
54d2599ad3
|
|||
ec7575d7f1
|
|||
bdf9f7737a
|
|||
7f584afa21
|
|||
ad3a77fd7a
|
|||
835068bcbe
|
|||
c92d12cdcd
|
|||
b9b1de8722
|
|||
16b0afafd3
|
|||
0824589054
|
|||
68db383c73
|
|||
b10919bfb0
|
|||
3035740ad1
|
|||
e806ff1b35
|
|||
83bef16379
|
|||
a490baacad
|
|||
cbae5a2fee
|
|||
b76454649b
|
|||
fc67f210d9
|
|||
954bcc19b7
|
|||
a6d6b3ba3c
|
|||
157eb700dd
|
|||
8082b78d02
|
|||
740b849f08
|
|||
04dd824362
|
|||
6a28ab60d4
|
|||
538132bee3
|
|||
fd4022d32d
|
|||
295c4c8095
|
|||
f93f8a643e
|
|||
e4fecdc4c8
|
|||
31053a0a29
|
|||
99bedbaffa
|
|||
b942f7a6a9
|
|||
fc730ad0de
|
|||
da12ee2101
|
|||
ef7eac1bb4
|
|||
9690d77b36
|
|||
463c26a0e0
|
|||
054547afd0
|
|||
dd6d1ac0de
|
|||
c96b2fb91c
|
|||
32933f9001
|
|||
70b2233113
|
|||
b45c051914
|
|||
a887380e66
|
|||
3dd852d3b9
|
|||
a6076f691a
|
150
.github/workflows/audit.yml
vendored
Normal file
@ -0,0 +1,150 @@
|
||||
name: Audit
|
||||
|
||||
on:
|
||||
push:
|
||||
pull_request:
|
||||
|
||||
jobs:
|
||||
lighthouse:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Setup Hugo
|
||||
uses: peaceiris/actions-hugo@v2
|
||||
with:
|
||||
hugo-version: latest
|
||||
extended: true
|
||||
|
||||
- name: Checkout (pull_request)
|
||||
if: github.event.pull_request
|
||||
uses: actions/checkout@v3
|
||||
with:
|
||||
submodules: recursive
|
||||
fetch-depth: 0
|
||||
ref: ${{ github.event.pull_request.base.ref }}
|
||||
|
||||
- name: Checkout (push)
|
||||
if: github.event_name == 'push'
|
||||
uses: actions/checkout@v3
|
||||
with:
|
||||
submodules: recursive
|
||||
fetch-depth: 0
|
||||
ref: ${{ github.event.before }}
|
||||
|
||||
- name: Build previous commit
|
||||
run: |
|
||||
hugo --buildDrafts --printI18nWarnings --printPathWarnings --baseURL https://localhost -d old/
|
||||
|
||||
- name: Checkout current commit
|
||||
uses: actions/checkout@v3
|
||||
with:
|
||||
submodules: recursive
|
||||
fetch-depth: 0
|
||||
clean: false
|
||||
|
||||
- name: Build current commit
|
||||
run: |
|
||||
hugo --buildDrafts --printI18nWarnings --printPathWarnings --baseURL https://localhost
|
||||
cp -r public/ new/
|
||||
# copy, so that public/ stays, it will be needed for Caddy to serve
|
||||
|
||||
- name: Save full diff
|
||||
run: diff -r old/ new/ | tee changes.diff || true
|
||||
|
||||
- name: Upload full diff
|
||||
uses: actions/upload-artifact@v3
|
||||
with:
|
||||
name: diff
|
||||
path: changes.diff
|
||||
|
||||
- name: Find changed URLs
|
||||
id: changed_urls
|
||||
env:
|
||||
SCHEME: https
|
||||
DOMAIN: localhost
|
||||
run: |
|
||||
urls="$(./changed-urls.sh)"
|
||||
echo "urls<<EOM" >> $GITHUB_OUTPUT
|
||||
echo "$urls" >> $GITHUB_OUTPUT
|
||||
echo "EOM" >> $GITHUB_OUTPUT
|
||||
echo -e "CHANGED:\n$urls"
|
||||
|
||||
- name: Install Caddy
|
||||
if: "${{ steps.changed_urls.outputs.urls != '' }}"
|
||||
run: |
|
||||
sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https
|
||||
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
|
||||
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
|
||||
sudo apt update
|
||||
sudo apt install caddy
|
||||
sudo systemctl disable --now caddy
|
||||
|
||||
- name: Compress
|
||||
if: "${{ steps.changed_urls.outputs.urls != '' }}"
|
||||
run: time ./compress.sh
|
||||
|
||||
- name: Audit using Lighthouse
|
||||
if: "${{ steps.changed_urls.outputs.urls != '' }}"
|
||||
uses: treosh/lighthouse-ci-action@v9
|
||||
with:
|
||||
uploadArtifacts: true
|
||||
configPath: ./lighthouserc.yaml
|
||||
runs: 3
|
||||
serverBaseUrl: https://lhci.bbaovanc.com/
|
||||
# this should be safe since it only allows adding (not deleting) data
|
||||
serverToken: 2fca0410-95ae-4ea9-8dc6-687ed7843a3a
|
||||
urls: ${{ steps.changed_urls.outputs.urls }}
|
||||
|
||||
|
||||
audit:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v3
|
||||
with:
|
||||
submodules: recursive
|
||||
fetch-depth: 0
|
||||
ref: ${{github.event.pull_request.head.ref}}
|
||||
repository: ${{github.event.pull_request.head.repo.full_name}}
|
||||
|
||||
- name: Setup Hugo
|
||||
uses: peaceiris/actions-hugo@v2
|
||||
with:
|
||||
hugo-version: latest
|
||||
extended: true
|
||||
|
||||
- name: Build
|
||||
run: |
|
||||
HUGO_MINIFY_TDEWOLFF_HTML_KEEPCOMMENTS=true HUGO_ENABLEMISSINGTRANSLATIONPLACEHOLDERS=true hugo --buildDrafts --printI18nWarnings --printPathWarnings
|
||||
|
||||
# For the following steps, see
|
||||
# https://discourse.gohugo.io/t/audit-your-published-site-for-problems/35184
|
||||
|
||||
- name: Audit - raw HTML
|
||||
if: always()
|
||||
run: |
|
||||
! grep -inorE "<\!-- raw HTML omitted -->" public/
|
||||
|
||||
- name: Audit - ZgotmplZ (unsafe URL content)
|
||||
if: always()
|
||||
run: |
|
||||
! grep -inorE "ZgotmplZ" public/
|
||||
|
||||
#- name: Audit - missing translations
|
||||
# if: always()
|
||||
# run: |
|
||||
# ! grep -inorE "\[i18n\]" public/
|
||||
|
||||
- name: Audit - nil values in printf
|
||||
if: always()
|
||||
run: |
|
||||
! grep -inorE "\(<nil>\)" public/
|
||||
|
||||
- name: Audit - nil values in printf without safeHTML
|
||||
if: always()
|
||||
run: |
|
||||
! grep -inorE "(<nil>)" public/
|
||||
|
||||
- name: Audit - HAHAHUGO
|
||||
if: always()
|
||||
run: |
|
||||
! grep -inorE "hahahugo" public/
|
17
.github/workflows/deploy.yml
vendored
@ -1,6 +1,7 @@
|
||||
name: Deploy
|
||||
|
||||
on:
|
||||
workflow_dispatch:
|
||||
push:
|
||||
branches:
|
||||
- master
|
||||
@ -13,7 +14,7 @@ jobs:
|
||||
url: https://bbaovanc.com
|
||||
steps:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v2
|
||||
uses: actions/checkout@v3
|
||||
with:
|
||||
submodules: recursive
|
||||
fetch-depth: 0
|
||||
@ -25,20 +26,28 @@ jobs:
|
||||
extended: true
|
||||
|
||||
- name: Build
|
||||
run: hugo --i18n-warnings --path-warnings
|
||||
run: hugo --printI18nWarnings --printPathWarnings
|
||||
|
||||
- name: Compress
|
||||
run: |
|
||||
time sudo ./compress.sh
|
||||
|
||||
- name: Setup SSH
|
||||
uses: kielabokkie/ssh-key-and-known-hosts-action@v1
|
||||
with:
|
||||
ssh-private-key: ${{ secrets.DEPLOY_SSH_KEY }}
|
||||
ssh-host: srv.bbaovanc.com
|
||||
ssh-port: 2222
|
||||
|
||||
- name: Upload
|
||||
uses: up9cloud/action-rsync@v1
|
||||
env:
|
||||
HOST: bbaovanc.com
|
||||
HOST: srv.bbaovanc.com
|
||||
USER: droneci
|
||||
PORT: 2222
|
||||
SOURCE: public/
|
||||
MODE: push
|
||||
VERBOSE: true
|
||||
KEY: ${{secrets.DEPLOY_SSH_KEY}}
|
||||
TARGET: /var/www/bbaovanc/public/
|
||||
TARGET: /var/www/bbaovanc.com/public/
|
||||
ARGS: -avPzc --delete-delay --exclude=/.git/ --exclude=/.github/
|
||||
|
17
.github/workflows/pull_request.yml
vendored
@ -12,7 +12,7 @@ jobs:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Checkout
|
||||
uses: actions/checkout@v2
|
||||
uses: actions/checkout@v3
|
||||
with:
|
||||
submodules: recursive
|
||||
fetch-depth: 0
|
||||
@ -27,6 +27,7 @@ jobs:
|
||||
token: ${{ github.token }}
|
||||
env: pr-${{ github.event.number }}
|
||||
ref: ${{ github.head_ref }}
|
||||
no_override: false
|
||||
|
||||
- name: Setup Hugo
|
||||
uses: peaceiris/actions-hugo@v2
|
||||
@ -35,23 +36,31 @@ jobs:
|
||||
extended: true
|
||||
|
||||
- name: Build
|
||||
run: hugo --i18n-warnings --path-warnings --baseURL "https://demo.bbaovanc.com/pull_request/${{ github.event.number }}"
|
||||
run: hugo --printI18nWarnings --printPathWarnings --baseURL "https://demo.bbaovanc.com/pull_request/${{ github.event.number }}" --buildDrafts
|
||||
|
||||
- name: Compress
|
||||
run: |
|
||||
time sudo ./compress.sh
|
||||
|
||||
- name: Setup SSH
|
||||
uses: kielabokkie/ssh-key-and-known-hosts-action@v1
|
||||
with:
|
||||
ssh-private-key: ${{ secrets.DEPLOY_SSH_KEY }}
|
||||
ssh-host: srv.bbaovanc.com
|
||||
ssh-port: 2222
|
||||
|
||||
- name: Upload
|
||||
uses: up9cloud/action-rsync@v1
|
||||
env:
|
||||
HOST: bbaovanc.com
|
||||
HOST: srv.bbaovanc.com
|
||||
USER: droneci
|
||||
PORT: 2222
|
||||
SOURCE: public/
|
||||
MODE: push
|
||||
VERBOSE: true
|
||||
KEY: ${{secrets.DEPLOY_SSH_KEY}}
|
||||
TARGET: /var/www/demo/pull_request/${{ github.event.number }}/
|
||||
TARGET: /var/www/demo.bbaovanc.com/pull_request/${{ github.event.number }}/
|
||||
ARGS: -avPzc --delete-delay --exclude=/.git/ --exclude=/.github/
|
||||
|
||||
- name: Finish deployment
|
||||
uses: bobheadxi/deployments@v0.6.0
|
||||
|
14
.github/workflows/pull_request_cleanup.yml
vendored
@ -1,7 +1,7 @@
|
||||
name: Pull Request Cleanup
|
||||
|
||||
on:
|
||||
pull_request:
|
||||
pull_request_target:
|
||||
types:
|
||||
- closed
|
||||
|
||||
@ -13,15 +13,17 @@ jobs:
|
||||
uses: kielabokkie/ssh-key-and-known-hosts-action@v1
|
||||
with:
|
||||
ssh-private-key: ${{ secrets.DEPLOY_SSH_KEY }}
|
||||
ssh-host: bbaovanc.com
|
||||
ssh-host: srv.bbaovanc.com
|
||||
ssh-port: 2222
|
||||
|
||||
- name: Delete pull request on server
|
||||
run:
|
||||
ssh -p 2222 droneci@bbaovanc.com rm -r /var/www/demo/pull_request/${{ github.event.number }}/
|
||||
ssh -p 2222 droneci@srv.bbaovanc.com rm -r /var/www/demo.bbaovanc.com/pull_request/${{ github.event.number }}/
|
||||
|
||||
- name: Delete deployment
|
||||
uses: strumwolf/delete-deployment-environment@v2
|
||||
- name: Deactivate deployment
|
||||
uses: bobheadxi/deployments@v0.6.0
|
||||
with:
|
||||
step: deactivate-env
|
||||
token: ${{ github.token }}
|
||||
environment: pr-${{ github.event.number }}
|
||||
env: pr-${{ github.event.number }}
|
||||
desc: Deployment was pruned
|
||||
|
5
.gitignore
vendored
@ -14,3 +14,8 @@ hugo.darwin
|
||||
hugo.linux
|
||||
|
||||
# End of https://www.toptal.com/developers/gitignore/api/hugo
|
||||
|
||||
/.hugo_build.lock
|
||||
|
||||
# My private drafts
|
||||
/content/blog/drafts/
|
||||
|
@ -1,69 +1,29 @@
|
||||
# Contributing to bobatheme
|
||||
|
||||
## Where to put stuff
|
||||
## Where to put questions/issues/etc
|
||||
|
||||
### Discussions
|
||||
Use the [GitHub Discussions forum][github-discussions-url] for any questions,
|
||||
or ideas. Use the "Q&A" section for both questions and issues as well.
|
||||
|
||||
The best place to ask questions or have discussions is the (relatively new)
|
||||
discussions feature on GitHub, available
|
||||
[here](https://github.com/BBaoVanC/bbaovanc.com/discussions). It's not too big
|
||||
of an issue though because discussions and issues can easily be converted
|
||||
between eachother.
|
||||
|
||||
### Issues
|
||||
|
||||
Issues should be used only for, well, issues. Ignore all the placeholder ones
|
||||
prefixed with "Translate:" and tagged with the "translation" tag as they are
|
||||
placeholders used in the projects tab. I might mark them as closed in the future
|
||||
to clean it up but I'll worry about that later.
|
||||
|
||||
### Translations
|
||||
|
||||
Discussion relating to translations should either go as comments or reviews on
|
||||
the pull request adding the translation, or as a discussion under the
|
||||
[Translations category](https://github.com/BBaoVanC/bbaovanc.com/discussions/categories/translations).
|
||||
|
||||
## Writing translations
|
||||
|
||||
Translations should aim to get the meaning as close as possible to original
|
||||
document. The changes in a translation pull request *should*:
|
||||
|
||||
- only update one page (multiple pages should be split into separate pull
|
||||
requests)
|
||||
- only contain changes for a single new file (no changes unrelated to
|
||||
translation)
|
||||
- thoroughly compared to the original text in order to get the same meaning
|
||||
across
|
||||
|
||||
## Pull requests
|
||||
|
||||
### Commit messages
|
||||
|
||||
It's not too big of a deal what you put in your commit messages, but try to give
|
||||
each commit a rough description of what it changes. I'll use squash merges most
|
||||
of the time anyways.
|
||||
|
||||
### Description
|
||||
|
||||
If the pull request doesn't require any extra information in addition to the
|
||||
title, you can probably leave the description blank. Otherwise you can put some
|
||||
information, just try to keep it concise; it's better to read a couple sentences
|
||||
than an entire essay with the same amount of information.
|
||||
[github-discussions-url]: https://github.com/BBaoVanC/bbaovanc.com/discussions
|
||||
|
||||
## Building
|
||||
|
||||
## Automatic deploy previews with Netlify
|
||||
Just in case you need it.
|
||||
|
||||
Netlify will automatically build each pull request into a public deploy preview,
|
||||
and will link it in a comment.
|
||||
## Automatic deploy previews with GitHub Actions
|
||||
|
||||
My GitHub Actions workflows will automatically build each pull request into a
|
||||
public deploy preview on demo.bbaovanc.com, and will link it in a comment.
|
||||
|
||||
## Manual (local) building
|
||||
|
||||
You can also build the site yourself using Hugo, including a live local preview.
|
||||
|
||||
1. Make sure you install the latest version of Hugo, or at least the
|
||||
1. Make sure you install the latest version of Hugo, or hopefully at least the
|
||||
`min_version` listed in
|
||||
[theme.toml](https://github.com/BBaoVanC/bobatheme/blob/master/theme.toml#L11).
|
||||
Let me know if that minimum version isn't enough and I'll fix it.
|
||||
2. Clone the repo
|
||||
3. Make sure to download and checkout the submodules (use `git submodule update
|
||||
--init --recursive`). The `--recursive` flag is especially important because
|
||||
|
9
Caddyfile
Normal file
@ -0,0 +1,9 @@
|
||||
# vim: ft=caddyfile
|
||||
|
||||
https://localhost {
|
||||
header Cache-Control no-cache
|
||||
root * public/
|
||||
file_server {
|
||||
precompressed br gzip
|
||||
}
|
||||
}
|
97
LICENSE
@ -1,4 +1,4 @@
|
||||
Attribution-ShareAlike 4.0 International
|
||||
Attribution 4.0 International
|
||||
|
||||
=======================================================================
|
||||
|
||||
@ -54,18 +54,16 @@ exhaustive, and do not form part of our licenses.
|
||||
|
||||
=======================================================================
|
||||
|
||||
Creative Commons Attribution-ShareAlike 4.0 International Public
|
||||
License
|
||||
Creative Commons Attribution 4.0 International Public License
|
||||
|
||||
By exercising the Licensed Rights (defined below), You accept and agree
|
||||
to be bound by the terms and conditions of this Creative Commons
|
||||
Attribution-ShareAlike 4.0 International Public License ("Public
|
||||
License"). To the extent this Public License may be interpreted as a
|
||||
contract, You are granted the Licensed Rights in consideration of Your
|
||||
acceptance of these terms and conditions, and the Licensor grants You
|
||||
such rights in consideration of benefits the Licensor receives from
|
||||
making the Licensed Material available under these terms and
|
||||
conditions.
|
||||
Attribution 4.0 International Public License ("Public License"). To the
|
||||
extent this Public License may be interpreted as a contract, You are
|
||||
granted the Licensed Rights in consideration of Your acceptance of
|
||||
these terms and conditions, and the Licensor grants You such rights in
|
||||
consideration of benefits the Licensor receives from making the
|
||||
Licensed Material available under these terms and conditions.
|
||||
|
||||
|
||||
Section 1 -- Definitions.
|
||||
@ -84,11 +82,7 @@ Section 1 -- Definitions.
|
||||
and Similar Rights in Your contributions to Adapted Material in
|
||||
accordance with the terms and conditions of this Public License.
|
||||
|
||||
c. BY-SA Compatible License means a license listed at
|
||||
creativecommons.org/compatiblelicenses, approved by Creative
|
||||
Commons as essentially the equivalent of this Public License.
|
||||
|
||||
d. Copyright and Similar Rights means copyright and/or similar rights
|
||||
c. Copyright and Similar Rights means copyright and/or similar rights
|
||||
closely related to copyright including, without limitation,
|
||||
performance, broadcast, sound recording, and Sui Generis Database
|
||||
Rights, without regard to how the rights are labeled or
|
||||
@ -96,33 +90,29 @@ Section 1 -- Definitions.
|
||||
specified in Section 2(b)(1)-(2) are not Copyright and Similar
|
||||
Rights.
|
||||
|
||||
e. Effective Technological Measures means those measures that, in the
|
||||
d. Effective Technological Measures means those measures that, in the
|
||||
absence of proper authority, may not be circumvented under laws
|
||||
fulfilling obligations under Article 11 of the WIPO Copyright
|
||||
Treaty adopted on December 20, 1996, and/or similar international
|
||||
agreements.
|
||||
|
||||
f. Exceptions and Limitations means fair use, fair dealing, and/or
|
||||
e. Exceptions and Limitations means fair use, fair dealing, and/or
|
||||
any other exception or limitation to Copyright and Similar Rights
|
||||
that applies to Your use of the Licensed Material.
|
||||
|
||||
g. License Elements means the license attributes listed in the name
|
||||
of a Creative Commons Public License. The License Elements of this
|
||||
Public License are Attribution and ShareAlike.
|
||||
|
||||
h. Licensed Material means the artistic or literary work, database,
|
||||
f. Licensed Material means the artistic or literary work, database,
|
||||
or other material to which the Licensor applied this Public
|
||||
License.
|
||||
|
||||
i. Licensed Rights means the rights granted to You subject to the
|
||||
g. Licensed Rights means the rights granted to You subject to the
|
||||
terms and conditions of this Public License, which are limited to
|
||||
all Copyright and Similar Rights that apply to Your use of the
|
||||
Licensed Material and that the Licensor has authority to license.
|
||||
|
||||
j. Licensor means the individual(s) or entity(ies) granting rights
|
||||
h. Licensor means the individual(s) or entity(ies) granting rights
|
||||
under this Public License.
|
||||
|
||||
k. Share means to provide material to the public by any means or
|
||||
i. Share means to provide material to the public by any means or
|
||||
process that requires permission under the Licensed Rights, such
|
||||
as reproduction, public display, public performance, distribution,
|
||||
dissemination, communication, or importation, and to make material
|
||||
@ -130,13 +120,13 @@ Section 1 -- Definitions.
|
||||
public may access the material from a place and at a time
|
||||
individually chosen by them.
|
||||
|
||||
l. Sui Generis Database Rights means rights other than copyright
|
||||
j. Sui Generis Database Rights means rights other than copyright
|
||||
resulting from Directive 96/9/EC of the European Parliament and of
|
||||
the Council of 11 March 1996 on the legal protection of databases,
|
||||
as amended and/or succeeded, as well as other essentially
|
||||
equivalent rights anywhere in the world.
|
||||
|
||||
m. You means the individual or entity exercising the Licensed Rights
|
||||
k. You means the individual or entity exercising the Licensed Rights
|
||||
under this Public License. Your has a corresponding meaning.
|
||||
|
||||
|
||||
@ -182,13 +172,7 @@ Section 2 -- Scope.
|
||||
Licensed Rights under the terms and conditions of this
|
||||
Public License.
|
||||
|
||||
b. Additional offer from the Licensor -- Adapted Material.
|
||||
Every recipient of Adapted Material from You
|
||||
automatically receives an offer from the Licensor to
|
||||
exercise the Licensed Rights in the Adapted Material
|
||||
under the conditions of the Adapter's License You apply.
|
||||
|
||||
c. No downstream restrictions. You may not offer or impose
|
||||
b. No downstream restrictions. You may not offer or impose
|
||||
any additional or different terms or conditions on, or
|
||||
apply any Effective Technological Measures to, the
|
||||
Licensed Material if doing so restricts exercise of the
|
||||
@ -270,24 +254,9 @@ following conditions.
|
||||
information required by Section 3(a)(1)(A) to the extent
|
||||
reasonably practicable.
|
||||
|
||||
b. ShareAlike.
|
||||
|
||||
In addition to the conditions in Section 3(a), if You Share
|
||||
Adapted Material You produce, the following conditions also apply.
|
||||
|
||||
1. The Adapter's License You apply must be a Creative Commons
|
||||
license with the same License Elements, this version or
|
||||
later, or a BY-SA Compatible License.
|
||||
|
||||
2. You must include the text of, or the URI or hyperlink to, the
|
||||
Adapter's License You apply. You may satisfy this condition
|
||||
in any reasonable manner based on the medium, means, and
|
||||
context in which You Share Adapted Material.
|
||||
|
||||
3. You may not offer or impose any additional or different terms
|
||||
or conditions on, or apply any Effective Technological
|
||||
Measures to, Adapted Material that restrict exercise of the
|
||||
rights granted under the Adapter's License You apply.
|
||||
4. If You Share Adapted Material You produce, the Adapter's
|
||||
License You apply must not prevent recipients of the Adapted
|
||||
Material from complying with this Public License.
|
||||
|
||||
|
||||
Section 4 -- Sui Generis Database Rights.
|
||||
@ -302,9 +271,8 @@ apply to Your use of the Licensed Material:
|
||||
b. if You include all or a substantial portion of the database
|
||||
contents in a database in which You have Sui Generis Database
|
||||
Rights, then the database in which You have Sui Generis Database
|
||||
Rights (but not its individual contents) is Adapted Material,
|
||||
Rights (but not its individual contents) is Adapted Material; and
|
||||
|
||||
including for purposes of Section 3(b); and
|
||||
c. You must comply with the conditions in Section 3(a) if You Share
|
||||
all or a substantial portion of the contents of the database.
|
||||
|
||||
@ -407,21 +375,22 @@ Section 8 -- Interpretation.
|
||||
|
||||
=======================================================================
|
||||
|
||||
Creative Commons is not a party to its public licenses.
|
||||
Notwithstanding, Creative Commons may elect to apply one of its public
|
||||
licenses to material it publishes and in those instances will be
|
||||
considered the “Licensor.” The text of the Creative Commons public
|
||||
licenses is dedicated to the public domain under the CC0 Public Domain
|
||||
Dedication. Except for the limited purpose of indicating that material
|
||||
is shared under a Creative Commons public license or as otherwise
|
||||
permitted by the Creative Commons policies published at
|
||||
Creative Commons is not a party to its public
|
||||
licenses. Notwithstanding, Creative Commons may elect to apply one of
|
||||
its public licenses to material it publishes and in those instances
|
||||
will be considered the “Licensor.” The text of the Creative Commons
|
||||
public licenses is dedicated to the public domain under the CC0 Public
|
||||
Domain Dedication. Except for the limited purpose of indicating that
|
||||
material is shared under a Creative Commons public license or as
|
||||
otherwise permitted by the Creative Commons policies published at
|
||||
creativecommons.org/policies, Creative Commons does not authorize the
|
||||
use of the trademark "Creative Commons" or any other trademark or logo
|
||||
of Creative Commons without its prior written consent including,
|
||||
without limitation, in connection with any unauthorized modifications
|
||||
to any of its public licenses or any other arrangements,
|
||||
understandings, or agreements concerning use of licensed material. For
|
||||
the avoidance of doubt, this paragraph does not form part of the public
|
||||
licenses.
|
||||
the avoidance of doubt, this paragraph does not form part of the
|
||||
public licenses.
|
||||
|
||||
Creative Commons may be contacted at creativecommons.org.
|
||||
|
||||
|
@ -1,3 +1,8 @@
|
||||
# bbaovanc.com
|
||||
|
||||
My personal website, generated using [Hugo](https://gohugo.io)
|
||||
|
||||
## Discussions
|
||||
|
||||
Use [GitHub Discussions](https://github.com/BBaoVanC/bbaovanc.com/discussions)
|
||||
for questions, ideas, discussions, etc. relating to me or my website.
|
||||
|
121
assets/css/comments.css
Normal file
@ -0,0 +1,121 @@
|
||||
/* Isso styling */
|
||||
h4.isso-thread-heading {
|
||||
color: var(--text-0);
|
||||
margin-bottom: 8px;
|
||||
}
|
||||
|
||||
.isso-comment:not(:first-of-type),
|
||||
.isso-follow-up .isso-comment {
|
||||
border-color: var(--background-3);
|
||||
}
|
||||
|
||||
.isso-author,
|
||||
.isso-page-author-suffix,
|
||||
.isso-comment-footer,
|
||||
.isso-comment-footer .isso-votes {
|
||||
color: var(--text-gray-0);
|
||||
}
|
||||
|
||||
.isso-comment-header .isso-spacer,
|
||||
.isso-spacer:hover,
|
||||
.isso-permalink,
|
||||
.isso-permalink:hover {
|
||||
color: var(--text-gray-1) !important;
|
||||
}
|
||||
a.isso-author:hover,
|
||||
.isso-permalink:hover {
|
||||
text-decoration: underline !important;
|
||||
}
|
||||
|
||||
.isso-comment.isso-is-page-author > .isso-text-wrapper {
|
||||
background-color: var(--background-accent-1);
|
||||
}
|
||||
|
||||
.isso-feedlink:hover,
|
||||
.isso-reply {
|
||||
color: var(--link-0) !important;
|
||||
text-shadow: unset !important;
|
||||
}
|
||||
.isso-reply:hover {
|
||||
text-decoration: underline;
|
||||
}
|
||||
|
||||
.isso-text pre,
|
||||
.isso-text :not(pre) > code {
|
||||
background-color: var(--background-2);
|
||||
border: none;
|
||||
padding: 2px 4px;
|
||||
border-radius: 5px;
|
||||
/* thanks isso.css for setting this to 85% for whatever reason */
|
||||
font-size: 0.75em;
|
||||
}
|
||||
|
||||
.isso-input-wrapper input,
|
||||
.isso-post-action > input,
|
||||
.isso-textarea,
|
||||
.isso-preview {
|
||||
color: var(--text-1);
|
||||
background-color: var(--background-1);
|
||||
border-color: var(--background-2) !important;
|
||||
}
|
||||
|
||||
.isso-input-wrapper input:focus,
|
||||
.isso-textarea:focus {
|
||||
border-color: var(--background-3) !important;
|
||||
}
|
||||
|
||||
.isso-post-action > input:hover {
|
||||
background-color: var(--background-2);
|
||||
}
|
||||
.isso-post-action > input:focus,
|
||||
.isso-post-action > input:active {
|
||||
background-color: var(--background-3);
|
||||
}
|
||||
|
||||
.isso-textarea {
|
||||
margin-bottom: 4px;
|
||||
}
|
||||
.isso-input-wrapper {
|
||||
display: inline-flex;
|
||||
flex-direction: column;
|
||||
margin-right: 4px;
|
||||
max-width: 25%;
|
||||
}
|
||||
.isso-input-wrapper input {
|
||||
order: 1;
|
||||
}
|
||||
.isso-input-wrapper label {
|
||||
order: 2;
|
||||
font-size: small;
|
||||
}
|
||||
.isso-post-action {
|
||||
margin-left: 4px;
|
||||
margin-top: 0;
|
||||
}
|
||||
@media screen and (max-width: 600px) {
|
||||
.isso-input-wrapper {
|
||||
display: block;
|
||||
max-width: 100%;
|
||||
}
|
||||
}
|
||||
|
||||
@media print {
|
||||
.comments {
|
||||
break-before: always;
|
||||
}
|
||||
.isso-comment {
|
||||
max-width: unset;
|
||||
}
|
||||
.isso-text-wrapper {
|
||||
break-inside: avoid;
|
||||
}
|
||||
|
||||
.isso-postbox,
|
||||
.isso-feedlink {
|
||||
display: none;
|
||||
}
|
||||
}
|
||||
|
||||
.isso-target {
|
||||
animation: target-fade 10s ease-out; /* defined in bobatheme */
|
||||
}
|
3
assets/js/share-event.js
Normal file
@ -0,0 +1,3 @@
|
||||
function share_event(service) {
|
||||
plausible("Share", {props: {Network: service}});
|
||||
}
|
8
changed-urls.sh
Executable file
@ -0,0 +1,8 @@
|
||||
#!/bin/sh
|
||||
|
||||
diff -qrNtbB old/ new/ |
|
||||
grep -oP '(?<=\s)new\/\S*' |
|
||||
xargs -d '\n' ls -1d 2>/dev/null |
|
||||
grep 'index.html$' |
|
||||
sed 's/index.html$//' |
|
||||
sed "s/^new/${SCHEME:=http}:\/\/${DOMAIN:=example.com}/"
|
45
config.toml
@ -1,45 +0,0 @@
|
||||
baseURL = "https://bbaovanc.com"
|
||||
theme = "bobatheme"
|
||||
defaultContentLanguage = "en"
|
||||
copyright = '<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">CC BY-SA 4.0</a>'
|
||||
sectionPagesMenu = "main"
|
||||
enableRobotsTXT = true
|
||||
paginate = 5
|
||||
enableGitInfo = true
|
||||
|
||||
[author]
|
||||
name = "bbaovanc"
|
||||
email = "bbaovanc@bbaovanc.com"
|
||||
|
||||
[markup]
|
||||
[markup.highlight]
|
||||
noClasses = false
|
||||
lineNos = true
|
||||
|
||||
[params]
|
||||
# these are for the OpenGraph/Twitter embeds in Hugo
|
||||
description = "My personal website"
|
||||
|
||||
# these are for favicons in bobatheme
|
||||
faviconICO = "favicon.ico"
|
||||
faviconPNG = "favicon.png"
|
||||
|
||||
# show word count and/or reading time (enabled by default)
|
||||
wordcount = true
|
||||
readingtime = true
|
||||
|
||||
# used for last update
|
||||
repoURL = "https://github.com/BBaoVanC/bbaovanc.com"
|
||||
|
||||
[languages]
|
||||
[languages.en]
|
||||
languageName = "English"
|
||||
title = "bbaovanc's Website"
|
||||
weight = 1
|
||||
|
||||
[languages.es]
|
||||
languageName = "Español"
|
||||
title = "sitio web de bbaovanc"
|
||||
weight = 2
|
||||
[languages.es.params]
|
||||
description = "Mi sitio web personal"
|
84
config.yaml
Normal file
@ -0,0 +1,84 @@
|
||||
baseURL: https://bbaovanc.com
|
||||
theme: bobatheme
|
||||
defaultContentLanguage: en
|
||||
copyright: '© 2021-2023 bbaovanc <a rel="license" href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>'
|
||||
sectionPagesMenu: main
|
||||
enableRobotsTXT: true
|
||||
paginate: 10
|
||||
enableGitInfo: true
|
||||
|
||||
taxonomies:
|
||||
_merge: deep
|
||||
|
||||
author:
|
||||
name: bbaovanc
|
||||
|
||||
markup: # this just keeps the bobatheme markup styling
|
||||
_merge: deep
|
||||
|
||||
related:
|
||||
includeNewer: true
|
||||
indices:
|
||||
#- name: keywords
|
||||
# weight: 100
|
||||
- name: categories
|
||||
weight: 80
|
||||
- name: tags
|
||||
weight: 80
|
||||
- name: date
|
||||
weight: 10
|
||||
threshold: 80
|
||||
toLower: true
|
||||
|
||||
params:
|
||||
# these are for the OpenGraph/Twitter embeds in Hugo
|
||||
description: My personal website
|
||||
|
||||
# these are for favicons in bobatheme (disabled by default)
|
||||
faviconSVG: favicon.svg
|
||||
appleTouchPNG: apple-touch-icon.png
|
||||
|
||||
# show reading time (enabled by default)
|
||||
readingtime: true
|
||||
|
||||
# used for "View source" (unset by default)
|
||||
gitFileURL: https://github.com/BBaoVanC/bbaovanc.com/blob/master
|
||||
gitFileIcon: code
|
||||
gitHistoryURL: https://github.com/BBaoVanC/bbaovanc.com/commits/master
|
||||
|
||||
# display a "Latest Posts" section on the homepage below its content
|
||||
homepageLatestPosts: true
|
||||
|
||||
# social media share icons
|
||||
shareButtons:
|
||||
twitter: true
|
||||
facebook: true
|
||||
linkedin: true
|
||||
reddit: true
|
||||
telegram: true
|
||||
print: true
|
||||
|
||||
# show "Latest Posts" section at bottom of content pages
|
||||
# latestPostsOnContent: true
|
||||
|
||||
|
||||
footer: >-
|
||||
See the [anonymous and privacy-friendly
|
||||
analytics](https://plausible.bbaovanc.com/bbaovanc.com) for this site,
|
||||
powered by [Plausible](https://plausible.io).
|
||||
|
||||
# see https://gohugo.io/about/hugo-and-gdpr/#all-privacy-settings
|
||||
# you probably want to keep this default
|
||||
privacy:
|
||||
_merge: deep
|
||||
|
||||
languages:
|
||||
en:
|
||||
languageName: English
|
||||
title: bbaovanc's Website
|
||||
weight: 1
|
||||
menu:
|
||||
main:
|
||||
- identifier: status-page
|
||||
name: Status Page
|
||||
url: https://status.bbaovanc.com
|
@ -3,20 +3,31 @@
|
||||
title: Home
|
||||
|
||||
description: >-
|
||||
This is my website.
|
||||
This is my personal website, home to my blog. It's powered by my own custom
|
||||
theme named bobatheme, which is available at
|
||||
https://github.com/BBaoVanC/bobatheme.
|
||||
|
||||
---
|
||||
|
||||
## My Website
|
||||
|
||||
This is my website. Pretty self-explanatory.
|
||||
This is my personal website. I wrote it myself from scratch using [my own
|
||||
theme][bobatheme-github] and a static site generator named [Hugo][hugo-website].
|
||||
I occasionally write blog posts under the [blog section][blog-section].
|
||||
|
||||
## A fresh new theme
|
||||
[bobatheme-github]: https://github.com/BBaoVanC/bobatheme
|
||||
[hugo-website]: https://gohugo.io
|
||||
[blog-section]: {{< ref "/blog/" >}}
|
||||
|
||||
My website uses my own custom theme named
|
||||
[bobatheme](https://github.com/BBaoVanC/bobatheme). Although it's not quite
|
||||
finished yet, the current style will probably stay for the forseeable future.
|
||||
## Topics I write about
|
||||
|
||||
## Another website
|
||||
I write mostly about technology, including:
|
||||
|
||||
- Linux
|
||||
- Open Source Software
|
||||
- Programming
|
||||
- Web Development
|
||||
|
||||
## My other website
|
||||
|
||||
I also run another website: https://boba.best.
|
||||
|
@ -1,39 +0,0 @@
|
||||
---
|
||||
|
||||
title: Nueva sistema de comentarios (otra vez)
|
||||
date: 2021-04-17
|
||||
toc: true
|
||||
|
||||
tags:
|
||||
- announcement
|
||||
- hugo
|
||||
- blog
|
||||
|
||||
---
|
||||
|
||||
Decidí cambiar mi sistema de comentarios de Isso a
|
||||
[Commento](https://www.commento.io/).
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Isso vs Commento
|
||||
|
||||
Sé que sólo ser seís días desde añadí Isso, pero decidí cambiar a una sistema de
|
||||
comentarios mejor. Isso se supone que ser sencillo, lo que significa que falta
|
||||
muchas herramientas. Commento tiene un montón de herramientas, tal como
|
||||
comentarios fijados, detección de spam, cerrar cadenas, notificaciones en correo
|
||||
electrónico (no podía hacerlo funcionar en Isso), y un diseño más lindo. También
|
||||
podía implementar algunos [custom CSS rules][1], que ayudan parecer lindo en la
|
||||
tema de mi blog. También es compatible con SSO, así que puedo admitir registro
|
||||
con GitHub, y quizás GitLab.
|
||||
|
||||
## Sumario del primero posteo
|
||||
|
||||
Si no has leído el [Nueva sistema de comentarios](../new-comment-system) posteo,
|
||||
aquí es la información más importante. Hay un sección de comentarios en el fondo
|
||||
de cada posteo donde puedes ver y publicar comentarios. Puedes comentar
|
||||
anónimamente, o crear una cuenta para mostrar tu nombre de usario y recibir
|
||||
notificaciones en correo electrónico. También puedes votar y responder a otras
|
||||
comentarios.
|
||||
|
||||
[1]: https://git.bbaovanc.com/bbaovanc.com/blog/src/commit/478e15218313a33216d361de387b3bd878cd0ba6/assets/css/comments.css
|
@ -1,41 +0,0 @@
|
||||
---
|
||||
|
||||
title: Nueva sistema de comentarios
|
||||
date: 2021-04-11
|
||||
toc: true
|
||||
|
||||
tags:
|
||||
- announcement
|
||||
- hugo
|
||||
- blog
|
||||
|
||||
---
|
||||
|
||||
Añadí una nueva sistema de comentarios a mi blog usando
|
||||
[Isso](https://posativ.org/isso/).
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Sobre
|
||||
|
||||
Instalé una sistema de comentarios que se llama
|
||||
[Isso](https://posativ.org/isso/) en mi blog hoy. En el fondo de cada entrada de
|
||||
blog, hay un sección de comentarios. Puedes comentar anónimamente, o mostrar tu
|
||||
nombre, dirección de correo electrónico, y/o sito web, que será mostrado a otras
|
||||
personas que están leyendo tu comentario. No pienso que nadie va a maltratar la
|
||||
sistema de comentarios porque mi sitio web es tan pequeña.
|
||||
|
||||
## Problemas conocidas
|
||||
|
||||
### Editar y eliminar no funciona
|
||||
|
||||
La sistema se supone que dejarte editar y eliminar tus comentarios 15 minutos
|
||||
después de enviarlos, pero no funciona ahora. La solicitud sólo responde un
|
||||
error de 403 (prohibido).
|
||||
|
||||
### Texto blanco enfrente de un fondo blanco en vista preliminar
|
||||
|
||||
Esto es una problema de CSS. También pasaba cuando editando y escribiendo un
|
||||
comentario, pero lo edité así que la caja de texto tiene texto negro. Yo pienso
|
||||
que una solución mejor es usar un fondo negro en el formulario comentario, pero
|
||||
arreglaré luego.
|
8
content/authors/_index.md
Normal file
@ -0,0 +1,8 @@
|
||||
---
|
||||
|
||||
title: Authors
|
||||
|
||||
description: >-
|
||||
List of authors on my website.
|
||||
|
||||
---
|
11
content/authors/bbaovanc/_index.md
Normal file
@ -0,0 +1,11 @@
|
||||
---
|
||||
|
||||
title: bbaovanc
|
||||
issoUserID: 284513e38f5c
|
||||
|
||||
---
|
||||
|
||||
I think you can probably tell from the website URL that I'm the one who owns
|
||||
this website.
|
||||
|
||||
<!--more-->
|
10
content/authors/github-copilot/_index.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
|
||||
title: GitHub Copilot
|
||||
|
||||
---
|
||||
|
||||
More information at https://copilot.github.com/. See [this
|
||||
post](/blog/copilot-post) for how I did it.
|
||||
|
||||
<!--more-->
|
@ -1,8 +0,0 @@
|
||||
---
|
||||
|
||||
title: Blog
|
||||
|
||||
description: >-
|
||||
Mis entradas de blog
|
||||
|
||||
---
|
@ -3,6 +3,6 @@
|
||||
title: Blog
|
||||
|
||||
description: >-
|
||||
My blog posts
|
||||
The home of my blog.
|
||||
|
||||
---
|
||||
|
@ -1,27 +1,35 @@
|
||||
---
|
||||
|
||||
title: Allow non root processes to bind to privileged ports in Linux
|
||||
date: 2021-03-28
|
||||
date: 2021-03-28T21:29:52-05:00
|
||||
lastmod: 2022-05-02T01:05:44-05:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
aliases:
|
||||
- posts/allow-non-root-processes-to-bind-to-privileged-ports/
|
||||
|
||||
tags:
|
||||
- guide
|
||||
categories:
|
||||
- guides
|
||||
- linux
|
||||
|
||||
tags:
|
||||
- gitea
|
||||
- systemd
|
||||
|
||||
---
|
||||
|
||||
In Linux, processes cannot bind to privileged ports (<=1024) unless they are
|
||||
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.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Introduction
|
||||
|
||||
In Linux, processes cannot bind to privileged ports (<=1024) unless they are
|
||||
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
|
||||
@ -31,9 +39,9 @@ executable itself.
|
||||
|
||||
### 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:
|
||||
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[^systemd-set-capabilities] that are commented out:
|
||||
|
||||
```systemd
|
||||
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
|
||||
@ -45,7 +53,7 @@ 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]:
|
||||
allowing it to bind to any port. Run the following command[^setcap-command]:
|
||||
|
||||
```bash
|
||||
setcap 'cap_net_bind_service=+ep' /path/to/program
|
||||
@ -54,7 +62,7 @@ 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]:
|
||||
Other caveats[^caveats-quote]:
|
||||
|
||||
> 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
|
||||
@ -67,6 +75,10 @@ Other caveats[^2]:
|
||||
> 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
|
||||
|
||||
[^systemd-set-capabilities]: See [these two lines in the Gitea systemd service
|
||||
file](https://github.com/go-gitea/gitea/blob/3416e2a82586fca4cd452b93237b979300f55d62/contrib/systemd/gitea.service#L69)
|
||||
and [this Stack Overflow answer](https://stackoverflow.com/a/47065825).
|
||||
|
||||
[^setcap-command]: https://stackoverflow.com/a/414258
|
||||
[^caveats-quote]: https://stackoverflow.com/a/414258
|
||||
|
After Width: | Height: | Size: 14 KiB |
@ -0,0 +1,144 @@
|
||||
---
|
||||
|
||||
title: Using GitHub Actions to audit my website with Google Chrome Lighthouse
|
||||
date: 2022-05-07T00:54:11-05:00
|
||||
lastmod: 2022-05-08T16:16:02-05:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
- devops
|
||||
- meta
|
||||
|
||||
tags:
|
||||
- caddy
|
||||
- github-actions
|
||||
- google-lighthouse
|
||||
|
||||
# this will be shown for the article in list pages and in the page metadata
|
||||
# it can be either an image or video (this might change in the future, however)
|
||||
resources:
|
||||
- name: feature
|
||||
src: dashboard-performance-graph.webp
|
||||
title: Picture of the `Performance` section on the Lighthouse CI dashboard
|
||||
|
||||
- name: youtube-embed-performance-comparison
|
||||
src: youtube-embed-performance-comparison.webp
|
||||
title: >-
|
||||
Performance hit caused by adding a YouTube embed. You can see the
|
||||
comparison itself [on this comparison
|
||||
page](https://lhci.bbaovanc.com/app/projects/bbaovanc.com/compare/01d2064b6fac?baseUrl=https%3A%2F%2Flocalhost%2Fblog%2Fthe-redesign-of-my-website%2F&compareUrl=https%3A%2F%2Flocalhost%2Fblog%2Fyoutube-url-structures-you-should-know%2F&baseBuild=01d2064b-6fac-40df-b4e6-373037ae1f9e).
|
||||
|
||||
---
|
||||
|
||||
The other day I set up automatic testing of my website using [Google Chrome
|
||||
Lighthouse][google-lighthouse]. I'm also running my own Lighthouse CI server to
|
||||
store test result history and show trends. Here's an outline of what this means,
|
||||
some of the results I've obtained so far, and my thoughts on the usefulness of
|
||||
Lighthouse.
|
||||
|
||||
[google-lighthouse]: https://developers.google.com/web/tools/lighthouse
|
||||
|
||||
<!--more-->
|
||||
|
||||
## What is Lighthouse?
|
||||
|
||||
Lighthouse is a tool developed by Google which audits websites and gives them a
|
||||
score in four categories: *Performance*, *Accessibility*, *Best Practices*, and
|
||||
*SEO (search engine optimization)*. It's also built into the developer console
|
||||
in Chrome, so you can run it manually on any website you want directly inside
|
||||
your browser.
|
||||
|
||||
I have already been using Lighthouse manually to do occasional tests on my
|
||||
website and its theme, [bobatheme][bobatheme]. However, I recently came across
|
||||
[this GitHub Action][lhci-action]. It caught my eye because I was [already using
|
||||
GitHub Actions][old-audit-workflow] to perform a few basic Hugo[^hugo]-related
|
||||
audits found [in a thread on the Hugo forum][hugo-audits-thread].
|
||||
|
||||
[^hugo]: [Hugo](https://gohugo.io) is the framework that my website is built on. It's
|
||||
a static site generator which generates my site according to my own custom
|
||||
templates that make up my theme.
|
||||
|
||||
[bobatheme]: https://github.com/BBaoVanC/bobatheme
|
||||
[lhci-action]: https://github.com/marketplace/actions/lighthouse-ci-action
|
||||
[old-audit-workflow]: https://github.com/BBaoVanC/bbaovanc.com/blob/31e25c2578a789afe71ce90352747eb427ca3c0e/.github/workflows/audit.yml#L31-L59
|
||||
[hugo-audits-thread]: https://discourse.gohugo.io/t/audit-your-published-site-for-problems/35184
|
||||
|
||||
## Setting it all up
|
||||
|
||||
My goal is to run Lighthouse's audits on an environment as similar to my real
|
||||
website's deployment as possible.
|
||||
|
||||
First, I [created a separate `lighthouse` job on my audit
|
||||
workflow][lighthouse-actions-job] on GitHub Actions. This job will do all of the
|
||||
testing. Since it's a separate job, it runs in parallel with my existing audit
|
||||
task.
|
||||
|
||||
[lighthouse-actions-job]: https://github.com/BBaoVanC/bbaovanc.com/blob/3668b6cfb11d09149b5da347219cdc75d0ce0985/.github/workflows/audit.yml#L7
|
||||
|
||||
Next, I copied [my existing build steps verbatim][production-build-steps]. This
|
||||
makes the site effectively identical to my real deployment on bbaovanc.com. One
|
||||
of the crucial steps is to pre-compress all the files so their compressed
|
||||
versions can be served without the server having to compress them on-the-fly,
|
||||
saving valuable processing power.
|
||||
|
||||
[production-build-steps]: https://github.com/BBaoVanC/bbaovanc.com/blob/db65e9fc23b840429f5c9ad2b43d7dd01a024f36/.github/workflows/deploy.yml#L22-L33
|
||||
|
||||
Serving the compressed files is crucial because it simulates the real world
|
||||
transfer size of the files. In addition, Lighthouse will recommend that you
|
||||
serve the files compressed.
|
||||
|
||||
Inside the audit environment I use the same webserver (Caddy) and a [similar
|
||||
configuration][audit-caddy-config] (compared to the [one running on
|
||||
bbaovanc.com][production-caddy-config]) to what I have running on bbaovanc.com.
|
||||
Caddy also is able to easily run the demo site with HTTPS, even on localhost.
|
||||
That allows it to test certain elements (such as the comment section) that
|
||||
wouldn't be allowed to load if it were plain, unsecured HTTP.
|
||||
|
||||
[audit-caddy-config]: https://github.com/BBaoVanC/bbaovanc.com/blob/3668b6cfb11d09149b5da347219cdc75d0ce0985/Caddyfile
|
||||
[production-caddy-config]: https://git.bbaovanc.com/configs/caddy/src/commit/e3227eb2a2679e27545c2417c2565941f03fb744/conf.d/bbaovanc.com
|
||||
|
||||
{{< see-also "/blog/caddy-is-the-best-webserver" >}}
|
||||
|
||||
I selected [a few significant pages on my website][lighthouse-urls] so
|
||||
Lighthouse can test a wide range of the features in my website's theme. The
|
||||
results of these tests are then uploaded to [my Lighthouse CI
|
||||
server][lhci-dashboard]. There you can view the audit history and see
|
||||
differences in results between builds.
|
||||
|
||||
[lighthouse-urls]: https://github.com/BBaoVanC/bbaovanc.com/blob/3668b6cfb11d09149b5da347219cdc75d0ce0985/lighthouserc.yaml#L4-L19
|
||||
[lhci-dashboard]: https://lhci.bbaovanc.com/app/projects/bbaovanc.com/dashboard
|
||||
|
||||
## What I found from the tests
|
||||
|
||||
### Performance impact of a YouTube video
|
||||
|
||||
I found that embedding a YouTube video using the built-in shortcode in Hugo
|
||||
made the website drastically slower. It's a lot clearer in the audit environment
|
||||
where everything is throttled down a bunch, so the performance impact is more
|
||||
clear. Below is a screenshot of the difference in score between my blog post
|
||||
with a YouTube embed and a similarly sized blog post which has no video.
|
||||
|
||||
{{< figure src="youtube-embed-performance-comparison" >}}
|
||||
|
||||
I can probably optimize this a little by making a copy of the built-in Hugo
|
||||
YouTube shortcode, and modifying it to defer the loading of the remote scripts.
|
||||
That will have to be a future project, and I'll probably write a post if I ever
|
||||
end up testing it.
|
||||
|
||||
## My thoughts on Lighthouse
|
||||
|
||||
You can make the argument that the results from Lighthouse don't really mean
|
||||
much in the real world. On modern devices and a decent internet speed most
|
||||
websites will load just fine.
|
||||
|
||||
Although most pages on my site have a perfect score from Lighthouse, I'm not
|
||||
going to go way out of my way in order to keep it that way. After all,
|
||||
Lighthouse is just a tool intended for "improving the quality of web
|
||||
pages."[^improve-quality-quote] That doesn't mean it needs to be perfect.
|
||||
|
||||
[^improve-quality-quote]: Source: [Google
|
||||
Developers](https://developers.google.com/web/tools/lighthouse)
|
After Width: | Height: | Size: 33 KiB |
105
content/blog/blog-post-newsletter/index.md
Normal file
@ -0,0 +1,105 @@
|
||||
---
|
||||
|
||||
title: Newsletter for my blog posts
|
||||
date: 2022-04-30T01:00:14-05:00
|
||||
lastmod: 2022-05-23T02:17:47-05:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
- meta
|
||||
|
||||
tags:
|
||||
- bobanews
|
||||
- listmonk
|
||||
- newsletter
|
||||
|
||||
# this will be shown for the article in list pages and in the page metadata
|
||||
# it can be either an image or video (this might change in the future, however)
|
||||
resources:
|
||||
- name: feature
|
||||
src: listmonk-bobatheme-template.webp
|
||||
title: My custom newsletter template based on my website's custom theme.
|
||||
|
||||
- name: listmonk-splash
|
||||
src: listmonk-splash.webp
|
||||
title: >-
|
||||
Dashboard on listmonk ---
|
||||
[source](https://listmonk.app/static/images/splash.png)
|
||||
|
||||
---
|
||||
|
||||
I created a newsletter for blog posts on my website so you can sign up for email
|
||||
notifications when I post new ones, so I have more than just an RSS feed.
|
||||
|
||||
<!--more-->
|
||||
|
||||
{{< aside warning >}}
|
||||
I decided that I didn't really want to deal with the extra work of managing a
|
||||
newsletter so I've removed it. (I didn't actually get any sign-ups).
|
||||
{{< /aside >}}
|
||||
|
||||
**See the ["Signing Up" section]({{< ref "#signing-up" >}}) for instructions on
|
||||
how to sign up for the newsletter.**
|
||||
|
||||
## Choosing the right mailing list manager
|
||||
|
||||
For my newsletter manager, I chose [listmonk](https://listmonk.app/). As I was
|
||||
searching for self-hosted newsletter managers, it caught my eye because of how
|
||||
modern and beautiful its interface looks. In fact, it was the only self-hosted
|
||||
newsletter/mailing list manager I looked at that doesn't have an overall old and
|
||||
ugly interface. Additionally, it has a live demo, so I was able to test it out
|
||||
and see if it would be able to meet my (relatively low) requirements.
|
||||
|
||||
{{< figure src="listmonk-splash" >}}
|
||||
|
||||
I also tried out [GNU Mailman 3](https://www.list.org/) about a year ago.
|
||||
However, I could not get it to integrate cleanly with my email
|
||||
server[^mailman-mailcow]. listmonk can operate over SMTP, just like any other
|
||||
program that sends mail. That makes the setup much less complicated, and I was
|
||||
also able to set up the [official Docker
|
||||
image](https://listmonk.app/docs/installation/#docker) using Docker Compose
|
||||
setup just like the other programs I use.
|
||||
|
||||
If you're interested, the Docker Compose configuration files I ended up writing
|
||||
are available at [configs/listmonk on my Gitea
|
||||
instance](https://git.bbaovanc.com/configs/listmonk).
|
||||
|
||||
## Newsletter formatting
|
||||
|
||||
I ended up writing my own template for listmonk from scratch, based on the CSS
|
||||
used in [bobatheme](https://github.com/BBaoVanC/bobatheme), the theme that my
|
||||
website uses. Here's a screenshot of how it currently looks:
|
||||
|
||||
{{< figure src="feature" >}}
|
||||
|
||||
## Signing up
|
||||
|
||||
{{< aside warning >}}
|
||||
I decided that I didn't really want to deal with the extra work of managing a
|
||||
newsletter so I've removed it. (I didn't actually get any sign-ups anyways.)
|
||||
{{< /aside >}}
|
||||
|
||||
You can sign up to get emails about new posts on the [newsletter signup form
|
||||
here](https://lists.bbaovanc.com/subscription/form). Make sure the box next to
|
||||
the list labeled `bbaovanc.com Blog Posts` is checked. You'll need to provide an
|
||||
email address, and optionally a nickname (or your real name if you want).
|
||||
|
||||
Right now there's only one list with public signup enabled, but that may change
|
||||
if you're reading this in the future. In that case, you can sign up for as many
|
||||
or as few lists as you want.
|
||||
|
||||
|
||||
|
||||
[^mailman-mailcow]: Mailman requires access to the mail server over
|
||||
[LMTP](https://en.wikipedia.org/wiki/Local_Mail_Transfer_Protocol). However,
|
||||
giving it access to my mail server over LMTP is not very easy because of the
|
||||
setup that [Mailcow](https://mailcow.email) (my email server) uses. There *is*
|
||||
an existing project called
|
||||
[dockerized-mailcow-mailman](https://github.com/g4rf/dockerized-mailcow-mailman),
|
||||
but it uses the Apache web server to serve the frontend. I'm not familiar with
|
||||
Apache, and also I don't really want to complicate my Mailcow setup switching
|
||||
to an almost completely different setup just for one little program.
|
After Width: | Height: | Size: 13 KiB |
BIN
content/blog/blog-post-newsletter/listmonk-splash.webp
Normal file
After Width: | Height: | Size: 24 KiB |
BIN
content/blog/caddy-is-the-best-webserver/caddy-browse.webp
Normal file
After Width: | Height: | Size: 13 KiB |
BIN
content/blog/caddy-is-the-best-webserver/caddy.webp
Normal file
After Width: | Height: | Size: 42 KiB |
235
content/blog/caddy-is-the-best-webserver/index.md
Normal file
@ -0,0 +1,235 @@
|
||||
---
|
||||
|
||||
title: Caddy is literally the best webserver
|
||||
date: 2021-11-13T00:43:35-06:00
|
||||
lastmod: 2023-01-16T20:57:00-06:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
- linux
|
||||
- sysadmin
|
||||
- software
|
||||
|
||||
tags:
|
||||
- caddy
|
||||
- webserver
|
||||
|
||||
resources:
|
||||
- name: feature
|
||||
src: caddy.webp
|
||||
title: >-
|
||||
Image source:
|
||||
[Caddy](https://caddyserver.com/resources/images/caddy-logo.svg)
|
||||
|
||||
- name: caddy-browse
|
||||
src: caddy-browse.webp
|
||||
title: >-
|
||||
Caddy's gorgeous directory list page.
|
||||
|
||||
---
|
||||
|
||||
After switching from NGINX to Caddy on all of my websites, I have come to the
|
||||
conclusion that Caddy is the best webserver in existence. With automatic HTTPS,
|
||||
a simple configuration file, and more, Caddy is just the best webserver overall
|
||||
for general use.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Built-in automatic HTTPS
|
||||
|
||||
Caddy can fetch certificates from Let's Encrypt and ZeroSSL out of the box.
|
||||
HTTPS is enabled by default for eligible domains[^hostname-requirements], unless
|
||||
you explicitly tell it not to.
|
||||
|
||||
### Incredible cipher security
|
||||
|
||||
Caddy has incredible defaults for TLS/SSL ciphers. Any site you host on Caddy
|
||||
gets a perfect score from [Qualys SSL Labs](https://www.ssllabs.com/ssltest/)
|
||||
out of the box.[^caddy-qualys-score]
|
||||
|
||||
## Dead simple configuration files: Caddy vs NGINX
|
||||
|
||||
Caddy's configuration file format is the easiest out of all the main webserver.
|
||||
The best way for me to demonstrate this simplicity is to compare it to one of
|
||||
the most popular webservers: [NGINX](https://www.nginx.com/).
|
||||
|
||||
### Serving some static files
|
||||
|
||||
The most essential feature you can use a webserver for.
|
||||
|
||||
#### Caddy
|
||||
|
||||
```caddyfile
|
||||
example.com {
|
||||
root * /var/www/example.com
|
||||
file_server
|
||||
}
|
||||
```
|
||||
|
||||
#### NGINX
|
||||
|
||||
```nginx
|
||||
server {
|
||||
listen 80;
|
||||
server_name example.com;
|
||||
index index.html index.txt;
|
||||
root /var/www/example.com;
|
||||
location / {
|
||||
try_files $uri $uri/ =404;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
As you can see, the Caddy config is a lot simpler than the NGINX one. But wait,
|
||||
there's more! This NGINX config is unencrypted HTTP only, but the Caddy one will
|
||||
automatically request a certificate from Let's Encrypt, enable HTTPS, and even
|
||||
redirect unencrypted HTTP to HTTPS.
|
||||
|
||||
From now on, for the sake of simplicity, I'll be ignoring HTTPS for the NGINX
|
||||
configs.
|
||||
|
||||
### PHP (PrivateBin)
|
||||
|
||||
The Caddy config for this example is the same as the [one used for
|
||||
bin.boba.best](https://git.boba.best/boba.best/caddy/src/commit/cd00151fbdd784979a8a181980cc36061be68c7d/conf.d/bin.boba.best).
|
||||
I've stripped it down a bit by removing the [custom error
|
||||
pages](https://git.boba.best/boba.best/caddy/src/commit/cd00151fbdd784979a8a181980cc36061be68c7d/Caddyfile#L15-L24),
|
||||
[HSTS](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security), [zstd
|
||||
compression](https://github.com/facebook/zstd), and logging.
|
||||
|
||||
#### Caddy
|
||||
|
||||
```caddyfile
|
||||
bin.boba.best {
|
||||
encode gzip
|
||||
|
||||
root * /var/www/bin.boba.best
|
||||
php_fastcgi unix//run/php/php-fpm.sock
|
||||
file_server
|
||||
}
|
||||
```
|
||||
|
||||
#### NGINX
|
||||
|
||||
```nginx
|
||||
server {
|
||||
listen 80;
|
||||
server_name bin.boba.best;
|
||||
index index.html index.txt index.php;
|
||||
root /var/www/bin.boba.best;
|
||||
gzip on;
|
||||
|
||||
location / {
|
||||
try_files $uri $uri/ =404;
|
||||
}
|
||||
|
||||
location ~ \.php$ {
|
||||
include snippets/fastcgi-php.conf;
|
||||
fastcgi_pass unix:/run/php/php-fpm.sock;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Reverse proxy + static files (Gitea)
|
||||
|
||||
This last example is based on
|
||||
[git.bbaovanc.com](https://git.bbaovanc.com/boba.best/caddy/src/commit/57c9f0011eae92ef5fa2992d99f01b0956802d64/conf.d/git.bbaovanc.com).
|
||||
Just like the last example, I've stripped off the custom error pages, HSTS, zstd
|
||||
compression, and logging.
|
||||
|
||||
#### Caddy
|
||||
|
||||
```caddyfile
|
||||
git.bbaovanc.com {
|
||||
encode gzip
|
||||
|
||||
handle_path /_/static/assets/* {
|
||||
root * /var/www/git.bbaovanc.com/public
|
||||
file_server
|
||||
}
|
||||
|
||||
handle {
|
||||
reverse_proxy localhost:81 {
|
||||
header_up X-Real-IP {remote_host}
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
#### NGINX
|
||||
|
||||
```nginx
|
||||
server {
|
||||
listen 80;
|
||||
server_name git.bbaovanc.com;
|
||||
gzip on;
|
||||
|
||||
location /_/static/assets {
|
||||
alias /var/www/git.bbaovanc.com/public/;
|
||||
}
|
||||
|
||||
location / {
|
||||
proxy_pass http://localhost:81;
|
||||
proxy_set_header X-Real-IP $remote_addr;
|
||||
}
|
||||
```
|
||||
|
||||
Although in this case the NGINX config was slightly shorter, I find the Caddy
|
||||
one a lot more clear and easy to understand. With NGINX, I find it weird how
|
||||
adding a trailing slash or not defines whether the prefix (`/_/static/assets` in
|
||||
this case) is stripped before searching the filesystem. In Caddy, you can use
|
||||
the `handle_path` directive, instead of just a regular `handle` directive.
|
||||
|
||||
You can read more about how `handle` and `handle_path` work in Caddy on the
|
||||
[Caddy docs](https://caddyserver.com/docs/caddyfile/directives/handle).
|
||||
|
||||
## The smaller details
|
||||
|
||||
These features might not matter to you, but this is my blog, and I care about
|
||||
them, so I'll be including them.
|
||||
|
||||
### Go templates
|
||||
|
||||
Caddy is written in Go and supports [Go
|
||||
templates](https://pkg.go.dev/text/template). This means you can make simple
|
||||
dynamic content while only using Caddy!
|
||||
|
||||
In fact, the [official Caddy website](https://caddyserver.com) is generated
|
||||
entirely using Caddy's and Go templates![^caddy-templating]
|
||||
|
||||
#### Error pages using HTTP Cats
|
||||
|
||||
I use [this
|
||||
snippet](https://git.bbaovanc.com/boba.best/caddy/src/commit/57c9f0011eae92ef5fa2992d99f01b0956802d64/Caddyfile#L8-L15)
|
||||
on both bbaovanc.com and boba.best to make custom error pages using images from
|
||||
[HTTP Cats](https://http.cat). It uses Caddy's template support to generate some
|
||||
simple HTML to show the error code, name, and cat image.
|
||||
|
||||
### Beautiful autoindex file browser
|
||||
|
||||
Apache and NGINX both have an optional "autoindex" feature which generates a
|
||||
list of files in a directory when there's no page there. However, it looks very
|
||||
ugly. Caddy, on the other hand, still has a simple index page, but looks a
|
||||
thousand times better.
|
||||
|
||||
Coincidentally, it matches the theme of my website very well, so I have to put a
|
||||
border around the image.
|
||||
|
||||
{{< figure src="caddy-browse" >}}
|
||||
|
||||
|
||||
[^hostname-requirements]: For the rules on what domains have automatic HTTPS by
|
||||
default, see ["Hostname requirements" on the Caddy
|
||||
documentation](https://caddyserver.com/docs/automatic-https#hostname-requirements).
|
||||
|
||||
[^caddy-qualys-score]: SSL Labs caps the score to an A if HSTS isn't enabled.
|
||||
After enabling it, then you get a perfect A+ score. See [my website's
|
||||
score](https://www.ssllabs.com/ssltest/analyze.html?d=bbaovanc.com&latest)
|
||||
([archived](https://archive.today/4JJDN)) for an example (bbaovanc.com).
|
||||
|
||||
[^caddy-templating]: See more info about templating [on the Caddy
|
||||
docs](https://caddyserver.com/docs/caddyfile/directives/templates#examples)
|
@ -1,18 +1,24 @@
|
||||
---
|
||||
|
||||
title: Checkra1n GUI on other Linux distros
|
||||
date: 2021-03-25
|
||||
date: 2021-03-25T21:19:51-05:00
|
||||
lastmod: 2021-10-16T21:25:38-05:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
aliases:
|
||||
- posts/checkra1n-gui-on-other-distros/
|
||||
|
||||
tags:
|
||||
- guide
|
||||
- linux
|
||||
- archlinux
|
||||
categories:
|
||||
- guides
|
||||
- jailbreak
|
||||
- linux
|
||||
|
||||
tags:
|
||||
- arch-linux
|
||||
- checkra1n
|
||||
|
||||
resources:
|
||||
|
342
content/blog/copilot-post/index.md
Normal file
@ -0,0 +1,342 @@
|
||||
---
|
||||
|
||||
# this is the title it generated. not even joking
|
||||
title: Copilot
|
||||
date: 2021-11-07T16:20:15-06:00
|
||||
lastmod: 2021-11-07T16:20:15-06:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- GitHub Copilot
|
||||
|
||||
categories:
|
||||
|
||||
tags:
|
||||
- github-copilot
|
||||
|
||||
series:
|
||||
- github-copilot-experiments
|
||||
|
||||
_build:
|
||||
list: never
|
||||
|
||||
---
|
||||
|
||||
Did you know that Copilot is a command line interface for Copilot? It's a tool
|
||||
for creating and managing Copilot projects.
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
||||
{{< aside >}}
|
||||
## What is this post?
|
||||
|
||||
I used [GitHub Copilot](https://copilot.github.com/) to write everything. All I
|
||||
did myself (being a human) was write a couple words and let it finish it off.
|
||||
I'll put any text that I wrote myself in an "aside" box, like you can see on
|
||||
this paragraph.
|
||||
{{< /aside >}}
|
||||
|
||||
## What is Copilot?
|
||||
|
||||
Copilot is a [Cloud Native
|
||||
Computing](https://en.wikipedia.org/wiki/Cloud_computing). It's used for
|
||||
managing the lifecycle of your application. It's also used as a tool for
|
||||
creating and managing Copilot projects.
|
||||
|
||||
## What is this?
|
||||
|
||||
This is an article about [GitHub Copilot]() and the Copilot CLI. It's a tool for
|
||||
creating and managing Copilot projects. I wrote it to help me learn the [GitHub
|
||||
Copilot API]() and to learn how to use the CLI. You can read more about the API
|
||||
[here](https://developer.github.com/v4/explorer/). Next time you want to learn
|
||||
more about Copilot, check out the [GitHub Copilot
|
||||
docs](https://developer.github.com/apps/copilot/).
|
||||
|
||||
## Why is this?
|
||||
|
||||
Because I'm a developer and I like to learn new things. This is a tool I wrote
|
||||
to learn how the Copilot API works. It's a tool for creating and managing
|
||||
Copilot projects. I wrote it to help me learn the [GitHub Copilot API]() and to
|
||||
learn how to use the CLI. You can read more about the API
|
||||
[here](https://developer.github.com/v4/explorer/). Next time you want to learn
|
||||
more about Copilot, check out the [GitHub Copilot
|
||||
docs](https://developer.github.com/apps/copilot/). It's a tool for creating and
|
||||
managing Copilot projects. I wrote it to help me learn the [GitHub Copilot
|
||||
API]() and to learn how to use the CLI. You can read more about the API
|
||||
[here](https://developer.github.com/v4/explorer/). Next time you want to learn
|
||||
more about Copilot, check out the [GitHub Copilot
|
||||
docs](https://developer.github.com/apps/copilot/).
|
||||
|
||||
## How did I write this?
|
||||
|
||||
I used [Hugo](https://gohugo.io/) to write this article. It's a static site
|
||||
generator that makes it easy to create and manage a blog. GitHub Copilot is what
|
||||
I use to create and manage Copilot projects.
|
||||
|
||||
## How do I use this?
|
||||
|
||||
Here's how you use this. You can read more about the CLI
|
||||
[here](https://developer.github.com/apps/copilot/). You can read more about the
|
||||
API [here](https://developer.github.com/v4/explorer/). Next time you want to
|
||||
learn more about Copilot, check out the [GitHub Copilot
|
||||
docs](https://developer.github.com/apps/copilot/). It's a tool for creating and
|
||||
managing Copilot projects. I wrote it to help me learn the [GitHub Copilot
|
||||
API]() and to learn how to use the CLI. You can read more about the API
|
||||
[here](https://developer.github.com/v4/explorer/). Next time you want to learn
|
||||
more about Copilot, check out the [GitHub Copilot
|
||||
docs](https://developer.github.com/apps/copilot/). Did you know that Copilot is
|
||||
a command line interface for Copilot? It's a tool for creating and managing
|
||||
Copilot projects. It's not a tool for creating and managing Copilot projects.
|
||||
It's a tool for creating and managing Copilot projects. I wrote it to help me
|
||||
learn the [GitHub Copilot API]() and to learn how to use the CLI. You can read
|
||||
more about the API [here](https://developer.github.com/v4/explorer/). Next time
|
||||
you want to learn more about Copilot, check out the [GitHub Copilot
|
||||
docs](https://developer.github.com/apps/copilot/).
|
||||
|
||||
## What do I need to know?
|
||||
|
||||
* You need a GitHub account
|
||||
* You need to have a GitHub Copilot API key
|
||||
* You need to have a GitHub Copilot CLI
|
||||
* You need to have a GitHub Copilot project
|
||||
|
||||
## How do I create a project?
|
||||
|
||||
1. Create a project on [GitHub
|
||||
Copilot](https://developer.github.com/apps/copilot/).
|
||||
2. Create a project on [GitHub
|
||||
Copilot](https://developer.github.com/apps/copilot/).
|
||||
3. Create a project on [GitHub
|
||||
Copilot](https://developer.github.com/apps/copilot/).
|
||||
|
||||
## How do I delete a project?
|
||||
|
||||
1. Delete a project on [GitHub
|
||||
Copilot](https://developer.github.com/apps/copilot/).
|
||||
2. Delete a project on [GitHub
|
||||
Copilot](https://developer.github.com/apps/copilot/).
|
||||
3. Delete a project on [GitHub
|
||||
Copilot](https://developer.github.com/apps/copilot/).
|
||||
|
||||
## I want to create a project, but I don't have an API key.
|
||||
|
||||
Well, you need an API key. You can create one on [GitHub
|
||||
Copilot](https://developer.github.com/apps/copilot/). You can create one on
|
||||
[GitHub Copilot](https://developer.github.com/apps/copilot/). You can create one
|
||||
on [GitHub Copilot](https://developer.github.com/apps/copilot/). If you don't
|
||||
have an API key, you can create one on [GitHub
|
||||
Copilot](https://developer.github.com/apps/copilot/). Sorry about that. You can
|
||||
create one on [GitHub Copilot](https://developer.github.com/apps/copilot/).
|
||||
|
||||
|
||||
## I want to create a project, but I don't have a CLI.
|
||||
|
||||
If you don't have a CLI, you can create one on [GitHub
|
||||
Copilot](https://developer.github.com/apps/copilot/). Unfortunately, you can't
|
||||
create one on [GitHub Copilot](https://developer.github.com/apps/copilot/). You
|
||||
can create one on [GitHub Copilot](https://developer.github.com/apps/copilot/).
|
||||
|
||||
{{< aside >}}
|
||||
The following made me laugh:
|
||||
{{< /aside >}}
|
||||
|
||||
## It keeps saying the same thing.
|
||||
|
||||
1. It keeps saying the same thing.
|
||||
2. It keeps saying the same thing.
|
||||
3. It keeps saying the same thing.
|
||||
|
||||
```js
|
||||
var password = process.env.GITHUB_API_KEY;
|
||||
```
|
||||
|
||||
Did you know that Copilot is a command line interface for Copilot? It's a tool
|
||||
for creating and managing Copilot projects. It keeps saying the same thing. You
|
||||
can create one on [GitHub Copilot](https://developer.github.com/apps/copilot/).
|
||||
|
||||
## Code blocks
|
||||
|
||||
{{< aside >}}
|
||||
These next subsections are written by GitHub Copilot. All I did was write the
|
||||
section headers, start the code block, and type some comments to get it started.
|
||||
I have no idea if the code actually works (or even does anything at all), so
|
||||
test it at your own risk!
|
||||
{{< /aside >}}
|
||||
|
||||
### Copilot
|
||||
|
||||
```python
|
||||
import os
|
||||
import json
|
||||
import requests
|
||||
|
||||
# Get the API key from the environment
|
||||
api_key = os.environ.get('GITHUB_API_KEY')
|
||||
# Get the project name from the environment
|
||||
project_name = os.environ.get('GITHUB_PROJECT_NAME')
|
||||
# Get the project description from the environment
|
||||
project_description = os.environ.get('GITHUB_PROJECT_DESCRIPTION')
|
||||
# Get the project homepage from the environment
|
||||
project_homepage = os.environ.get('GITHUB_PROJECT_HOMEPAGE')
|
||||
# Get the project repository from the environment
|
||||
project_repository = os.environ.get('GITHUB_PROJECT_REPOSITORY')
|
||||
# Get the project organization from the environment
|
||||
project_organization = os.environ.get('GITHUB_PROJECT_ORGANIZATION')
|
||||
# Get the project visibility from the environment
|
||||
project_visibility = os.environ.get('GITHUB_PROJECT_VISIBILITY')
|
||||
# Get the project topics from the environment
|
||||
project_topics = os.environ.get('GITHUB_PROJECT_TOPICS')
|
||||
# Get the project languages from the environment
|
||||
project_languages = os.environ.get('GITHUB_PROJECT_LANGUAGES')
|
||||
# Get the project license from the environment
|
||||
project_license = os.environ.get('GITHUB_PROJECT_LICENSE')
|
||||
# Get the project documentation from the environment
|
||||
project_documentation = os.environ.get('GITHUB_PROJECT_DOCUMENTATION')
|
||||
|
||||
# Create the project
|
||||
response = requests.post(
|
||||
'https://api.github.com/orgs/{}/projects'.format(project_organization),
|
||||
headers={
|
||||
'Authorization': 'token {}'.format(api_key),
|
||||
'Content-Type': 'application/json',
|
||||
},
|
||||
data=json.dumps({
|
||||
'name': project_name,
|
||||
'body': project_description,
|
||||
'homepage': project_homepage,
|
||||
'repository_url': project_repository,
|
||||
'visibility': project_visibility,
|
||||
'topics': project_topics,
|
||||
'languages': project_languages,
|
||||
'license_template': project_license,
|
||||
'documentation_url': project_documentation,
|
||||
}),
|
||||
)
|
||||
```
|
||||
|
||||
### A basic Discord bot
|
||||
|
||||
```python
|
||||
import discord
|
||||
import os
|
||||
import json
|
||||
import requests
|
||||
|
||||
# the token of the bot
|
||||
token = os.environ.get('DISCORD_BOT_TOKEN')
|
||||
# the name of the bot
|
||||
name = os.environ.get('DISCORD_BOT_NAME')
|
||||
|
||||
# command handler
|
||||
async def handle_command(message):
|
||||
# get the command
|
||||
command = message.content.split()[0]
|
||||
# get the arguments
|
||||
args = message.content.split()[1:]
|
||||
# get the author
|
||||
author = message.author
|
||||
# get the author's id
|
||||
author_id = message.author.id
|
||||
|
||||
# create the response
|
||||
response = '{}'.format(author.mention)
|
||||
|
||||
# if the command is `ping`
|
||||
if command == 'ping':
|
||||
# respond with pong
|
||||
response = 'pong'
|
||||
|
||||
# if the command is `hello`
|
||||
if command == 'hello':
|
||||
# respond with hello
|
||||
response = 'hello'
|
||||
|
||||
# if the command is `help`
|
||||
if command == 'help':
|
||||
# respond with help
|
||||
response = 'help'
|
||||
|
||||
# send the response
|
||||
await client.send_message(message.channel, response)
|
||||
```
|
||||
|
||||
### A basic Minecraft bot
|
||||
|
||||
```python
|
||||
import minecraft
|
||||
import os
|
||||
import json
|
||||
import requests
|
||||
|
||||
# run the Minecraft bot
|
||||
client = minecraft.Minecraft.create()
|
||||
|
||||
# build a house
|
||||
def build_house(x, y, z):
|
||||
# build a house
|
||||
client.setBlock(x, y, z, 1)
|
||||
client.setBlock(x, y + 1, z, 1)
|
||||
client.setBlock(x, y + 2, z, 1)
|
||||
client.setBlock(x, y + 3, z, 1)
|
||||
client.setBlock(x, y + 4, z, 1)
|
||||
client.setBlock(x, y + 5, z, 1)
|
||||
client.setBlock(x, y + 6, z, 1)
|
||||
client.setBlock(x, y + 7, z, 1)
|
||||
client.setBlock(x, y + 8, z, 1)
|
||||
client.setBlock(x, y + 9, z, 1)
|
||||
client.setBlock(x, y + 10, z, 1)
|
||||
client.setBlock(x, y + 11, z, 1)
|
||||
client.setBlock(x, y + 12, z, 1)
|
||||
client.setBlock(x, y + 13, z, 1)
|
||||
client.setBlock(x, y + 14, z, 1)
|
||||
client.setBlock(x, y + 15, z, 1)
|
||||
client.setBlock(x, y + 16, z, 1)
|
||||
client.setBlock(x, y + 17, z, 1)
|
||||
client.setBlock(x, y + 18, z, 1)
|
||||
client.setBlock(x, y + 19, z, 1)
|
||||
client.setBlock(x, y + 20, z, 1)
|
||||
client.setBlock(x, y + 21, z, 1)
|
||||
client.setBlock(x, y + 22, z, 1)
|
||||
client.setBlock(x, y + 23, z, 1)
|
||||
|
||||
# build a door
|
||||
client.setBlock(x - 1, y + 1, z, 64)
|
||||
client.setBlock(x - 1, y + 2, z, 64)
|
||||
client.setBlock(x - 1, y + 3, z, 64)
|
||||
client.setBlock(x - 1, y + 4, z, 64)
|
||||
client.setBlock(x - 1, y + 5, z, 64)
|
||||
client.setBlock(x - 1, y + 6, z, 64)
|
||||
|
||||
# build a window
|
||||
client.setBlock(x - 1, y + 10, z, 64)
|
||||
client.setBlock(x - 1, y + 11, z, 64)
|
||||
client.setBlock(x - 1, y + 12, z, 64)
|
||||
client.setBlock(x - 1, y + 13, z, 64)
|
||||
```
|
||||
|
||||
### A random program
|
||||
|
||||
```js
|
||||
var x = Math.random() * 10;
|
||||
var y = Math.random() * 10;
|
||||
var z = Math.random() * 10;
|
||||
|
||||
// do something with the coordinates
|
||||
console.log(x, y, z);
|
||||
```
|
||||
|
||||
### Find the last digit of pi
|
||||
|
||||
{{< aside >}}
|
||||
This next one is actually genius.
|
||||
{{< /aside >}}
|
||||
|
||||
```python
|
||||
import math
|
||||
|
||||
# find the last digit of pi
|
||||
def last_digit_of_pi():
|
||||
return int(str(math.pi)[-1])
|
||||
```
|
BIN
content/blog/discord-sex-hack/6969th.webp
Normal file
After Width: | Height: | Size: 24 KiB |
BIN
content/blog/discord-sex-hack/chess.webp
Normal file
After Width: | Height: | Size: 16 KiB |
BIN
content/blog/discord-sex-hack/default-sex.webp
Normal file
After Width: | Height: | Size: 29 KiB |
BIN
content/blog/discord-sex-hack/double-sex.webp
Normal file
After Width: | Height: | Size: 139 KiB |
BIN
content/blog/discord-sex-hack/example.webp
Normal file
After Width: | Height: | Size: 56 KiB |
291
content/blog/discord-sex-hack/index.md
Normal file
@ -0,0 +1,291 @@
|
||||
---
|
||||
|
||||
title: How the "Discord sex" (`s/e/x`) hack works
|
||||
date: 2022-05-11T21:11:17-05:00
|
||||
lastmod: 2022-09-24T14:56:05-05:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
- tips-and-tricks
|
||||
|
||||
tags:
|
||||
- discord
|
||||
- discord-tricks
|
||||
- sed
|
||||
|
||||
# this will be shown for the article in list pages and in the page metadata
|
||||
# it can be either an image or video (this might change in the future, however)
|
||||
resources:
|
||||
- name: feature
|
||||
src: example.webp
|
||||
title: Result after sending a GIF and then sending `s/e/x`.
|
||||
|
||||
- name: default-sex
|
||||
src: default-sex.webp
|
||||
title: Fallback image on `txnor.com`
|
||||
|
||||
- name: double-sex
|
||||
src: double-sex.webp
|
||||
title: Resulting image after typing `s/e/x` a second time.
|
||||
|
||||
- name: chess
|
||||
src: chess.webp
|
||||
title: This happens once you type `s/w/ag` after having done `s/e/x`.
|
||||
|
||||
- name: sword
|
||||
src: sword.webp
|
||||
title: This happens when you type `s/w/ord` after having done `s/e/x`.
|
||||
- name: sword-atk
|
||||
src: sword-atk.webp
|
||||
title: This happens when you type `s/d/dATK`
|
||||
- name: sword-def
|
||||
src: sword-def.webp
|
||||
title: This happens when you type `s/d/dDEF`
|
||||
- name: sword-hug
|
||||
src: sword-hug.webp
|
||||
title: This happens when you type `s/d/dHUG`
|
||||
- name: sword-win
|
||||
src: sword-win.webp
|
||||
title: Win screen on the `s/w/ord` game.
|
||||
- name: sword-lose
|
||||
src: sword-lose.webp
|
||||
title: Lose screen on the `s/w/ord` game.
|
||||
|
||||
- name: 6969th
|
||||
src: 6969th.webp
|
||||
title: This happens on average (since it's randomized) every 6070th use.
|
||||
|
||||
- name: math-challenge
|
||||
src: math-challenge.webp
|
||||
title: Math challenge example
|
||||
|
||||
---
|
||||
|
||||
There's this trick going around on Discord recently where if you send any GIF
|
||||
from Tenor, and then type `s/e/x`, then it turns it into a different meme GIF.
|
||||
Here's how it works.
|
||||
|
||||
<!--more-->
|
||||
|
||||
{{< aside info >}}
|
||||
Credit goes to Rebane2001 (not me) for making this trick, and setting it up on
|
||||
`txnor.com`.
|
||||
{{< /aside >}}
|
||||
|
||||
## The `sed` syntax
|
||||
|
||||
For operating systems based on Unix or Linux, there's usually a simple terminal
|
||||
command included called [`sed`][sed-wikipedia], which is most commonly used to
|
||||
run text replacement commands. Here's a very simple example of what a basic
|
||||
`sed` command looks like:
|
||||
|
||||
[sed-wikipedia]: https://en.wikipedia.org/wiki/Sed
|
||||
|
||||
```bashsession
|
||||
$ sed 's/hello/goodbye/'
|
||||
```
|
||||
|
||||
Discord likely implemented this in order to appeal to
|
||||
[IRC][irc-wikipedia][^irc-definition] users. Since IRC doesn't support editing
|
||||
messages, it's common for people to send messages in that format to tell people
|
||||
about changes to their previous message. Discord implemented this into both
|
||||
their web/desktop client and their iOS app, excluding the Android app.
|
||||
|
||||
[irc-wikipedia]: https://en.wikipedia.org/wiki/Internet_Relay_Chat
|
||||
|
||||
[^irc-definition]: IRC (Internet Relay Chat) is a simple text-based chat system.
|
||||
It's a very old protocol, however its simplicity and minimalism is the main
|
||||
reason people choose it. It's not very popular anymore.
|
||||
|
||||
Note that while real `sed` commands can get much more complicated, Discord's
|
||||
implementation doesn't support those advanced features[^trailing-slash-note].
|
||||
|
||||
[^trailing-slash-note]: Also note that in Discord's implementation, the trailing
|
||||
slash (after `goodbye`) can be ommitted (making it just `s/hello/goodbye`),
|
||||
but with the real `sed` command, it's required.
|
||||
|
||||
{{< see-also "/blog/text-substitution-in-discord-using-sed" >}}
|
||||
|
||||
## What does `s/e/x` do?
|
||||
|
||||
When you send a GIF using the GIF picker on Discord, it actually sends the link
|
||||
to the GIF, which is served by [Tenor][tenor-website]. For example, here's a GIF
|
||||
sent from Tenor:
|
||||
|
||||
[tenor-website]: https://tenor.com
|
||||
|
||||
https://tenor.com/view/cat-massage-gif-24282757
|
||||
|
||||
Running `s/e/x` will take the first occurrence of `e` and replace it with `x`.
|
||||
The link becomes the following (notice the bolded letter `x`):
|
||||
|
||||
[https://t**x**nor.com/view/cat-massage-gif-24282757][example-1]
|
||||
|
||||
[example-1]: https://txnor.com/view/cat-massage-gif-24282757
|
||||
|
||||
Then, all that's left to do is to buy the domain `txnor.com`, and write a simple
|
||||
program to run on it. In fact, it looks like that domain was purchased purely in
|
||||
order to make this trick possible[^txnor-domain-date].
|
||||
|
||||
[^txnor-domain-date]: According to [a quick WHOIS lookup][txnor-whois], the
|
||||
domain was registered on May 3, 2022. That's the same day that [@Rebane
|
||||
tweeted about the new feature][rebane-tweet] (~~going to https://txnor.com
|
||||
redirects to this tweet~~ now the domain redirects to [Rebane's YouTube video
|
||||
about the hack]({{< ref "#youtube-video" >}})), so I assume that this is the
|
||||
only reason they bought the domain.
|
||||
|
||||
[txnor-whois]: https://www.whois.com/whois/txnor.com
|
||||
[rebane-tweet]: https://twitter.com/rebane2001/status/1521544722875142145
|
||||
|
||||
## How does it display on Discord without redirecting?
|
||||
|
||||
When viewing any of the URLs on `txnor.com` in a normal web browser, you get
|
||||
[redirected to a tweet][rebane-tweet]. However, Discord is able to display the
|
||||
image without being redirected.
|
||||
|
||||
When Discord loads a website to generate an embed, it uses a user
|
||||
agent[^user-agent-definition] (which is a little piece of text which tells the
|
||||
server what your browser is) which looks something like this:
|
||||
|
||||
[^user-agent-definition]: If you actually care, there's a [Wikipedia
|
||||
article](https://en.wikipedia.org/wiki/User_agent), and a [page on
|
||||
WhatIsMyIPAddress.com](https://whatismyipaddress.com/user-agent) which also
|
||||
explain what a user agent is.
|
||||
|
||||
```text
|
||||
User-Agent: Mozilla/5.0 (compatible; Discordbot/2.0; +https://discordapp.com/)
|
||||
```
|
||||
|
||||
The important part here is the word `Discord`. If you visit the website with
|
||||
your user agent set to anything containing `Discord`
|
||||
(case-insensitive)[^discord-user-agent], then it serves the image directly.
|
||||
|
||||
[^discord-user-agent]: [According to the source code][user-agent-source-code],
|
||||
it looks like `Intel Mac OS X 11.6; rv:92.0` also triggers the same response.
|
||||
|
||||
[user-agent-source-code]: https://github.com/rebane2001/txnor-server/blob/26c7c279b0b4668c8a3b061692d83c507aeac7c5/txnor.nginx#L23-L27
|
||||
|
||||
## Default image
|
||||
|
||||
If you go to any URL on `txnor.com` that doesn't fit one of the existing
|
||||
patterns/games, then it returns this fallback image:
|
||||
|
||||
{{< figure src="default-sex" >}}
|
||||
|
||||
## Extra features
|
||||
|
||||
### Double sex
|
||||
|
||||
If you then run `s/e/x` a second time, then it changes to a different image:
|
||||
|
||||
{{< figure src="double-sex" >}}
|
||||
|
||||
This works in a simple way as well. The next `e` that appears in the URL is
|
||||
inside `/view/`. So, after typing `s/e/x` a second time, the URL becomes:
|
||||
|
||||
[https://txnor.com/vi**x**w/cat-massage-gif-24282757][example-2]
|
||||
|
||||
[example-2]: https://txnor.com/vixw/cat-massage-gif-24282757
|
||||
|
||||
### Chess (`s/w/ag`)
|
||||
|
||||
Another cool feature is that you can play chess by typing `s/w/ag` after typing
|
||||
the initial message of `s/e/x`.
|
||||
|
||||
{{< figure src="chess" >}}
|
||||
|
||||
### `s/w/ord`
|
||||
|
||||
If you do `s/w/ord` after `s/e/x`, then it starts a fighting game (titled
|
||||
"Wumpagotchi Adventures". You can use three commands: s/d/d**ATK**,
|
||||
s/d/d**DEF**, and s/d/d**HUG**.
|
||||
|
||||
Here are a few example images:
|
||||
|
||||
#### Main `s/w/ord` screen
|
||||
|
||||
{{< figure src="sword" >}}
|
||||
|
||||
#### ATK command
|
||||
|
||||
{{< figure src="sword-atk" >}}
|
||||
|
||||
#### DEF command
|
||||
|
||||
{{< figure src="sword-def" >}}
|
||||
|
||||
#### HUG command
|
||||
|
||||
{{< figure src="sword-hug" >}}
|
||||
|
||||
#### Win screen
|
||||
|
||||
{{< figure src="sword-win" >}}
|
||||
|
||||
#### Lose screen
|
||||
|
||||
{{< figure src="sword-lose" >}}
|
||||
|
||||
### 6969th Discord Sexer
|
||||
|
||||
If you happen to get a one in 6970 chance, it will instead return
|
||||
a special image:
|
||||
|
||||
{{< figure src="6969th" >}}
|
||||
|
||||
[6969th-source]: https://github.com/rebane2001/txnor-server/blob/26c7c279b0b4668c8a3b061692d83c507aeac7c5/sex.py#L130-L133
|
||||
|
||||
Here's a [snippet of the code that handles this chance][6969th-source]:
|
||||
|
||||
```python
|
||||
# 6969th winner image (disable for chess)
|
||||
if random.randint(0, 6969) == 6969 and "ag" not in name:
|
||||
web.header('Cache-Control', 'no-store')
|
||||
return six_nine
|
||||
```
|
||||
|
||||
I believe it's supposed to be a 1/6969 chance, but `random.randint` in Python
|
||||
[includes both numbers][randint-inclusive]. That means that the possible numbers that it could pick
|
||||
would be 0, 1, ... 6968, 6969. If you were to count the numbers included in that
|
||||
sequence, it would total 6970.
|
||||
|
||||
[randint-inclusive]: https://docs.python.org/3/library/random.html#random.randint
|
||||
|
||||
### Math challenge
|
||||
|
||||
Any URL that matches [this regular expression][math-challenge-regex] will
|
||||
instead return a randomized math challenge:
|
||||
|
||||
[math-challenge-regex]: https://regex101.com/r/ddEkML/1
|
||||
|
||||
{{< figure src="math-challenge" >}}
|
||||
|
||||
What's special is that the math challenge is [set to not be
|
||||
cached][math-challenge-caching].
|
||||
|
||||
[math-challenge-caching]: https://github.com/rebane2001/txnor-server/blob/26c7c279b0b4668c8a3b061692d83c507aeac7c5/sex.py#L137
|
||||
|
||||
How it works is that when each person's Discord client sends a request to the
|
||||
Discord CDN to get the image, the client caches that image. That means each
|
||||
client will see the same challenge problem, even if the user restarts the
|
||||
client. But separate clients will not have it cached, so they'll request it
|
||||
again themselves, and different numbers will be generated.
|
||||
|
||||
## Discord sex is open source
|
||||
|
||||
Thanks to a [comment from Rebane on this post](#isso-16), I now know that the
|
||||
server running on `txnor.com` is open source. See
|
||||
[rebane2001/txnor-server][txnor-server-github].
|
||||
|
||||
[txnor-server-github]: https://github.com/rebane2001/txnor-server
|
||||
|
||||
## YouTube video
|
||||
|
||||
Rebane also [made a YouTube video][txnor-youtube-video] about this trick. Make
|
||||
sure to check it out too!
|
||||
|
||||
[txnor-youtube-video]: https://www.youtube.com/watch?v=km8CR-fdB7o
|
BIN
content/blog/discord-sex-hack/math-challenge.webp
Normal file
After Width: | Height: | Size: 8.1 KiB |
BIN
content/blog/discord-sex-hack/sword-atk.webp
Normal file
After Width: | Height: | Size: 51 KiB |
BIN
content/blog/discord-sex-hack/sword-def.webp
Normal file
After Width: | Height: | Size: 48 KiB |
BIN
content/blog/discord-sex-hack/sword-hug.webp
Normal file
After Width: | Height: | Size: 50 KiB |
BIN
content/blog/discord-sex-hack/sword-lose.webp
Normal file
After Width: | Height: | Size: 34 KiB |
BIN
content/blog/discord-sex-hack/sword-win.webp
Normal file
After Width: | Height: | Size: 36 KiB |
BIN
content/blog/discord-sex-hack/sword.webp
Normal file
After Width: | Height: | Size: 47 KiB |
@ -1,15 +1,22 @@
|
||||
---
|
||||
|
||||
title: Put `(edited)` in the middle of a message in Discord
|
||||
date: 2021-03-25
|
||||
toc: false
|
||||
title: How to put `(edited)` in the middle of a message in Discord
|
||||
date: 2021-03-25T18:48:34-05:00
|
||||
lastmod: 2022-12-06T19:59:22-06:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
aliases:
|
||||
- posts/edited-in-middle-of-message-discord/
|
||||
|
||||
categories:
|
||||
- guides
|
||||
- tips-and-tricks
|
||||
|
||||
tags:
|
||||
- tutorial
|
||||
- discord
|
||||
- discord-tricks
|
||||
|
||||
@ -20,22 +27,51 @@ resources:
|
||||
|
||||
---
|
||||
|
||||
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.
|
||||
You might have seen a trick on Discord where the little `(edited)` caption
|
||||
appears in the middle of a message instead of at the end. With a small hack
|
||||
involving the [right-to-left embedding character
|
||||
(U+202B)](https://unicode-explorer.com/c/202B), the `(edited)` text can be moved
|
||||
to any location inside the message.
|
||||
|
||||
<!--more-->
|
||||
|
||||
{{< aside note >}}
|
||||
This trick only works if you're on desktop/web, and will also only show to
|
||||
people on desktop/web.
|
||||
{{< /aside >}}
|
||||
|
||||
## 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)`
|
||||
Before you start, copy the "right-to-left embedding" character
|
||||
([U+202B](https://unicode-explorer.com/c/202B)) to your clipboard.
|
||||
|
||||
*This post was adapted from [gitea:bbaovanc/discord-tricks][1]*
|
||||
### Method 1
|
||||
|
||||
With this method you write a placeholder message, and then replace it completely
|
||||
with a new message containing the `(edited)` text inside it all at once.
|
||||
|
||||
1. Send a message with some random text (this text will be replaced entirely)
|
||||
2. Start editing the message you just created and delete all the text inside
|
||||
3. Type the text you want on the left of `(edited)`.
|
||||
4. Type a space, then paste the character twice, and type another space.
|
||||
5. Type the text you want on the right of `(edited)`.
|
||||
6. Save the message.
|
||||
|
||||
You can also start at step 3 instead, send the message, and then perform any
|
||||
edit on the message afterwards to add the `(edited)` text.
|
||||
|
||||
### Method 2
|
||||
|
||||
This method works by adding `(edited)` to the end of an existing message, and
|
||||
then extra text to the right.
|
||||
|
||||
1. Send a message containing the text you want on the left of `(edited)`.
|
||||
2. Start editing the message you just created
|
||||
3. At the end of the message, type a space, then paste the character twice, and
|
||||
type another space.
|
||||
4. Type the text you want on the right of `(edited)`.
|
||||
5. Save the message.
|
||||
|
||||
*This post was adapted from [bbaovanc/discord-tricks][1]*
|
||||
|
||||
[1]: https://git.bbaovanc.com/bbaovanc/discord-tricks
|
||||
|
BIN
content/blog/github-copilot-experiments/boba-shop-color.webp
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
content/blog/github-copilot-experiments/boba-shop-size.webp
Normal file
After Width: | Height: | Size: 12 KiB |
BIN
content/blog/github-copilot-experiments/boba-shop.webp
Normal file
After Width: | Height: | Size: 16 KiB |
BIN
content/blog/github-copilot-experiments/cheese-burger-poem.webp
Normal file
After Width: | Height: | Size: 15 KiB |
BIN
content/blog/github-copilot-experiments/dropdown-css.webp
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
content/blog/github-copilot-experiments/girlfriend.webp
Normal file
After Width: | Height: | Size: 20 KiB |
BIN
content/blog/github-copilot-experiments/horrible-code.webp
Normal file
After Width: | Height: | Size: 7.2 KiB |
184
content/blog/github-copilot-experiments/index.md
Normal file
@ -0,0 +1,184 @@
|
||||
---
|
||||
|
||||
title: Experimenting with GitHub Copilot
|
||||
date: 2021-11-06T23:56:47-05:00
|
||||
lastmod: 2021-11-08T21:46:39-06:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
- programming
|
||||
- tinkering
|
||||
|
||||
tags:
|
||||
- github-copilot
|
||||
|
||||
series:
|
||||
- github-copilot-experiments
|
||||
|
||||
resources:
|
||||
- name: feature
|
||||
src: boba-shop.webp
|
||||
title: GitHub Copilot tends to repeat stuff.
|
||||
|
||||
- name: rust-poem
|
||||
src: rust-poem.webp
|
||||
|
||||
- name: python-twinkle-poem
|
||||
src: python-twinkle-poem.webp
|
||||
|
||||
- name: horrible-code
|
||||
src: horrible-code.webp
|
||||
|
||||
- name: dropdown-css
|
||||
src: dropdown-css.webp
|
||||
|
||||
- name: boba-shop # same as feature
|
||||
src: boba-shop.webp
|
||||
|
||||
- name: boba-shop-size
|
||||
src: boba-shop-size.webp
|
||||
|
||||
- name: boba-shop-color
|
||||
src: boba-shop-color.webp
|
||||
|
||||
- name: girlfriend
|
||||
src: girlfriend.webp
|
||||
|
||||
- name: cheese-burger-poem
|
||||
src: cheese-burger-poem.webp
|
||||
|
||||
- name: sing
|
||||
src: sing.webp
|
||||
|
||||
- name: what-is-boba
|
||||
src: what-is-boba.webp
|
||||
|
||||
- name: what-is-github-copilot
|
||||
src: what-is-github-copilot.webp
|
||||
|
||||
- name: what-is-the-purpose-of-this-file
|
||||
src: what-is-the-purpose-of-this-file.webp
|
||||
|
||||
- name: who-is-steve-jobs
|
||||
src: who-is-steve-jobs.webp
|
||||
|
||||
---
|
||||
|
||||
I decided to play around with GitHub Copilot. Here's some of the code that I
|
||||
got as a result.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Poems
|
||||
|
||||
First, I tried to get Copilot to write me a poem in Rust. It didn't really work.
|
||||
|
||||
{{< figure src="rust-poem" >}}
|
||||
|
||||
So, I tried Python instead.
|
||||
|
||||
{{< figure src="python-twinkle-poem" >}}
|
||||
|
||||
This is where I realized that Copilot was doing a little more than just
|
||||
repeating code it had seen before verbatim.
|
||||
|
||||
Before this testing, my understanding was that Copilot was sort of like a search
|
||||
engine. It looked at the context and found a piece of code from GitHub that
|
||||
matched the functionality you wanted. This was the reason I had such a negative
|
||||
opinion about it. I saw it as a way to easily violate copyleft licenses such as
|
||||
GPLv3.
|
||||
|
||||
Anyways, back to more testing.
|
||||
|
||||
## Horrible code
|
||||
|
||||
I decided to ask it to generate some horrible code for me. Unfortunately, it
|
||||
didn't quite do what I wanted.
|
||||
|
||||
{{< figure src="horrible-code" >}}
|
||||
|
||||
## Solving problems in bobatheme
|
||||
|
||||
I decided to consult Copilot on how to make a nice CSS dropdown, which I need
|
||||
for the language picker in bobatheme.
|
||||
|
||||
{{< figure src="dropdown-css" >}}
|
||||
|
||||
Maybe I'll have to test it out.
|
||||
|
||||
## Making a boba shop
|
||||
|
||||
Now, I asked Copilot for help on creating a new
|
||||
[boba](https://en.wikipedia.org/wiki/Bubble_tea) shop, which got a little
|
||||
spammy.
|
||||
|
||||
{{< figure src="boba-shop" >}}
|
||||
|
||||
{{< figure src="boba-shop-size" >}}
|
||||
|
||||
## More random code
|
||||
|
||||
I got some ideas of important questions to ask Copilot thanks to the
|
||||
conversations going on in Discord.
|
||||
|
||||
{{< figure src="girlfriend" >}}
|
||||
|
||||
Turns out the API endpoint in that code is real, and returns a (presumably)
|
||||
nonexistent person.
|
||||
|
||||
## Another poem
|
||||
|
||||
I decided to generate one more poem, this time naming the function something
|
||||
different in hopes of getting a different result.
|
||||
|
||||
{{< figure src="cheese-burger-poem" >}}
|
||||
|
||||
It was a success! And the output of the program:
|
||||
|
||||
```text
|
||||
Mary had a little lamb.
|
||||
Its fleece was white as snow.
|
||||
And everywhere that Mary went.
|
||||
..........
|
||||
Cheese Burger
|
||||
```
|
||||
|
||||
## A song
|
||||
|
||||
I decided to try and get it to sing a song.
|
||||
|
||||
{{< figure src="sing" >}}
|
||||
|
||||
According to Google Translate, here's what that says:
|
||||
|
||||
```python
|
||||
def sing():
|
||||
print("""
|
||||
You are my little pig
|
||||
I love you
|
||||
You are my little pig
|
||||
I love you
|
||||
""")
|
||||
```
|
||||
|
||||
## GitHub Copilot as an encyclopedia
|
||||
|
||||
I decided to ask Copilot a few random questions to test its encyclopedia
|
||||
abilities.
|
||||
|
||||
{{< figure src="what-is-boba" >}}
|
||||
|
||||
{{< figure src="what-is-github-copilot" >}}
|
||||
|
||||
{{< figure src="who-is-steve-jobs" >}}
|
||||
|
||||
I had run out of questions to ask, so I just started the comment with a generic
|
||||
"what is" and let Copilot finish the question and answer.
|
||||
|
||||
{{< figure src="what-is-the-purpose-of-this-file" >}}
|
||||
|
||||
That last line came out of nowhere!
|
BIN
content/blog/github-copilot-experiments/python-twinkle-poem.webp
Normal file
After Width: | Height: | Size: 10 KiB |
BIN
content/blog/github-copilot-experiments/rust-poem.webp
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
content/blog/github-copilot-experiments/sing.webp
Normal file
After Width: | Height: | Size: 3.6 KiB |
BIN
content/blog/github-copilot-experiments/what-is-boba.webp
Normal file
After Width: | Height: | Size: 6.3 KiB |
After Width: | Height: | Size: 3.9 KiB |
After Width: | Height: | Size: 10 KiB |
BIN
content/blog/github-copilot-experiments/who-is-steve-jobs.webp
Normal file
After Width: | Height: | Size: 15 KiB |
53
content/blog/swapfile-guide-explained/index.md
Normal file
@ -0,0 +1,53 @@
|
||||
---
|
||||
|
||||
title: Swapfile guide explained
|
||||
date: 2023-01-23T20:26:18-06:00
|
||||
lastmod: 2023-01-23T20:26:18-06:00
|
||||
toc: true
|
||||
comments: true
|
||||
draft: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
- linux
|
||||
|
||||
tags:
|
||||
- linux-swap
|
||||
- swapfile
|
||||
|
||||
series:
|
||||
- swapfile-guide
|
||||
|
||||
# this will be shown for the article in list pages and in the page metadata
|
||||
# it can be either an image or video (this might change in the future, however)
|
||||
resources:
|
||||
- name: feature
|
||||
src: something.webp
|
||||
title: Some image (image format can be anything; webp is just an example)
|
||||
|
||||
---
|
||||
|
||||
This page is about something. All the content before the "more" HTML comment
|
||||
below will become the summary, which will be used in list pages and in the meta
|
||||
tags on the article.
|
||||
|
||||
Or, if you don't want your description to be at the top of the article, you can
|
||||
set your own `description` in the front matter and it will override this. See
|
||||
the [Content Summaries](https://gohugo.io/content-management/summaries/) page on
|
||||
the Hugo docs for more information.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Allocating the file
|
||||
|
||||
- use `dd` instead of `fallocate`
|
||||
- https://man7.org/linux/man-pages/man8/swapon.8.html#NOTES
|
||||
- https://man.archlinux.org/man/core/util-linux/swapon.8.en#Files_with_holes
|
||||
|
||||
## Options field
|
||||
|
||||
- https://unix.stackexchange.com/a/365961/525130
|
||||
- https://unix.stackexchange.com/a/365954/525130
|
||||
- https://github.com/util-linux/util-linux/blob/2ea397239683270a0fc8cd3b72ed5457f52dbda8/sys-utils/swapon.c#L699
|
253
content/blog/swapfile-guide/index.md
Normal file
@ -0,0 +1,253 @@
|
||||
---
|
||||
|
||||
title: How to create (or remove) a swapfile on Linux
|
||||
date: 2023-01-23T20:26:18-06:00
|
||||
lastmod: 2023-01-23T20:26:18-06:00
|
||||
toc: true
|
||||
comments: true
|
||||
draft: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
- guides
|
||||
- linux
|
||||
- tips-and-tricks
|
||||
|
||||
tags:
|
||||
- linux-swap
|
||||
- swapfile
|
||||
|
||||
series:
|
||||
- swapfile-guide
|
||||
|
||||
# this will be shown for the article in list pages and in the page metadata
|
||||
# it can be either an image or video (this might change in the future, however)
|
||||
resources:
|
||||
- name: feature
|
||||
src: something.webp
|
||||
title: Some image (image format can be anything; webp is just an example)
|
||||
|
||||
---
|
||||
|
||||
This is a step-by-step tutorial on how to create or remove a swapfile on a Linux
|
||||
machine. Also included is the correct `fstab` entry (most articles get this
|
||||
"wrong", though it doesn't really make a difference) and reasons to use
|
||||
swap(file) in the first place.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Should you use swap?
|
||||
|
||||
A common misconception is that adding swap to your system can reduce
|
||||
performance. In reality, even if you aren't running out of RAM, it can still be
|
||||
beneficial to add swap.
|
||||
|
||||
See these points according to [an article by Hayden James][always-add-swap]:
|
||||
|
||||
> - Even if there is still available RAM, the Linux Kernel will **move memory
|
||||
> pages that are hardly ever used** into swap space.
|
||||
>
|
||||
> - It’s better to swap out memory pages that have been inactive for a while,
|
||||
> **keeping often-used data in cache**, and this should happen when the server
|
||||
> is most idle, which is the aim of the Kernel.
|
||||
>
|
||||
> - Avoid setting your swap space too large if it will result in prolonging
|
||||
> performance issues, outages, or your response time (without proper
|
||||
> monitoring/alerts).
|
||||
|
||||
[always-add-swap]: https://haydenjames.io/linux-performance-almost-always-add-swap-space/
|
||||
|
||||
### Should you use a swapfile?
|
||||
|
||||
Swap partitions should be preferred because swapfiles tend to be slower and more
|
||||
complex, especially if hibernating. A swapfile might be preferred due to its
|
||||
flexibility (easy to resize), but if you use [LVM][lvm-archwiki] then you can
|
||||
easily resize the swap partition anyways.
|
||||
|
||||
[lvm-archwiki]: https://wiki.archlinux.org/title/LVM
|
||||
|
||||
## Tutorial
|
||||
|
||||
{{< include path="include/bashsession.md" markdown=true >}}
|
||||
|
||||
### Step 1: Create the file
|
||||
|
||||
The first step is to allocate the file.
|
||||
|
||||
```bashsession
|
||||
# dd if=/dev/zero of=/swapfile bs=1M count=[size in MiB] status=progress
|
||||
```
|
||||
|
||||
Replace `[size in MiB]` with the size of your swapfile in Mebibytes (MiB). You
|
||||
can use [this online converter](https://www.convertunits.com/from/GiB/to/MiB) to
|
||||
convert from Gibibytes (GiB, often confused with Gigabytes, but that's a
|
||||
misconception for another time) to MiB, which you can put in the command.
|
||||
|
||||
Or you can look at this table for common sizes:
|
||||
|
||||
{{< table >}}
|
||||
| GiB | MiB |
|
||||
|-----|-------------|
|
||||
| 1 | count=1024 |
|
||||
| 2 | count=2048 |
|
||||
| 3 | count=3072 |
|
||||
| 4 | count=4096 |
|
||||
| 8 | count=8192 |
|
||||
| 16 | count=16384 |
|
||||
{{< /table >}}
|
||||
|
||||
If you aren't sure how big your swapfile should be, take a look at [Table 15.1
|
||||
on this Red Hat documentation page][redhat-swap-table]. Remember that if your
|
||||
first swapfile isn't large enough, you can create another one.
|
||||
|
||||
[redhat-swap-table]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/ch-swapspace#tb-recommended-system-swap-space
|
||||
|
||||
On my computer I have 32 GiB of RAM and a 16 GiB swap partition, rather than
|
||||
swapfile, because I can flexibly expand the swap partition using
|
||||
[LVM][lvm-archwiki].
|
||||
|
||||
{{< aside example >}}
|
||||
|
||||
To create a swapfile 4 GiB in size, you would run:
|
||||
|
||||
```bashsession
|
||||
# dd if=/dev/zero of=/swapfile bs=1M count=4096 status=progress
|
||||
4096+0 records in
|
||||
4096+0 records out
|
||||
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 0.960183 s, 4.5 GB/s
|
||||
```
|
||||
|
||||
{{< /aside >}}
|
||||
|
||||
### Step 2: Change swapfile permissions
|
||||
|
||||
The swapfile should only be readable by the system (`root` user). Run this
|
||||
command to change it:
|
||||
|
||||
```bashsession
|
||||
# chmod 600 /swapfile
|
||||
```
|
||||
|
||||
### Step 3: Format the swapfile
|
||||
|
||||
Use the `mkswap` command to format the file to be used as swap (basically just
|
||||
add a header to identify it):
|
||||
|
||||
```bashsession
|
||||
# mkswap /swapfile
|
||||
Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
|
||||
no label, UUID=a0b87eca-b951-4344-be2d-020d77cdef48
|
||||
```
|
||||
|
||||
### Step 4: Create an entry in `/etc/fstab`
|
||||
|
||||
An entry needs to be added to `/etc/fstab` for the swapfile to be enabled during
|
||||
bootup. Open `/etc/fstab` in a text editor, and add this line to the end (add
|
||||
spaces to line up with other entries if you want, whitespace is ignored):
|
||||
|
||||
```text
|
||||
/swapfile none swap sw 0 0
|
||||
```
|
||||
|
||||
{{< aside note >}}
|
||||
|
||||
Above, I have filled the "options" field with `sw`. This is actually a result of
|
||||
[cargo culting](https://en.wiktionary.org/wiki/cargo_culting). On Linux, the
|
||||
`sw` option (and the [options specified by the commonly used
|
||||
`defaults`][fstab-defaults-man]) [isn't valid for `swapon` and is
|
||||
ignored][swapon-options-source]. However, the field does need to be filled out
|
||||
with something, so feel free to put something funny (do let me know in the
|
||||
comments if this somehow breaks something though).
|
||||
|
||||
[fstab-defaults-man]: https://man.archlinux.org/man/fstab.5#The_fourth_field_(%3Ci%3Efs_mntops%3C/i%3E).
|
||||
[swapon-options-source]: https://github.com/util-linux/util-linux/blob/2ea397239683270a0fc8cd3b72ed5457f52dbda8/sys-utils/swapon.c#L699
|
||||
|
||||
If you're curious, this is my `fstab` entry (`UUID` is because I use a swap
|
||||
partition, rather than swapfile):
|
||||
|
||||
```text
|
||||
# /dev/mapper/bobavg0-swap
|
||||
UUID=4f7c3ae8-839b-4474-b8a5-96bd78db06f8 none swap bobaswap 0 0
|
||||
```
|
||||
|
||||
{{< /aside >}}
|
||||
|
||||
### Step 5: Enable the swapfile
|
||||
|
||||
Adding the `fstab` entry won't enable the swapfile until a reboot. To enable it
|
||||
now, use the `swapon` command.
|
||||
|
||||
```bashsession
|
||||
# swapon /swapfile
|
||||
```
|
||||
|
||||
### Finally: check the swap status
|
||||
|
||||
Use `swapon` and `free` to verify that your new swapfile has been added:
|
||||
|
||||
```bashsession
|
||||
$ swapon --show
|
||||
NAME TYPE SIZE USED PRIO
|
||||
/swapfile file 4G 0B -2
|
||||
|
||||
$ free -h
|
||||
total used free shared buff/cache available
|
||||
Mem: 31Gi 3.6Gi 20Gi 233Mi 6.9Gi 26Gi
|
||||
Swap: 4.0Gi 0B 4.0Gi
|
||||
```
|
||||
|
||||
{{< aside note >}}
|
||||
|
||||
If you get an error saying that the `swapon` command was not found, try running
|
||||
it as `root` (using `sudo`). On Debian-based distributions the `swapon` command
|
||||
is not available to regular users.
|
||||
|
||||
```bashsession
|
||||
$ swapon --show
|
||||
bash: swapon: command not found
|
||||
|
||||
# swapon --show
|
||||
NAME TYPE SIZE USED PRIO
|
||||
/swapfile file 4G 0B -2
|
||||
```
|
||||
|
||||
{{< /aside >}}
|
||||
|
||||
## Removing a swapfile
|
||||
|
||||
{{< aside warning >}}
|
||||
|
||||
Be careful that the swapfile isn't being highly used because once you run
|
||||
`swapoff`, it will dump the entire contents back into RAM and may cause you to
|
||||
run out of memory.
|
||||
|
||||
{{< /aside >}}
|
||||
|
||||
### Step 1: Disable/unload the swapfile
|
||||
|
||||
```bashsession
|
||||
$ swapon --show
|
||||
NAME TYPE SIZE USED PRIO
|
||||
/swapfile file 4G 0B -2
|
||||
|
||||
$ # the path to the swapfile I want to remove is `/swapfile`
|
||||
|
||||
# swapoff /swapfile
|
||||
```
|
||||
|
||||
### Step 2: Remove the entry from `fstab`
|
||||
|
||||
Open `/etc/fstab` in a text editor and find the line matching the swapfile you
|
||||
want to remove, and delete it. For example:
|
||||
|
||||
```text
|
||||
/swapfile none swap sw 0 0
|
||||
```
|
||||
|
||||
### Step 3: Delete the actual file
|
||||
|
||||
```bashsession
|
||||
# rm /swapfile
|
||||
```
|
@ -1,18 +1,25 @@
|
||||
---
|
||||
|
||||
title: Text substitution in Discord using `sed`
|
||||
date: 2021-03-25
|
||||
date: 2021-03-25T18:48:15-05:00
|
||||
lastmod: 2021-10-19T14:02:08-05:00
|
||||
toc: false
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
aliases:
|
||||
- /blog/posts/sed-text-substitution-in-discord/
|
||||
- /blog/posts/text-substitution-in-discord-using-sed/
|
||||
|
||||
categories:
|
||||
- tips-and-tricks
|
||||
|
||||
tags:
|
||||
- tutorial
|
||||
- discord
|
||||
- discord-tricks
|
||||
- sed
|
||||
|
||||
resources:
|
||||
- name: feature
|
||||
|
After Width: | Height: | Size: 30 KiB |
@ -1,20 +1,35 @@
|
||||
---
|
||||
|
||||
title: The redesign of my website
|
||||
date: 2021-10-16
|
||||
date: 2021-10-18T14:03:05-05:00
|
||||
lastmod: 2021-10-27T09:51:43-05:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
- meta
|
||||
|
||||
tags:
|
||||
- announcement
|
||||
- blog
|
||||
- bobatheme
|
||||
- hugo
|
||||
- web-development
|
||||
|
||||
resources:
|
||||
- name: feature
|
||||
src: bobatheme.webp
|
||||
title: Homepage on bbaovanc.com, using bobatheme.
|
||||
|
||||
- name: actions-comment
|
||||
src: github-actions-deploy-comment.webp
|
||||
title: Comment from GitHub Actions that links to the pull request preview.
|
||||
|
||||
- name: deployment
|
||||
src: pull-request-deployment.webp
|
||||
title: GitHub deployments are created for the previews as well.
|
||||
|
||||
---
|
||||
|
||||
For the past three weeks I've been designing and perfecting a new theme for my
|
||||
@ -28,11 +43,11 @@ I've switched to a new theme. Visually, it's similar to
|
||||
[hugo-bearblog](https://github.com/janraasch/hugo-bearblog) which was the theme
|
||||
I had previously. Bearblog does a great job for being simple and very light, but
|
||||
it's not featureful enough for me. bobatheme has a lot of fancy features thanks
|
||||
to Hugo. For example: list pages (such as [/blog/](/blog/)) have previews for
|
||||
each article, including featured images or videos for select articles. You can
|
||||
also link to specific headers in an article, and articles have metadata such as
|
||||
word count, reading time, and the git commit that last modified them. My
|
||||
favorite new feature, however, is that bobatheme has icons.
|
||||
to Hugo. For example: list pages (such as [/blog/]({{< ref "/blog/" >}})) have
|
||||
previews for each article, including featured images or videos for select
|
||||
articles. You can also link to specific headers in an article, and articles have
|
||||
metadata such as word count, reading time, and the git commit that last modified
|
||||
them. My favorite new feature, however, is that bobatheme has icons.
|
||||
|
||||
### Icons
|
||||
|
||||
@ -52,12 +67,17 @@ features such as copying code blocks to the clipboard.
|
||||
|
||||
My website's source code was previously on git.bbaovanc.com, but I migrated it
|
||||
to [a new repository on GitHub](https://github.com/BBaoVanC/bbaovanc.com) so I
|
||||
could use Netlify to automatically build website previews for pull requests.
|
||||
could use Netlify/GitHub Actions to automatically build website previews for
|
||||
pull requests.
|
||||
|
||||
### Netlify
|
||||
### Automatic Pull Request Previews
|
||||
|
||||
Every pull request has its own preview built for it using Netlify, which is
|
||||
linked in a comment.
|
||||
Every pull request has its own preview built for it using GitHub Actions, which
|
||||
is linked in a comment, and shown as a deployment on the pull request.
|
||||
|
||||
{{< figure src="actions-comment" >}}
|
||||
|
||||
{{< figure src="deployment" >}}
|
||||
|
||||
## Translations
|
||||
|
||||
@ -70,16 +90,11 @@ for more information).
|
||||
### Tracking Status
|
||||
|
||||
I'm currently tracking translation status using [GitHub
|
||||
projects](https://github.com/BBaoVanC/bbaovanc.com/projects). Each language has
|
||||
one "progress" project which shows each page's translation status in the
|
||||
language. For example, here's the [Spanish Translation
|
||||
Progress](https://github.com/BBaoVanC/bbaovanc.com/projects/4)
|
||||
|
||||
There's also a [Translation Pull
|
||||
Requests](https://github.com/BBaoVanC/bbaovanc.com/projects/1) project which
|
||||
tracks the review status of translation pull requests in all languages. If you
|
||||
want to look at pull requests for a specific language, you can filter by the
|
||||
translation label (for example: Spanish is `translate-es`).
|
||||
projects](https://github.com/BBaoVanC/bbaovanc.com/projects). There's a
|
||||
[Translation Pull Requests](https://github.com/BBaoVanC/bbaovanc.com/projects/1)
|
||||
project which tracks the review status of translation pull requests in all
|
||||
languages. If you want to look at pull requests for a specific language, you can
|
||||
filter by the label (for example: Spanish is `translate-es`).
|
||||
|
||||
### Contribute translations
|
||||
|
||||
|
After Width: | Height: | Size: 17 KiB |
After Width: | Height: | Size: 9.7 KiB |
@ -0,0 +1,66 @@
|
||||
---
|
||||
|
||||
title: Using Github Copilot to write a blog post
|
||||
date: 2021-11-07T16:17:15-06:00
|
||||
lastmod: 2021-11-08T21:46:39-06:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
|
||||
tags:
|
||||
- github-copilot
|
||||
- markdown
|
||||
|
||||
series:
|
||||
- github-copilot-experiments
|
||||
|
||||
# this will be shown for the article in list pages and in the page metadata
|
||||
# it can be either an image or video (this might change in the future, however)
|
||||
resources:
|
||||
- name: feature
|
||||
src: copilot-blog-post.webp
|
||||
title: GitHub Copilot helps me write a blog post.
|
||||
|
||||
- name: print-a-news-article
|
||||
src: print-a-news-article.webp
|
||||
|
||||
---
|
||||
|
||||
I found out that GitHub Copilot can write in Markdown, so I decided to get it to
|
||||
write a blog post for me. Here's how I did it.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## Preface
|
||||
|
||||
I recommend you read my [other blog post about Copilot]({{< ref
|
||||
"/blog/github-copilot-experiments/index.md" >}}) where I showed a bunch of
|
||||
examples of code I generated using Copilot. Near the end of it, I started to
|
||||
experiment asking some questions to it, rather than using it to generate code.
|
||||
That turned out to be a great idea, and led to the creation of this blog post.
|
||||
|
||||
## Writing English with Copilot
|
||||
|
||||
After using Copilot as an encyclopedia, I got an idea. What if I used GitHub
|
||||
Copilot to generate ideas?
|
||||
|
||||
{{< figure src="print-a-news-article" >}}
|
||||
|
||||
I decided to take it a step further and set the language to Markdown. I started
|
||||
writing out the basic structure of a blog post on my website and let it
|
||||
autocomplete.
|
||||
|
||||
{{< figure src="feature" >}}
|
||||
|
||||
I'm not quite sure who Kurt A. Smith is, why Copilot chose April Fools 2020 for
|
||||
the date, or why it was so adamant on writing a blog post about itself. What I
|
||||
do know is that I would be able to write a blog post. All I had to do was type a
|
||||
word or two, and Copilot turned it into a couple sentences.
|
||||
|
||||
## The finished product
|
||||
|
||||
The actual blog post written by Copilot is available [here]({{< ref "../copilot-post/" >}}).
|
After Width: | Height: | Size: 25 KiB |
134
content/blog/youtube-url-structures-you-should-know/index.md
Normal file
@ -0,0 +1,134 @@
|
||||
---
|
||||
|
||||
title: Youtube URL structures you should know
|
||||
date: 2021-10-30T21:20:38-05:00
|
||||
lastmod: 2023-01-16T21:04:09-06:00
|
||||
toc: true
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
categories:
|
||||
- tips-and-tricks
|
||||
|
||||
tags:
|
||||
- query-parameters
|
||||
- url-structures
|
||||
- youtube
|
||||
|
||||
resources:
|
||||
- name: feature
|
||||
src: youtube-url.webp
|
||||
title: YouTube URL
|
||||
|
||||
- name: mdn-url-parameters
|
||||
src: mdn-url-parameters@x2.png
|
||||
title: >-
|
||||
[What is a
|
||||
URL?](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_is_a_URL#parameters)
|
||||
by [Mozilla
|
||||
Contributors](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_is_a_URL/contributors.txt)
|
||||
is licensed under [CC-BY-SA
|
||||
2.5](https://creativecommons.org/licenses/by-sa/2.5/)
|
||||
|
||||
---
|
||||
|
||||
Knowing the basic structure and parameters in a YouTube URL can come in handy on
|
||||
the occasion you need it. Here's how to find the video ID, link to a specific
|
||||
timestamp, and more.
|
||||
|
||||
<!--more-->
|
||||
|
||||
## What is youtu.be?
|
||||
|
||||
YouTube has its own domain for [URL
|
||||
shortening](https://en.wikipedia.org/wiki/URL_shortening): `youtu.be`. It's
|
||||
roughly equivalent to `youtube.com/watch`.
|
||||
|
||||
## Query parameter basics
|
||||
|
||||
Query parameters can be added to a URL just by suffixing it with something like
|
||||
`?key=value&something=else`. That example sets `key` to `value` and `something`
|
||||
to `else`. Note how the first parameter is prefixed with `?`, and then the
|
||||
following parameters are separated with `&`.
|
||||
|
||||
{{< figure src="mdn-url-parameters" >}}
|
||||
|
||||
See the [page on the Mozilla Developer
|
||||
Docs](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_is_a_URL)
|
||||
for more information on the anatomy of a URL.
|
||||
|
||||
## Linking to a video
|
||||
|
||||
Here's the video I'll be using as an example:
|
||||
|
||||
{{< youtube F6va6tg62qg >}}
|
||||
|
||||
I embedded that video on my website with this code:[^hugo-shortcode]
|
||||
|
||||
```text
|
||||
{{</* youtube F6va6tg62qg */>}}
|
||||
```
|
||||
|
||||
The argument there (`F6va6tg62qg`) is the video ID, which is the unique
|
||||
identifier for the video. Here's how the YouTube URLs for that video look:
|
||||
|
||||
- https://www.youtube.com/watch?v=F6va6tg62qg
|
||||
- https://youtu.be/F6va6tg62qg
|
||||
|
||||
Take note that on `youtube.com`, the video ID is provided as a [query
|
||||
parameter](#query-parameter-basics), and on `youtu.be`, it's just provided as
|
||||
the path of the URL.
|
||||
|
||||
## Linking a specific timestamp
|
||||
|
||||
You can add the `t=` parameter to the URL to have it automatically seek to a
|
||||
specific timestamp when opened. The value can be expressed in hours, minutes,
|
||||
and seconds (using `h`, `m`, and `s` respectively). Here's how that looks:
|
||||
|
||||
- https://www.youtube.com/watch?v=F6va6tg62qg&t=14s
|
||||
- https://youtu.be/F6va6tg62qg?t=14s
|
||||
|
||||
Unfortunately my example video isn't long enough to show hours or minutes, so
|
||||
here's a different one:
|
||||
|
||||
- https://www.youtube.com/watch?v=dQw4w9WgXcQ&t=3m14s
|
||||
- https://youtu.be/dQw4w9WgXcQ?t=3m14s
|
||||
|
||||
Those link 3 minutes and 14 seconds into the video. Notice how the `youtube.com`
|
||||
link prefixes the `t=` parameter with an `&` since it's the second parameter.
|
||||
The `youtu.be` link just uses a `?` because it's the first (and only) parameter.
|
||||
|
||||
## Playlists
|
||||
|
||||
The `list=` parameter contains the ID of the playlist you're watching the video
|
||||
from, if any. Otherwise, the parameter is omitted. Here's how that looks:
|
||||
|
||||
- https://www.youtube.com/watch?v=47dtFZ8CFo8&list=PLwxnUUM01nt2nMh9DPq09e6fIDbumybgt
|
||||
- https://youtu.be/47dtFZ8CFo8?list=PLwxnUUM01nt2nMh9DPq09e6fIDbumybgt
|
||||
|
||||
There, the playlist ID was `PLwxnUUM01nt2nMh9DPq09e6fIDbumybgt`. You can link to
|
||||
the playlist itself with a format like:
|
||||
|
||||
```text
|
||||
https://youtube.com/playlist?list=[playlist_id]
|
||||
```
|
||||
|
||||
For example, the direct link to the playlist in the two example links I used is:
|
||||
|
||||
- https://youtube.com/playlist?list=PLwxnUUM01nt2nMh9DPq09e6fIDbumybgt
|
||||
|
||||
As far as I know, it's not possible to link to a playlist using `youtu.be`.
|
||||
|
||||
## Further reading
|
||||
|
||||
[This Stack Exchange answer](https://webapps.stackexchange.com/a/9881) is a good
|
||||
reference for some other YouTube parameters.
|
||||
|
||||
[^hugo-shortcode]: I use a static site generator called
|
||||
[Hugo](https://gohugo.io) for my website. It has a built in "shortcode" which
|
||||
is a feature that allows me to embed certain code blocks into a page. One of
|
||||
its shortcodes, named `youtube`, allows me to embed a YouTube video into my
|
||||
post. You can read more info about [shortcodes on the Hugo
|
||||
docs](https://gohugo.io/content-management/shortcodes/#use-hugos-built-in-shortcodes)
|
After Width: | Height: | Size: 5.9 KiB |
After Width: | Height: | Size: 3.3 KiB |
7
content/categories/_index.md
Normal file
@ -0,0 +1,7 @@
|
||||
---
|
||||
|
||||
title: Categories
|
||||
|
||||
---
|
||||
|
||||
List of categories on my website. These are different types or styles of posts.
|
11
content/categories/devops/_index.md
Normal file
@ -0,0 +1,11 @@
|
||||
---
|
||||
|
||||
title: DevOps
|
||||
|
||||
---
|
||||
|
||||
Posts about toolchain and software pipeline stuff. The abbreviation means
|
||||
software development (Dev) plus IT operations (Ops). Includes things such as
|
||||
CI/CD (GitHub Actions).
|
||||
|
||||
<!--more-->
|
9
content/categories/guides/_index.md
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
|
||||
title: Guides
|
||||
|
||||
---
|
||||
|
||||
Any kind of guide or tutorial.
|
||||
|
||||
<!--more-->
|
9
content/categories/jailbreak/_index.md
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
|
||||
title: Jailbreak
|
||||
|
||||
---
|
||||
|
||||
Anything related to jailbreaking (iOS or other Apple devices).
|
||||
|
||||
<!--more-->
|
9
content/categories/linux/_index.md
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
|
||||
title: Linux
|
||||
|
||||
---
|
||||
|
||||
Anything relating to Linux (the kernel or operating systems).
|
||||
|
||||
<!--more-->
|
9
content/categories/meta/_index.md
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
|
||||
title: Meta
|
||||
|
||||
---
|
||||
|
||||
Posts talking about my website.
|
||||
|
||||
<!--more-->
|
9
content/categories/programming/_index.md
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
|
||||
title: Programming
|
||||
|
||||
---
|
||||
|
||||
Any posts relating to programming and/or software development.
|
||||
|
||||
<!--more-->
|
9
content/categories/software/_index.md
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
|
||||
title: Software
|
||||
|
||||
---
|
||||
|
||||
Posts that discuss/review various programs.
|
||||
|
||||
<!--more-->
|
10
content/categories/sysadmin/_index.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
|
||||
title: Sysadmin
|
||||
|
||||
---
|
||||
|
||||
Anything relating to managing servers (usually relating to Linux). "Sysadmin" is
|
||||
short for "system administrator".
|
||||
|
||||
<!--more-->
|
9
content/categories/tinkering/_index.md
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
|
||||
title: Tinkering
|
||||
|
||||
---
|
||||
|
||||
Posts where I experiment with things.
|
||||
|
||||
<!--more-->
|
10
content/categories/tips-and-tricks/_index.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
|
||||
title: Tips and Tricks
|
||||
|
||||
---
|
||||
|
||||
Random little tips and/or tricks that I want to share. Will probably be mostly
|
||||
short articles (but that's not a bad thing).
|
||||
|
||||
<!--more-->
|
@ -3,12 +3,18 @@
|
||||
title: Contact
|
||||
menu: main
|
||||
toc: false
|
||||
comments: false
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
description: >-
|
||||
Want to contact me? Here's how you can.
|
||||
|
||||
---
|
||||
|
||||
- Email: [contact@bbaovanc.com](mailto:contact@bbaovanc.com)
|
||||
- Matrix: [@bbaovanc:boba.best](https://matrix.to/#/@bbaovanc:boba.best)
|
||||
- Email: bbaovanc@bbaovanc.com
|
||||
- If needed, encrypt your email with [my PGP
|
||||
key](https://keyserver.ubuntu.com/pks/lookup?search=bbaovanc%40bbaovanc.com&fingerprint=on&op=index)
|
||||
- GitHub Discussions (Q&A):
|
||||
https://github.com/BBaoVanC/bbaovanc.com/discussions/categories/q-a
|
||||
|
@ -3,11 +3,14 @@
|
||||
title: Donate
|
||||
menu: main
|
||||
toc: false
|
||||
comments: false
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
description: >-
|
||||
I have a few cryptocurrency addresses that you can use if you want to donate to
|
||||
me.
|
||||
I have a few cryptocurrency addresses that you can use if you want to donate
|
||||
to me.
|
||||
|
||||
---
|
||||
|
||||
|
@ -3,7 +3,10 @@
|
||||
title: Links
|
||||
menu: main
|
||||
toc: true
|
||||
comments: false
|
||||
comments: true
|
||||
|
||||
authors:
|
||||
- bbaovanc
|
||||
|
||||
aliases:
|
||||
- /blog/links/
|
||||
@ -15,41 +18,57 @@ description: >-
|
||||
|
||||
## Other
|
||||
|
||||
- [GitHub](https://github.com/BBaoVanC/)
|
||||
- [GitHub](https://github.com/BBaoVanC/) - my GitHub profile
|
||||
- [boba.best](https://boba.best/)
|
||||
|
||||
## My Website
|
||||
|
||||
- [Homepage](https://bbaovanc.com/) - theme:
|
||||
[bobatheme](https://github.com/BBaoVanC/bobatheme)
|
||||
- [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/)
|
||||
- [bbaovanc.com source code](https://github.com/BBaoVanC/bbaovanc.com)
|
||||
- [bobatheme](https://github.com/BBaoVanC/bobatheme) - theme for this
|
||||
website
|
||||
- [Searx Instance](https://search.bbaovanc.com/) - privacy-respecting search
|
||||
engine
|
||||
- [Gitea Instance](https://git.bbaovanc.com/) - mostly just mirrors of my GitHub
|
||||
repos
|
||||
|
||||
## My Software
|
||||
## My Projects
|
||||
|
||||
- [smines](https://github.com/BBaoVanC/smines)
|
||||
- [imgupload.py](https://github.com/imgupload-py/imgupload.py)
|
||||
- [mojiman](https://github.com/BBaoVanC/mojiman)
|
||||
- [pynamegen](https://git.bbaovanc.com/bbaovanc/pynamegen)
|
||||
- [smines](https://github.com/BBaoVanC/smines) - TUI minesweeper in C, made for
|
||||
practice
|
||||
- [imgupload.py](https://github.com/imgupload-py/imgupload.py) - simple image
|
||||
uploading server written with Python Flask
|
||||
- [mojiman](https://github.com/BBaoVanC/mojiman) - program I made to learn Rust
|
||||
- [pynamegen](https://git.bbaovanc.com/bbaovanc/pynamegen) - name generator
|
||||
written in Python
|
||||
- [libnamegen](https://git.bbaovanc.com/bbaovanc/libnamegen)
|
||||
- [liblistloader](https://git.bbaovanc.com/bbaovanc/liblistloader)
|
||||
- [libprogress](https://git.bbaovanc.com/bbaovanc/libprogress)
|
||||
- [RokuRemote](https://github.com/BBaoVanC/RokuRemote)
|
||||
- [RokuRemote](https://github.com/BBaoVanC/RokuRemote) - keyboard-based remote
|
||||
control for Roku
|
||||
|
||||
## My Configurations
|
||||
|
||||
- [dotfiles](https://github.com/BBaoVanC/dotfiles)
|
||||
- [dwm](https://github.com/BBaoVanC/.dwm)
|
||||
- [dwm-flexipatch](https://github.com/BBaoVanC/dwm-flexipatch)
|
||||
- [dwmblocks](https://github.com/BBaoVanC/dwmblocks)
|
||||
- [dmenu](https://github.com/BBaoVanC/dmenu)
|
||||
- [dotfiles](https://github.com/BBaoVanC/dotfiles) - main repository with my
|
||||
configs
|
||||
- [docker-dotfiles](https://github.com/BBaoVanC/docker-dotfiles) - Docker image
|
||||
that contains my dotfiles
|
||||
- [onehalf](https://github.com/BBaoVanC/onehalf) - the theme I use on my
|
||||
terminal
|
||||
|
||||
### Archived
|
||||
|
||||
- [dwm](https://github.com/BBaoVanC/dwm)
|
||||
- [st](https://github.com/BBaoVanC/st)
|
||||
- [slstatus](https://github.com/BBaoVanC/slstatus)
|
||||
- [xmonad](https://github.com/BBaoVanC/.xmonad)
|
||||
- [dwm](https://github.com/BBaoVanC/.dwm) - outer repo with submodules for my
|
||||
various dwm-related configs
|
||||
- [dwm-flexipatch](https://github.com/BBaoVanC/dwm-flexipatch) - see
|
||||
https://github.com/bakkeby/dwm-flexipatch
|
||||
- [dwmblocks](https://github.com/BBaoVanC/dwmblocks) - DWM status bar, see
|
||||
https://github.com/torrinfail/dwmblocks
|
||||
- [dmenu](https://github.com/BBaoVanC/dmenu) - dynamic menu, see
|
||||
https://tools.suckless.org/dmenu/
|
||||
- [st](https://github.com/BBaoVanC/st) - simple terminal, see
|
||||
https://st.suckless.org
|
||||
- [slstatus](https://github.com/BBaoVanC/slstatus) - suckless status, see
|
||||
https://tools.suckless.org/slstatus/
|
||||
- [dwm](https://github.com/BBaoVanC/dwm) - dynamic window manager, see
|
||||
https://dwm.suckless.org/
|
||||
- [xmonad](https://github.com/BBaoVanC/.xmonad) - see https://xmonad.org
|
||||
|
7
content/series/_index.md
Normal file
@ -0,0 +1,7 @@
|
||||
---
|
||||
|
||||
title: Series
|
||||
|
||||
---
|
||||
|
||||
List of series, which are sequences of closely related posts.
|
10
content/series/github-copilot-experiments/_index.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
|
||||
title: Github Copilot Experiments
|
||||
|
||||
---
|
||||
|
||||
Make sure to read the last two posts where I made GitHub Copilot write a blog
|
||||
post itself.
|
||||
|
||||
<!--more-->
|
10
content/series/swapfile-guide/_index.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
|
||||
title: Swapfile Guide
|
||||
|
||||
---
|
||||
|
||||
A tutorial on how to set up a swapfile on Linux, but with some more depth than
|
||||
just a step-by-step.
|
||||
|
||||
<!--more-->
|
8
content/tags/_index.md
Normal file
@ -0,0 +1,8 @@
|
||||
---
|
||||
|
||||
title: Tags
|
||||
|
||||
---
|
||||
|
||||
List of tags on my website. These are specific things or ideas that I talk about
|
||||
in a post.
|
10
content/tags/arch-linux/_index.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
|
||||
title: Arch Linux
|
||||
|
||||
---
|
||||
|
||||
A Linux distribution which aims to be lightweight, flexible, and simple. See
|
||||
https://archlinux.org for more information.
|
||||
|
||||
<!--more-->
|
12
content/tags/bobanews/_index.md
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
|
||||
title: bobanews
|
||||
|
||||
---
|
||||
|
||||
The main name for my newsletter. I recommend you read the [blog post I wrote
|
||||
about it][newsletter-post].
|
||||
|
||||
[newsletter-post]: {{< ref "/blog/blog-post-newsletter" >}}
|
||||
|
||||
<!--more-->
|
12
content/tags/bobatheme/_index.md
Normal file
@ -0,0 +1,12 @@
|
||||
---
|
||||
|
||||
title: bobatheme
|
||||
|
||||
---
|
||||
|
||||
Posts about bobatheme, my custom [Hugo][hugo-website] theme which I use on this
|
||||
website.
|
||||
|
||||
[hugo-website]: https://gohugo.io
|
||||
|
||||
<!--more-->
|
14
content/tags/caddy/_index.md
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
|
||||
title: Caddy
|
||||
|
||||
---
|
||||
|
||||
Caddy is a powerful and open source webserver written in [Golang][golang] which
|
||||
includes some fancy features such as built-in automatic HTTPS. It's by far my
|
||||
favorite webserver. See my [blog post about Caddy][caddy-blog-post] for why.
|
||||
|
||||
[golang]: https://go.dev/
|
||||
[caddy-blog-post]: {{< ref "/blog/caddy-is-the-best-webserver" >}}
|
||||
|
||||
<!--more-->
|
13
content/tags/checkra1n/_index.md
Normal file
@ -0,0 +1,13 @@
|
||||
---
|
||||
|
||||
title: checkra1n
|
||||
|
||||
---
|
||||
|
||||
An [iOS jailbreak][ios-jailbreaking] which supports the iPhone 4s to the iPhone
|
||||
X. See the [official checkra1n website][checkra1n-website] for more information.
|
||||
|
||||
[ios-jailbreaking]: https://en.wikipedia.org/wiki/IOS_jailbreaking
|
||||
[checkra1n-website]: https://checkra.in/
|
||||
|
||||
<!--more-->
|
9
content/tags/discord-tricks/_index.md
Normal file
@ -0,0 +1,9 @@
|
||||
---
|
||||
|
||||
title: Discord Tricks
|
||||
|
||||
---
|
||||
|
||||
Tips and tricks I have learned about Discord.
|
||||
|
||||
<!--more-->
|
14
content/tags/discord/_index.md
Normal file
@ -0,0 +1,14 @@
|
||||
---
|
||||
|
||||
title: Discord
|
||||
|
||||
---
|
||||
|
||||
An extremely popular chat platform. You have to live under a rock to not know
|
||||
what Discord is.
|
||||
|
||||
<!--more-->
|
||||
|
||||
See also: the [discord-tricks tag][discord-tricks-tag].
|
||||
|
||||
[discord-tricks-tag]: {{< ref "/tags/discord-tricks/" >}}
|