Removing my Misskey instance

My self-hosted misskey instance is shutting down. This commit remove
any related link to my misskey instance.

content/blog/announcement-permanently-shutdown-services-and-public-nodes/index.id.md

@@ -30,14 +30,14 @@ authors:
   - ditatompel
 ---
 
-Layanan-layanan saya seperti **Monero _Public_ Node** (*mainnet*, *stagenet*, dan  *testnet*), **Peertube** dan **Mastodon** akan saya tutup secara permanen per tanggal 25 Juni 2023.
+Layanan-layanan saya seperti **Monero _Public_ Node** (*mainnet*, *stagenet*, dan  *testnet*), **Peertube**, **Misskey**, dan **Mastodon** akan saya tutup secara permanen per tanggal 25 Juni 2023.
 
 <!--more-->
 ---
 
 *Dear Users*,
 
-Saya harap pengunguman ini sampai kepada Anda dengan baik. Sudah lebih dari 2 tahun saya menjalankan **Monero _Public_ Node**, **Peertube**, dan **Mastodon** instance. Suatu kehormatan bagi saya dapat menjalankan layanan-layanan tersebut secara gratis untuk umum, terutama untuk komunitas dan pengguna **Monero**.
+Saya harap pengunguman ini sampai kepada Anda dengan baik. Sudah lebih dari 2 tahun saya menjalankan **Monero _Public_ Node**, **Peertube**, Misskey, dan **Mastodon** instance. Suatu kehormatan bagi saya dapat menjalankan layanan-layanan tersebut secara gratis untuk umum, terutama untuk komunitas dan pengguna **Monero**.
 
 Selama beberapa bulan terakhir, ada beberapa kendala yang saya alami dalam menyediakan dan melakukan *maintenance* layanan-layanan tersebut, sehingga dengan sangat berat hati saya memutuskan untuk menutup layanan-layanan tersebut secara permanent.
 
@@ -48,12 +48,11 @@ Ada beberapa sebab dan alasan yang memaksa saya untuk tidak dapat melanjutkan la
 
 Berikut ini adalah layanan-layanan publik yang akan saya tutup secara permanen:
 - `xmrnode1.ditatompel.com`, Monero `mainnet` Public Remote Node, termasuk untuk RPC dan P2P.
-- `stagenet.xmr.ditatompel.com`, Monero `stagenet` Public Remote Node, termasuk untuk RPC dan P2P.
-- `testnet.xmr.ditatompel.com`, Monero `testnet` Public Remote Node, termasuk untuk RPC dan P2P.
 - `tube.ditatompel.com`, Peertube instance.
 - `sts.ditatompel.com`, Mastodon instance.
+- `hey.ditatompel.com`, Misskey instance.
 
