I’m confused - they confirmed 6 deaths, but did not know how or where they occurred…. So are the deaths even related to the fire?

What kind of patch cables are you using here?

If you go to your profile, there is a setting to turn it private; after that you should have an option on your posts to keep them private or public

I wish there was a simpler way to keep PixelFed private; I get that there is a lot of focus on the fediverse, but this can also serve as a private image/video sharing platform for close friends and family.

Being public by default creates a blocker for the average person joining it.

Never understood homes that pave/block out all the greenery; makes the home depressing af all for saving some 30min of upkeep per week.

I would suggest signing up for a free Cloudflare account and setting up any DNS for your Pi through there, using the Cache feature.

Once that is done, setup an automated script that will pull down Cloudflare IPs into a file (you can use a cronjob to run this daily):

#!/bin/bash

set -e

cf_ips() {
  echo "# https://www.cloudflare.com/ips"

  for type in v4 v6; do
    echo "# IP$type"
    curl -sL "https://www.cloudflare.com/ips-$type/" | sed "s|^|allow |g" | sed "s|\$|;|g"
    echo
  done

  echo "# Generated at $(LC_ALL=C date)"
}

cf_ips > allow-cloudflare.conf
(cf_ips && echo "deny all; # deny all remaining ips") > allow-cloudflare-only.conf

Then in your web server config to only accept connections from Cloudflare IPs:

server {
	listen 80 default_server;
	listen [::]:80 default_server;
	server_name example.com;
        root /var/www/html;

	include /etc/nginx/allow-cloudflare-only.conf;
}

I prefer this method over UFW/iptables block as it allows you to control the IP block per web config, so if needed, you can make exceptions by not adding the include /etc/nginx/allow-cloudflare-only.conf; into that specific site’s conf file.

Who he is, is pretty simple: a puppet dictator that only remains in power because of Putin. ¯_(ツ)_/¯

What a great time to get off Reddit