𝘋𝘪𝘳𝘬

It first checks if ~/.bashrc.d is an existing directory. If this it the case it then iterates over all entries in that directory. In this iteration it checks if the entry is a file and if this is the case it sources that file using the bash-internal shorthand . for source.

So it basically executes all scripts in ~/.bashrc.d. This makes it possible for you to split your bash configuration into multiple files. This quite common and a lot of programs already support it (100% depends on the program, though).

This is absolutely harmless as it is. But: if you or a program places anything in the directory ~/.bashrc.d it WILL be sourced everytime you start a bash.

A slightly better variant would be iterating over ~/.bashrc.d/*.sh instead of just ~/.bashrc.d/* to make sure to only grab files with the .sh suffix (even if suffixes are basically meaningless from a technical point of view) and also test for the file being executable (-x instead of -f).

This would make sure that only files that are ending with .sh and that are executable are sourced. The “attack vector”, if you want to call it like that, would then be a bit more narrow than just placing a file in a directory.

As for why it’s there: Did you ever touch your .bashrc? If not, maybe it is there since the beginning because it’s in the so-called skeleton (see /etc/skel/.bashrc) that was used to initialize certain files on user account creation.

Use XMPP. Thanks to Let’s Encrypt being implemented in basically every reverse proxy, setting it up is a matter of seconds.

Warp is closed source and [needs a mandatory account, and] Wave is an Electron app.

You host it locally and use a web browser to access it.

A blast from the past!

The -vvv I know is the same as -v -v -v. Can’t check right now, but is the short parameter -f? So maybe give -ff a try …

You just really force it.

It’s like with -v in various applications. -v means “verbose”, and -vv means “really verbose”, and -vvv means “an ungodly amount of data printed to the terminal, so much that it might crash”.

For that reason, Mono was avoided by linux app developers. But since MS had acquired the company that made and developed Mono

“You don’t like it? Fine then, we buy it and force it on you!”

Classic Microshit.

I remember ZoneMinder.

A full-featured, open source, state-of-the-art video surveillance software system.

https://zoneminder.com/

Is this still a thing nowadays?

Yeah … I just hope they’re now being able to decouple the UI and the core and make it easier to migrate to more recent UI toolkits.

port from GTK2 to GTK3

Migrating from an already rooten toolkit to a toolkit that is dead since a few years.

Nice.

Also reliability, speed, and quality.

established standard for HTML

That is constantly changing.

Like CSS or JS, or other modern web technologies nowadays browsers are capable of.

Samsung T7 totally worth every cent. You connect it via USB-C.

Came here to say exactly this.

Reads like XMPP.

GoToSocial is awesome. Some features are still missing, but the server is in active development.

As front-end I use Elk. It’s selfhostable as well as publicly usable at https://elk.zone. It’s labeled as alpha software but runs absolutely well.

Great, isn’t it? You just set up a system you like for you to use, without any bullshit.

I wonder if Arch makes people unhappy or if unhappy people chose Arch.

I have to use Windows on my work computer and I am finding it hard to get FOSS applications on Windows that can do stuff like

The Gold standard in the screen recording world is OBS. It’s not only available for Linux, but also for Windows and, well, is the gold standard. If you ask the question if OBS can do this-or-that regarding screen recording, the answer generally is yes (or “yes, via plugin”). Just use OBS on all platforms, it’s clearly the most mature screen recording tool out there.