@lucy@Njord@eniko >no shit but like what genuinely good (affordable) laptop brands are even around these days?
None for the consumer market. At least when buying new.
If you want a mostly affordable laptop that won't probably develop a keyboard/stability issue in two years, decommissioned business laptops that have been refurbished are the way. Business laptops are at least mostly repairable unlike consumer trash.
@mischievoustomato@p@nyanide@ins0mniak This aren't for Fedi scrapers. These are IPs that kept hammering my Gitea instance until it almost died. One day I literally woke up with 20 alerts in my inbox because of these retards.
@sun@feld Makes sense, I've been hit by a lot of scraping in the last month to the point that I nullroute a lot of /16s and some /8s just to cope with the load.
@sun@feld Unironically just drop AWS into the nullroute bucket if you don't need it. Same with Alibaba LLC and Huawei Cloud. Nothing of value is hosted there (at least for a Fedi server) and it's most of the traffic.
@nyanide@p@ins0mniak I'll send them when I'm done with other stuff (couple hours).
When in doubt bgp.he.net is your friend. Throw one of the annoying IPs into search->click on AS number->Prefixes vX and enjoy all the nullroutable prefixes.
I ended up just killing off their IPs, but because I also had to wipe the logs (media.fse ran out of space on /var) I can't check if they did.
With Claude it's at least easy. Return 403 to the UA and you are done. Which btw still does not stop their attempts at scraping. They will continue to hit webserver even when they obviously aren't let through. From there a log monitor will do the job.
With the Chink scrapers, it's a bit harder than automated log monitoring. They are clever in a way, where they will not send you more than approx. 3 requests from one IP, meaning that the typical monitoring tools like fail2ban or something custom won't work as all of the ones I know of don't do subnet/ASN detection, or it will be very trigger-happy.
Thankfully they are retarded in other ways which make them stick out like a sore thumb in the logs. Currently I just look at the logs every few days unless they trigger alerts and throw the whole announced prefix into the trash. So far that has worked out great.
@p@ins0mniak >I was not going to open up port 445 and they were sending so many connection attempts that the majority of the bandwidth was those fuckers. I had an angry moment over Chinese scrapers two weeks ago after I promptly nullrouted half of Huawei Cloud 2 weeks before that. They thought it would be great to switch to Alibaba US and hammer my Gitea instance with requests for every file in most repos and asking for every revision of those files. And in typical Chink when they didn't receive a response in time (obvious when you are sending ~15r/s to a small server), they just closed the connection and tried again in 30 minutes while still scraping other files.
And they have the audacity to use normal browser UAs from a randomized selection of a few making them very hard to block in an easy. Claude on the other hand completely ignores the meta tag and robots.txt, but at least they have "ClaudeBot" in the UA making them trivially blockable in nginx. That said, Claude is also retarded in a different way. They send requests for issues with numbers in the thousands and never stop when literally all of them return a 404.
Seniors in dev are worried that new graduates will take their job with AI, but the reality is that even "developers" with a degree barely know how to operate a computer. In-house helpdesk and hardware administration will probably be a goldmine in a decade.
@meso Curiosity. Everything I know about computers and related subjects is self taught. The math behind it usually isn't that advanced as computers also can't calculate advanced math quickly enough. And most of it can be understood in an abstract way where you take the properties of the used math at face value while still understanding how the whole algorithm works. The very advanced part usually is the proof of why it works.