Redundancy and marginal ddos protection for starters, I guess if it's hobby-level it's not as important that there's as much uptime as possible but a slightly more distributed architecture is easy enough to setup and maintain. For security purposes it's much better not to expose your servers directly to the internet like this and rather stick them in a private subnet with a load balancer in front of it.
You wouldn't make outgoing requests from your load balancer though, and a request from their image previewer to comrade furry's server is how they discovered the ip in the first place
Kinda weird that it's only on one server
Why? Webservers/apps aren't that demanding.
Redundancy and marginal ddos protection for starters, I guess if it's hobby-level it's not as important that there's as much uptime as possible but a slightly more distributed architecture is easy enough to setup and maintain. For security purposes it's much better not to expose your servers directly to the internet like this and rather stick them in a private subnet with a load balancer in front of it.
The one time I visited that stupid site it had a cloud flare DDOS protection thing, so they took some defensive measure at the very least.
Yeah, that likely sits between the domain and the server, but that doesn't stop anyone from flooding that listed IP directly
Ah. Makes sense.
Could be a load balancer or something. Given that site’s horrible performance the couple times I checked it out, it might just be one server though.
You wouldn't make outgoing requests from your load balancer though, and a request from their image previewer to comrade furry's server is how they discovered the ip in the first place