Hmm, best would be if those kids find a real hobby so they stop bothering us. On the other hand, it helps us understand Lemmy better and secure it.

If it’s the same people, they’ll probably get tired of it and move on. But the more we talk about it, the more likely it is that new people want to get in on the “fun”. I’d say to not make memes about the downtime and pretty much act like it doesn’t exist (as users, obviously the admins should take action as necessary to mitigate it and post to be transparent).

This would probably be less useful than you think.

Firstly, changing the default doesn’t matter - the attackers will just switch to targeting whichever URL causes the most pain.

Secondly, in comparison to prerendered pages of live content, js files are incredibly cheap and easy to chuck on a CDN. They don’t change often, so you don’t need to worry about cache invalidation, and even at a server level they’re probably hosted by a simple file server rather than hitting the DB.

That doesn’t help with volumes of otherwise legit looking traffic right? The problem that Cloudflare and Akamai etc address is usually content that is otherwise static that can be cached. Say the front page of hot lemmy.world is updated every few minutes with the newest hot item. That page is otherwise distributed by the CDN so the CDN can just direct the traffic to access it, and no requests are made to lemmy.world.

nginx would be helpful for any attacks located from a single address trying to making large numbers of connections, but without reading more into the attack I can suspect that this isn’t what the attacker did.

Be aware that you use another server so you might consider donating to them instead.