I notice that few hours ago access to lwn timed out.
My user agent is: "Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0"
@corbet @lwn Not scraping as much as opening the weekly issue every week and saving it to a file with a Firefox extension (Save Page WE), and then putting that in a Git repository.
I admit I went back through the archives to backfill my collection.
Why? I wanted to count how many times you've quote me. I'm that vain.
@corbet getting a 403 with iPad:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.2 Safari/605.1.15
@corbet @lwn I typically read LWN through my RSS feed (love that LWN provides this service, btw, thank you!). Looks like the user agent is: “Mozilla/5.0 (compatible; Miniflux/2.2.16; +https://miniflux.app)”. Dug this up in the miniflux source code on GitHub. The “2.2.16” string may change depending on the miniflux version. Haven’t had any issues accessing content myself, but providing this info in case it helps others. Sorry about all the scraper attacks :(
@corbet @lwn I read lwn from time to time at work, and when I got blocked yesterday, I wondered whether people at our company were reading lwn so enthusiastically that we were getting blocked... .This notion was strengthened by the fact that many of us could access it from our home internet providers.
I was saddened to hear that the situation was even worse...
I can only quote https://scicomm.xyz/@ianrosewrites/110373559167883196 again... "Right now, there's no AI. There's just someone else's work."