You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yesterday, I made a computer program that would download a playlist file and play it, but because of a bug in my program it started to load and play hundreds of musics in a matter of seconds. The problem was that I had the server with the music files, and I could only prevent my PC from crashing by manually unplugging the Ethernet cable. I did solve the problem, but the main concern was that I was alone on the server when the incident happened, and since the "playing music" part is client side, it could have been way worse than yesterday. Please fix this is a real threat. With a server with maybe 100 players on it, and 100 musics played in 5 seconds, it's equal to a whopping 2000, it's easy to see that any home computer would not be able to withstand the force of the DDoS. Of course closing the port would be easier, but some sort of "rate limit" would have been better.
The text was updated successfully, but these errors were encountered:
Yesterday, I made a computer program that would download a playlist file and play it, but because of a bug in my program it started to load and play hundreds of musics in a matter of seconds. The problem was that I had the server with the music files, and I could only prevent my PC from crashing by manually unplugging the Ethernet cable. I did solve the problem, but the main concern was that I was alone on the server when the incident happened, and since the "playing music" part is client side, it could have been way worse than yesterday. Please fix this is a real threat. With a server with maybe 100 players on it, and 100 musics played in 5 seconds, it's equal to a whopping 2000, it's easy to see that any home computer would not be able to withstand the force of the DDoS. Of course closing the port would be easier, but some sort of "rate limit" would have been better.
The text was updated successfully, but these errors were encountered: