Conversation
corbet

Jonathan Corbet

So @lwn is currently under the heaviest scraper attack seen yet. It is a DDOS attack involving tens of thousands of addresses, and that is affecting the responsiveness of the site, unfortunately.

There are many things I would like to do with my time. Defending LWN from AI shitheads is rather far from the top of that list. I *really* don't want to put obstacles between LWN and its readers, but it may come to that.

(Another grumpy day, sorry)
6
125
124
tmcfarlane@toot.community

Tristan Colgate-McFarlane

Reply to @corbet
Edited 4 hours ago

@corbet @lwn this, combined with search engines prioritising the stolen content!
This is why I think the web is genuinely doomed. It's not enough to steal the content, for search engines to kill click thtoughs and ad revenues, they are literally killing the ability of original authors to serve the traffic to the few real users that might want to see it.
Devastating.

0
0
0
allan_christoffersen@discuss.systems

Allan Christoffersen

Reply to @corbet

@corbet @lwn
As a avid longtime subscriber and reader, I can only give thanks and hope you will survive also this blast of willfully wrong behaviour. Thank you for your openness.

0
0
0
nirik@fosstodon.org

nirik fedora redhat

Reply to @corbet

@corbet @lwn Been there. ;(

0
0
0
foxylad@mastodon.nz

FoxyLad tinoflag

Reply to @corbet

@corbet @lwn Any inkling which AI (Arsehole Incorporated) it is? The crash can't come soon enough.

1
0
0
corbet

Jonathan Corbet

Reply to @foxylad@mastodon.nz
@foxylad @lwn There is no way to know who is after the data. The actual attack is likely perpetrated by Bright Data or one of its equally vile competitors.
0
1
1
sb@metroholografix.ca

sb arms & legs

Reply to @corbet

@corbet @lwn
Just speaking with my user hat on here, but given the circumstances I don't mind the ever-so-slight inconvenience of an challenge.

0
0
0
cadey@pony.social

Xe verified

Reply to @corbet

@corbet @lwn If you need help, email me. I can work with you in case there's low hanging fruit that you missed.

0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: