Good to note this example is from 2022-08-30. Despite its “reputation” among some, Arch doesn’t break that often by itself.

Not OP, but modularity. An X11 WM is just a WM. You can choose compositor, bar, shortcut daemon, etc. With Wayland, a single implementation holds most of that, and more. If you need a specific feature from your display server, you are stuck on WMs that support it. This has forced me to use KDE for Wayland on my main workstation, and although it works well, it’s not my prefered WM/workflow.

Alongside that, no clones of several X11 WMs exist. bspwm for example. Riverwm exists, but has major limitations, and the workflow isn’t the same.

https://ntfy.sh/

Easily set up, and easily attached to other things. Simple notifications about whatever is needed, like service health or updates, new posts on public platforms, etc. A simple curl is plenty to send and receive notifications, and it works on Android without requiring FCM (Google infrastructure).

1. A puppeting (personal account) Discord bridge basically requires your own homeserver. You are trusting the homeserver owner / bridge host fully with your Discord account.
2. It is technically against Discord ToS. While I don’t think anyone’s been banned yet, several people have started receiving warnings that they “spammed”, most of them after sending an attachment. These warnings are on your account for 2 years, and could contribute to an account ban.
3. Voice chat is not, and probably will not be supported.
4. Do NOT bridge a “large” server. You are essentially re-hosting the chats, which can be extremely taxing for large and active Discord servers.

I use mine for a single channel in a “medium-size” server (~2k people), a friend group server, DMs, and a few channels that follow a bunch of announcement channels on other servers.