Thanks for asking. Not sure how I toggled that on…

You can put the game into its own time namespace.

https://www.man7.org/linux/man-pages/man7/time_namespaces.7.html

Mozilla stated that a while back.

How do I capitalize Firefox? How do I abbreviate it?

Only the first letter is capitalized (so it’s Firefox, not FireFox.) The preferred abbreviation is “Fx” or “fx”.

#8 in the FAQ

You’re right, it doesn’t. That does give me an idea though.

You could use overlayfs with an opaque upper directory to hide the files littering your $HOME and still access them by bind-mounting them into the appropriate xdg dirs.

Way more effort than it’s worth, of course.

I’m not the best person to ask as I just chat on a few channels in a single server.

There definitely are software projects that run their real-time support through Matrix in the same way others do it through IRC or Discord.

At the same time most servers seem to have a General room (or similar) for off-topic chats.

Peruse the big list of public rooms here. That might give you a sense of it.

Featureset-wise it falls somewhere between IRC and Discord.

Custom bangs are private to the user. It’s not dissimilar to saving a bookmark in your browser, except your bookmarks are hosted by someone else.

It doesn’t have to be about legality either. Maybe you like a service that is being protested by DDG for whatever reason.

But they don’t allow bangs for sites that do illegal things like copyright infringement. Libgen was my example.

Make an effort to use bangs and I bet you’ll stay under the limit. Edit: bang searches don’t count towards the limit

Knowing I wanted a result from a certain site but using the search engine to get there was a (bad) habit I brought over from Google.

!imdb barbie

!w mattel

There’s even custom bangs, which is something DDG doesn’t give you: !libgen some book

Not the parent poster, but I am similarly concerned about tag spam. I find big tag blocks can ruin the reading experience on platforms that display them in-line with the body text.

Another comment suggested that tags be put in a field separate from the body of the post (and they shouldn’t be parsed from the body, either). I think that’s the best way to facilitate Lemmy clients to (optionally) hide big tag blocks.