-Layanan-layanan diatas akan saya tutup secara permanen per tanggal 5 Novemver 2023. Jika Anda pernah melakukan registrasi di **Peertube** dan **Mastodon** *instance* saya, mohon untuk segera melakukan download data Anda yang berada disana.
+Layanan-layanan diatas akan saya tutup secara permanen per tanggal 5 Novemver 2023. Jika Anda pernah melakukan registrasi di **Peertube**, **Misskey**, dan **Mastodon** *instance* saya, mohon untuk segera melakukan download data Anda yang berada disana.
 
 > _layanan pengecekan Monero Remote Node yang diakses dari [https://www.ditatompel.com/monero/remote-node](https://www.ditatompel.com/monero/remote-node) akan **tetap berjalan seperti biasa**._
 

content/blog/announcement-permanently-shutdown-services-and-public-nodes/index.md

@@ -30,14 +30,14 @@ authors:
   - ditatompel
 ---
 
-I will permanently close my services such as the **Monero Public Node** (*mainnet*, *stagenet*, and *testnet*), **Peertube** and **Mastodon** as of June 25, 2023.
+I will permanently close my services such as the **Monero Public Node** (*mainnet*, *stagenet*, and *testnet*), **Peertube**, **Misskey** and **Mastodon** as of June 25, 2023.
 
 <!--more-->
 ---
 
 Dear Users,
 
-I hope this announcement finds you well. It's been more than 2 years that I run Monero Public Node, Peertube, and Mastodon instances. It is an honor for me to be able to run these services free of charge for the public, especially for the Monero community and users.
+I hope this announcement finds you well. It's been more than 2 years that I run Monero Public Node, Peertube, Misskey, and Mastodon instances. It is an honor for me to be able to run these services free of charge for the public, especially for the Monero community and users.
 
 For the last few months, I have several problems in providing and maintaining these services, so I decided to permanently close these services. It's hard for me, but I have to.
 
@@ -48,12 +48,11 @@ There are various reasons that make me unable to continue to maintain these serv
 
 The following services will be close permanently:
 - `xmrnode1.ditatompel.com`, Monero `mainnet` Public Remote Node, including RPC and P2P.
-- `stagenet.xmr.ditatompel.com`, Monero `stagenet` Public Remote Node, including RPC and P2P.
-- `testnet.xmr.ditatompel.com`, Monero `testnet` Public Remote Node, including RPC and P2P.
 - `tube.ditatompel.com`, Peertube instance.
 - `sts.ditatompel.com`, Mastodon instance.
+- `hey.ditatompel.com`, Misskey instance.
 
-I will permanently close the services above as of November 5th, 2023. If you have ever registered on my Peertube and Mastodon instances, please download your data as soon as possible.
+I will permanently close the services above as of November 5th, 2023. If you have ever registered on my Peertube, Misskey, and Mastodon instances, please download your data as soon as possible.
 
 > _The Monero Remote Node checker service ([https://www.ditatompel.com/monero/remote-node](https://www.ditatompel.com/monero/remote-node)) still **continue to run as usual**._
 
@@ -61,4 +60,4 @@ I apologize and hope this announcement can be understood and well received, than
 
 Sincerely,
 
-ditatompel
+ditatompel

content/tutorials/how-to-install-misskey-in-ubuntu-22-04-manual-without-docker/index.md

@@ -174,7 +174,7 @@ Dont forget to save managed process by PM2 using `pm2 save` command.
 ## Updating Misskey
 To update Misskey that run using NodeJS (via NPM and PM2), you can follow my another article: [Misskey NodeJS (NVM with PM2) update steps]({{< ref "/tutorials/misskey-nodejs-nvm-with-pm2-update-steps/index.md" >}}).
 
-That's it, and welcome to another awesome Fediverse project! Take a look my Fediverse account [@ditatompel@hey.ditatompel.com](https://hey.ditatompel.com/@ditatompel) from Misskey.
+That's it, and welcome to another awesome Fediverse project!
 
 ## Resources
 - [Misskey-hub.net :official installation page](https://misskey-hub.net/en/docs/install/manual.html)

content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.id.md

@@ -44,14 +44,10 @@ Artikel ini membahas mengenai cara menginstal Mastodon di Ubuntu 20.04 beserta d
 
 Catatan: saya menggunakan *self-signed* SSL *certificate* karena *instance* yang akan saya jalankan akan berada dibalik **Cloudflare** *reverse proxy*.
 
-Video **asciinema** saat proses installasi dan konfigurasi Mastodon dapat dilihat dibawah ini:
+Video saat proses installasi dan konfigurasi Mastodon dapat dilihat dibawah ini:
 
-<script id="asciicast-14" src="https://asciinema.ditatompel.com/a/14.js" async></script>
-
-Atau full YouTube Video:
 {{< youtube eBUr7JFiGMo >}}
 
-
 ## Pre-requisites
 Sebelum memulai, ada beberapa syarat yang harus dipenuhi untuk dapat menjalankan Mastodon, yaitu:
 
@@ -243,4 +239,4 @@ systemctl enable --now mastodon-web mastodon-sidekiq mastodon-streaming
 Tunggu beberapa menit dan coba akses Mastodon dari web broser dan selamat menikmati!
 
 ## Resources
-* [https://docs.joinmastodon.org/admin/install/](https://docs.joinmastodon.org/admin/install/)
+* [https://docs.joinmastodon.org/admin/install/](https://docs.joinmastodon.org/admin/install/)

content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.md

@@ -41,11 +41,7 @@ authors:
 
 This article is my personal snippet for running Mastodon instance on Ubuntu 20.04 from source. I use *self-signed* certificate instead of **cerbot** because the instance will be run behind **Cloudflare** reverse proxy.
 
-The **asciinema** video below is the whole process I install Mastodon instance (for reference)
-
-<script id="asciicast-14" src="https://asciinema.ditatompel.com/a/14.js" async></script>
-
-Or the whole YouTube video:
+The video below is the whole process I install Mastodon instance (for reference)
 
 {{< youtube eBUr7JFiGMo >}}
 

content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.id.md

@@ -34,7 +34,7 @@ authors:
   - ditatompel
 ---
 
-Hari ini, saya menemui kendala saat melakukan upgrade [self-hosted asciinema-server](https://asciinema.ditatompel.com/) milik saya. Setelah [mengikuti proses upgrade sesuai dokumentasi asciinema-server di GitHub](https://github.com/asciinema/asciinema-server/wiki/Installation-guide#upgrading), *container* `phoenix` dan `postgres` gagal berjalan dan selalu restart.
+Hari ini, saya menemui kendala saat melakukan upgrade _self-hosted_ **asciinema server** milik saya. Setelah [mengikuti proses upgrade sesuai dokumentasi asciinema-server di GitHub](https://github.com/asciinema/asciinema-server/wiki/Installation-guide#upgrading), *container* `phoenix` dan `postgres` gagal berjalan dan selalu restart.
 
 <!--more-->
 
@@ -147,4 +147,4 @@ docker exec -it <DOCKER_CONTAINER_ID> psql -d postgres -U postgres -f /var/lib/p
 > **Catatan**: `DOCKER_CONTAINER_ID` Anda akan berbeda dengan `DOCKER_CONTAINER_ID` yang sebelumnya. Pastikan gunakan *docker container ID* yang benar.
 
 ### Jalankan asciinema-server seperti biasa
-Setelah itu, jalankan semua service asciinema-server seperti biasa dengan menjalankan perintah `docker-compose up -d`. Seharusnya Anda sudah dapat menggakses **self-hosted asciinema-server** Anda kembali.
+Setelah itu, jalankan semua service asciinema-server seperti biasa dengan menjalankan perintah `docker-compose up -d`. Seharusnya Anda sudah dapat menggakses **self-hosted asciinema-server** Anda kembali.

content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.md

@@ -34,7 +34,7 @@ authors:
   - ditatompel
 ---
 
-Today, I'm experiencing some problem with my recent [self-hosted asciinema-server](https://asciinema.ditatompel.com/) upgrade. After following the upgrade process according to the [asciinema-server documentation page on GitHub](https://github.com/asciinema/asciinema-server/wiki/Installation-guide), the `phoenix` and `postgresql` containers failed to run and kept restarting.
+Today, I'm experiencing some problem with my recent self-hosted asciinema server upgrade. After following the upgrade process according to the [asciinema-server documentation page on GitHub](https://github.com/asciinema/asciinema-server/wiki/Installation-guide), the `phoenix` and `postgresql` containers failed to run and kept restarting.
 
 <!--more-->
 
@@ -153,4 +153,4 @@ docker exec -it <DOCKER_CONTAINER_ID> psql -d postgres -U postgres -f /var/lib/p
 > _**Note**: Your `DOCKER_CONTAINER_ID` will be different from the previous `DOCKER_CONTAINER_ID`. Make sure to use the correct docker container ID._
 
 ### 4. Run asciinema-server as usual
-After that, run all the `asciinema-server` services as usual (`docker-compose up -d`), and you should be able to **access your self-hosted asciinema-server** again.
+After that, run all the `asciinema-server` services as usual (`docker-compose up -d`), and you should be able to **access your self-hosted asciinema-server** again.