You can always look to implement webtorrent. It does not work everywhere, but it works very well.
Basically how it works it's that you have a streemable file, you make a torrent, and a javascript client on the browser it's capable of downloading and streaming it.
Good choice : Install ifupdown or whatever. YAML it's a terrible file to edit by commandline.
Bad choice : use chatgpt to generate your network configuration
The vault local copy stays around. You can export and import it back.
Man I'm a fucking moron.
"Legally blind, what an odd way to describe not caring about law and piracy"
The documentation it's surprisingly bad at explaining common patterns of use.
It is also a bit thicker compared to nginx or HAproxy.
This IP it's failing rDNS, the PTR address of that IP points to the domain name srv-185-36-81-40.serveroffer.net , but not the other way around. This alone does not invalidate a connection but should raise it's spam threshold.
It has issued an authentication attempt, and after failing it has quit the connection.
If the people at serveroffer.lt do not sound familiar to you, it's probably an automated attack.
https://ipinfo.io/AS209605/185.36.81.0/24
The most basic thing you should have in place it's a brute force protector, like fail2ban, or netfilter. Crowsec it's nice too. Otherwise you are going to get hosed.
For basic duplicates, I find rmlint to be a superior alternative.
No no, you keep the ones you have and you buy 8 24 ones.