Come on Dave sort yourself out.

You know this is a porn site then! 😂

How’d they know it was a he

Here it is:

https://github.com/meetrevision/playbook

Well thankfully it’s an open source playbook now and not an ISO anymore. Plus it’s got a decent discord server to chat about it

I quite like 11 after it’s had a good going over with Revision!

I use it on my VMs, my bootcamp and my main gaming pc.

You download the AME tool, load in the Revi playbook and press go. Just need to disable AV for it to do its magic.

I love to extol the virtues of ReviOS. You’ll never have to worry about windows doing things ever again as it rips the guts out of windows. Seriously check it out.

It’s real easy to install.

Also what Linux and theme are you running there?

I loved that phone. I had the red version. Front facing speakers was fantastic!

Saw the same thing on Guinness in Aldi. Must be some automatic printer or something. Surely no sane person would make it!

Have you tried moving it an inch to the left?

😅 I kid.

You can buy a vesa stand mount though fairly cheap.

Sony currently do a cool thing with their stands where you can place them in 3 or so different position along the tv if you wanted. Finally someone thinking!

Finally someone talking sense.

Well yes of course but the API route should be guarded still both internally and externally. If it’s like a fetch all post with certain filters and parameters then it being run over and over over the space of a few seconds by thousands of requests then that takes up execution time on the database. Identifying that is easy as is preventing it. Rate limiting and banning undesirable requests. No normal user will be executing grandiose requests multiple times a second. That’s what constitutes a denial of service.

Anyway, you do you.

Then surely those routes can be protected with various methods such as CrowdSec? And help mitigate overwhelming the endpoints slow process time. Especially if the attacks come from known IPs. Or at least repeat offenders (x requests in 1s from an IP for example) can get blocked straight away.

I found a lot of crawlers were using HTTP1.1 traffic so I just blanket denied anything that wasn’t HTTP2 at the lowest level. Certainly helped that small menace!

There has to be away to stop the pricks

Are bad actors able to access the database to execute queries or is it through the main front end site and accessing API endpoints over and over? Then surely they can be blocked at this point?

Are you guys using a load balancer at all? How about a tool like CrowdSec?

I use that and the nginx Bad Bot Blocker to stop malicious shits on the sites I operate (medium-large e-commerce) to great success. We used to get scraped heavily by competitors but now they get the middle finger.

I presume you have fail2ban too?