Oh, more meetings will fix it! /s
TechnologyClassroom
Defederating or suspending will prevent your instance from seeing the content of another instance. Blocking the IP addresses associated with the domain will prevent the other instance from seeing your content by normal means. Meta could spin up a secret instance to spy on the fediverse (and probably already does this) which is impossible to stop, but this act is a means of protest.
If you run an instance connected to the fediverse, use a firewall to block the threads.net domain.
There are many ways to run code at startup. cronjobs and systemd are common ways to handle this. I have also had things start automatically with my desktop environment which comes later in the boot process.
Tax dollars should not be against the interests of those that pay taxes.
DD might be using something like that. I have heard they block TOR as well. I have used a VPN with ports 80 and 443 on their WiFi years ago.
Deep packet inspection is unlikely the culprit in my experience. SSH and SFTP use port 22 by default which is probably blocked. I log in to my work VPN through common ports 80 and 443 on public WiFi.
You could also have your back end pull from a git repo every minute. A cron job could check a GitLab repo for changes and update the site if any changes are found.
That is a networking issue which is not specific to Hugo. You need to solve this as most of the suggestions also involve SSH.
One way is to use a VPN like openvpn or wireguard that can use a common port like 80 or 443.
What do you find limited about Hugo?
The ability to edit titles seems like an obvious feature that Reddit never added.
I 100% agree that any interaction with the fediverse is public and this does not stop Meta from creating a minimal instance under a different domain which they probably already do. This act is one of protest.