me before reading this: I know the basics of CSS.

me after reading this: I know nothing about CSS.

git is already a decentralized version control software. Your local git repos are mirrors by themselves.

Put some git fetch in a server crontab, and you’re done. You can access them via ssh if your user have permissions.

Sorry, I can’t hear you over the artillery noise.

As a spanish/romance speaking person: ahahahah LOL!

Where do you thing “gratis” and “libre” come from?

Wait.

Does Portainer ask your email? I haven’t used it in years. I though it was just a container that you run, with mounted docker socket, and that’s it.

Is it now doing some “telemetry” and sending user data, like email, to their servers? If so, I’m glad I’m not using that anymore.

VPS + VPN is the cheapest option I believe for the services. It doesn’t have to be “elaborated”.

You can port-forward public VPS ports to your private addresses/ports. If you don’t want to use iptables you can use firewalld.

The only “but” will be latency. For gaming it won’t perform as you may need.

• https://major.io/p/forwarding-ports-with-firewalld/
• https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/security_guide/sec-port_forwarding#sec-Adding_a_Port_to_Redirect

It’s no longer open source. Big Deal in my books.

Vault features are cool. I really like it. But with Hashicorp now there is this big risk of “rug pulling” regarding its license.

The wise thing, in my opinion, is to avoid this company as much as possible.

Not true.

The immutability of the thing is just Merkle trees. And integrity of the writings is any form of authorized blocks. From a certificate from an authority a la PKI to proof of work. And anything in between.

The thing is that there are not too many applications for slow distributed inmutable databases.

DNS is the only thing that I know that is globally distributed, with slow updates of domains being acceptable.

omg they were roommates!

You missed the part of they just hating money.

A slow but decentralized and immutable database can have it’s applications. You can have a semi-decentralized one if it’s needed, doing stuff like PKI. I wish DNS were like that.

But the popular use is currencies. And scams. And people here seems to hate money, even more than actual scams.

Why not both?

If you’re concerned about security, consider GPG signing your kernel with Libreboot GRUB for an additional layer of verification at boot.

Hey! I had no idea that was possible. I usually encrypt everything but /boot, because it’s easy that way.

I don’t have a “threat model” of someone puting malware in /boot while I’m away of the computer. But it would be nice to know how to prevent that.

Do you have a link of a guide or tutorial for that?

Keys and tokens will be shared securely via singaporean hotels wifi.

If your comments have been federated to other instances, they will be there until they are deleted locally. If someone clicks on your user profile, they will get a DNS error if the domain is no longer there. Images in the comments pointing to you instance will be broken too. Nothing terrible actually happens.

Migrating accounts a la Mastodon is not happening soon in Lemmy.

My advice is: Go on and save some money.

Sorry to read that.

I’ve dded an external drive instead of an SD card once by mistake. I’ve never felt more stupid than that day.

Friends don’t let friends to use snap.

I used to love Ubuntu. But for many reasons, snaps among them, it no longer exists to me. It’s just Mint or Debian if I need something Ubuntu-like.

It’s running NetBSD, isn’t it?

Some security tips:

Firewall should block everything by default, and you start allowing incoming and outgoing connections when you need them or if something fails.

Disable passwords and root access in ssh daemon.

Use fail2ban or something similar to block bots failing to log-in.

Use random long passwords for everything (eg: like databases). And put then in a password manager. If you can remember the database password, it’s not strong enough. If you can remember the admin password for a public web service, it’s weak.

Don’t repeat the passwords. Everything should have its own random long password.

.env files and files with secrets should be readable only by its service user. Chmod them to 400.

Monitor logs from time to time to see if something funny is happening.

Random ports are easy to discover and there are tools to discover what service is behind a port.

It’s annoying for the legitimate user and easy to bypass by an actual attacker.

Also, if you use a random port above 1024 it could be a security issue since any user could star listening if the legitimate process crashes.

See this