

For me it was KitchenOwl. It’s shopping list works and looks similar to Bring, which we had used before and made the transition for my wife easier.
For me it was KitchenOwl. It’s shopping list works and looks similar to Bring, which we had used before and made the transition for my wife easier.
If you don’t plan on supporting this for at least a few years I would say no.
If you don’t expect to have a decent local userbase I would say no (local in the sense of a common interest, e.g. it might be useful to host an instance for all members of even a small company if you expect a decent amount of posts).
If it’s just you and your family (let’s be honest: it’s just you) I would say no.
The fediverse can federate, but if everyone is using their own server it’s just a fancy peer to peer network.
I also think it may be the browser not using the DNS provided by the router. This is often called Safe Browsing or Secure DNS in browser settings.
While almost everyone here seems to hate AI (maybe for the wrong reason, but who am I to judge) I like to have AI as it is able to provide answers a simple search engine cannot.
What I don’t see is hosting something like this myself. The managing of source and indexing them would take too much of my, my server’s and the web servers to be indexed energy (maybe I am wrong).
There are already good solutions (OpenWebUI with Ollama) that can be tweaked to almost do what you’re describing and the AI models get better every month, so I don’t think a custom AI search engine could keep up with it.
For a general guide on how to make ssh more secure I stick to https://www.sshaudit.com/
You can check your config and they also provide step by step guides for several distros…
I use INWX (based in Germany). Prices are consistently low (not always the cheapest, but fair). The web UI is a bit rusty, but it works perfectly and you can manage everything there.
That show is equal parts content and advertising. That is a bit too much for me…
That’s the way to do it. The problem is that the request originates from the browser of you website visitor. You need to open a path for them to you media server. Nginx and it’s reverse proxy functionality is exactly what you need for that.
I think what he means is that if your backup is triggered from your main server and your main server is compromised the backups can also be attacked immediately. If the backup is requested from the backup machine you will at least have the time between the attack and the next backup to prevent the attack from reaching your backup machines.