Good point.

Ooh, typo. I’ll edit it so that those who fulfill these kinds of things know not to glass your home.

Trilium. You’ll be glass glad you tried it.

Syncthing-fork on fdroid.

Womp womp

Heh. I was kinda playing at being a Debian elitist.

But yeah, none of the major distros get there without reason.

I had to ditch my girlfriend because she became an arch elitist. Debian ftw.

Yeah, there’s stuff to like, but… but…

I just disable most of the Pop stuff and use vanilla gnome.

So, all of the awkward pauses, the lack of inflection - you’re saying keep those, just change who it sounds like is speaking?

I use digital ocean as dns host. They have an API, so I check my IP with a script and update if needed.

Sick burns

licks the edible paper, but it tastes like plant

meows

Interesting how you use “simple” and “mail server” in the same sentence.

And, how does what you said cancel out what you responded to?

What you probably want is a dmz or red/green localnets. A reverse proxy (as others have mentioned) like haproxy or nginx) are extremely unlikely to, themselves, be hacked. But they don’t really add security, either.

What does add security is to have a router with a firewall, with one or more red networks, and a green network.

The red network has all of your public-facing servers. They have virtually no external access, and no internal access except to respond. It’s even good to have a rule on the router that you can turn on/off that blocks all outbound connections from the red network to the external world. To upgrade a server, turn off the rule, upgrade, and then turn the rule on again. The router only forwards inbound connections from the internet on a specific port, and routes them to the server/servers on the red network(s) on a (possibly different) specific port.

Most ownage-style hacks involve (once compromised) either calling home (can’t if the server is not allowed outbound connections) or opening an additional port (who cares, the router will never forward anything to that port).

Then, back up your important info, and keep multiple copies of that info - daily for a week, monthly for a few months, and yearly.

I do say that with certainty. And I didn’t claim that proof of stake has no environmental impact - it just doesn’t have more impact than, for example, a web server.

If I start a carbon-neutral wing of an oil company, of course it doesn’t make an oil company carbon-neutral. However, that doesn’t impact the real value of other companies that actually are carbon neutral.

Similarly, Ethereum is, by far, not a “green” tech, and their usage of proof of stake can easily and reasonably be called greenwashing if they don’t also severely limit the usage of POW.

Proof of Stake, though, is not a power-hungry tech, period. And it is a means for crypto to become, overall, a nominal energy user. There are other chains out there (cardano, algorand, nano, and many others) that don’t use PoW and that use reasonable amounts of energy.

I appreciate your passion for the environment. But misrepresentation does not help your case, though misrepresentation may help those your fight.

Well said. Solid facts.

Not “especially”, but “specifically” POW. I don’t agree about their worthlessness, but even if I did, it’s POW that’s shitting on the environment, not other systems.

Think of it like this:

• there’s a syncthing share
• you connect any devices you want to that share
• each device uses a local folder to act as that share
• the devices need to know each other

Then, syncthing sorts it all out. You can move a file into the share on phone1, and it’ll show up on phone2. Move it out of that share on phone2, and it disappears from phone1. Same deal for any other device connected to that share.

You can make this all simpler by using the same name for the share and on all folders:

• A share named Kim-n-Max
• A folder named /storage/emulated/0/shares/Kim-n-Max on Max’s phone
• A folder named /storage/Kim-n-Max on Kim’s phone
• A folder named c:\Users\Max\Kim-n-Max on Max’s computer

…all is pretty clear then.

One of us… One of us… One of us!