dbx12

The thing you are thinking about is called TOTP or timed one time password.

The XDG default location would be ~/.config/autostart/. It contains .desktop files for programs to start automatically.

What if I know it will compile for several minutes so I leave it alone to go office chair jousting? It would be fair to lock up the UI in this case.

When you are allowed into the vicinity of this kind of equipment, you should be able to identify matching shapes without circles in the first place…

You both are wrong! I wrote my own distro with opinionated modifications and it is superior to both of your distros!

Masks don’t only protect from airborne viruses…

Oh, that makes warnings errors and does not mean “ignore errors”. I’m not too familiar with compiler flags. You could do some mental gymnastics to argue that the unused variable causes the compiler to exit and thus the code is not functioning and thus the unused variable is not a warning but an error :^)

I for my part prefer it that way. Makes sure the code stays clean and nobody can just silence the warnings and be done with it. Because why would you accept useless variables that clutter the code in production builds? Imagine coming back after some time and try to understand the code again. At least you have the guarantee the variable is used somehow and not just “hmm, what does this do? … ah, it’s unused”

Unused variable is an error which fails to compile.

And half of them are “curated list of X”

Hmm, I see. The perfectionist in me would want to shed that processor load though ^^

Without any judgement: why are your servers running X11? Just because you dislike SSH’ing to them?

Review is done before code gets into main, but that’s inefficient for most of the non-mission critical projects out there. A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.

Assuming you have a project with continuous delivery, that is an absolute foot gun. Optimistically merge the change and then realize in situ that you forgot the WHERE part of your SQL command (or analog statement of the query builder)? No fucking thanks.

Yep, it’s a repost of this one.

One could even think this OP is an alt account.

There are some good points in it but the list feels poorly written as it contains very general tips which feel like fluff to increase the article length like:

Protect the client-side against attacks.

Or just wrong stuff like:

Validate all server-side input data.

If you can trust someone, it’s the server. You should validate data coming from the client on the server side.

Some things even contradict each other like

Implement strong authentication, such as two-factor authentication (2FA).

And

Use secure authentication mechanisms such as OAuth.

Assuming your app is an OAuth client, you have no say in how the identity provider identifies the user.

Good point, but even better than

Monitor file and source code integrity.

is having the application source code read-only, ideally owned by another user to avoid the confused deputy problem.

If all of those servers are yours (which they likely are, since you get ssh access), you can use one key for all. Using different keys would make one compromised key less problematic. But if someone was able to copy one file of your system, they can copy multiple files.

That resolves keeping track of things as well 😄

absolute galaxy brain moment

The stalebot is most times useless. The only scenario where I can see use of it is a maintainer waiting for the reporter to add information. But closing issues because no maintainer checked on them? That’s garbage and discourages bug reports.

I use the cookiebro extension for that. Allows whitelisting domains or single cookies and can clean up all others with a few clicks.

I would recommend key based authentication for SSH connections. For the normal connection, the key pair is enough, if you want admin (root) access, you would use the command sudo which in turn requires a password. For creating a default admin account: Linux does this for you, it’s called root. You should create a personal user to work with in daily business and add it to the sudoers group (permits using the sudo command)