Is this rage bait of tech bro bait?

in the context of the comment you referenced:

Definitely have the server on its own VLAN. It shouldn’t have any access to other devices that are not related to the services and I would also add some sort of security software.

If you have a public service that you expect to have multiple users on you definitely should have some level of monitoring whether it is just the application logs from the forum that you want to host or further have some sort of EDR on the server.

Things I would do if I was hosting a public forum:

• Reverse proxy
• fail2ban
• dedicated server that does not have any personal data or other services that are sensitive
• complete network isolation with VLAN
• send application logs to ELK
• clamAV

And if the user base grows I would also add:

• EDR such as velociraptor
• an external firewall / ips
• possibly move from docker to VM for further isolation (not likely)

Just tailscale really.

My services are only exposed to the tailscale network, so I don’t have to worry about otger devices on my LAN.

A good VPN with MFA is all you really need if you are the only user.

If for example the server is actually a computer in the LAN and maybe it’s also his media server and his backup server then potentially any compromise could lead to his personal information leaked and or other computers in the LAN compromised.

So what could actually happen? His personal photos and passwords and accounts can be leaked or taken over. He could be spied on by accessing his webcam. A lot of things could go wrong.

You are right. Learning by doing is awesome. Just be sure to do it in a safe way. Get a VPC. Do it there. No personal information, no access to other services. Just this service, just for this purpose. Worst case scenario, if it’s taken over, the only thing that’s harmed is the forum itself. Which is not the end of the world, I’m guessing.

Especially if this is from a computer that has access/information beyond just the public service.

Don’t do it.

Hosting a public service with no real knowledge of security can only end badly.

Get a vpc, do it there, learn from mistakes.

It’s more than just HTTPS, you also need proper authentication, regular updates, emergency updates for critical vulnerabilities, ideally some sort of monitoring to detect potential misuse of the service or any escalations from the service to the OS.

Ask yourself this: If this was your first time driving a car, would you rather do it in an empty parking lot where at worst you will damage the car. Or would you rather do it in a busy street where at worst you can kill someone?

I suggest skipping the devops part and instead starting with a course. If you go with setting it up you will probably spend 95% of the time doing devops and not security (which is usually the client of the devops team that maintains the SIEM)

IP based blocking is complicated once you are big enough or providing service to users is critical.

For example, if you are providing some critical service such as health care, you cannot have a situation where a user cannot access health care info without hard proof that they are causing an issue and that you did your best to not block the user.

Let’s say you have a household of 5 people with 20 devices in the LAN, one can be infected and running some bot, you do not want to block 5 people and 20 devices.

Another example, double NAT, you could have literally hundreds or even thousands of people behind one IP.

You can try this https://www.iwf.org.uk/en/uk-report/

I would suggest doing it with the tor browser as to not be associated with it in any way.

Sadly without the actual content and giving your server away for forensics, this might not go anywhere. But! It can help build a case, especially if any of the pii (ip, username, etc) you provide is already being investigated.

Lit af

Wifi works great on every distro I tried

In my experience, a stable beginner friendly distro such as mint, is 10x closer to “just working” but…

I do think that the windos DE tends to be more reliable than any linux DE I have tested. The only DE that compares is gnome, which I find very very stable (but I hate it)

I think that non-technical people are just used to a simple playbook of:

1. GUI is rarely the issue, so you never need to see the terminal.
2. If there is an issue, restart
3. If that didn’t work, ask for help from your local techy

And for linux step 3 usually doesn’t work because your local techy is probably someone who just knows how to google and paste into cmd.

64gb phone in 2025 that costs 1000$ feels like those pictures of 1000$ rent “apartments” in new york that are just the right size to fit a bed and a toilet in.