logological

This is hardly unprecedented -- in fact, it looks like the US government has learned a thing or two from the anti-spam community. If you actually want to block e-mail or newsgroup spam at its source, you don't complain to the spammer themselves, but rather to their mail/news provider, and if that doesn't work, you escalate the issue to the upstream provider, the hosting company for the spammer's website, the registrar for the spammer's domain names, and so on. This is time-consuming but is sometimes effective. (Of course, dedicated spammers may then switch providers, or start employing distributed botnets of zombified residential devices, but knocking out their infrastructure at least temporarily does disrupt their operations for a time and drives up their cost of business to the point where they may reduce or even cease their activity.)

> I don't think they are?

If filling out the source code request form via Google Forms and/or accessing the download link via Google Drive requires the requester to run non-free (or at least non-GPLv2) JavaScript, then maybe it is in violation of section 6 of the GPLv2 ("You may not impose any further restrictions on the recipients' exercise of the rights granted herein") since the requester is then required to accept an entirely different set of licensing terms and conditions.

Yeah, there don't seem to be any settings by those names in the web version. Or maybe their presence depends not on whether you're using the web vs. mobile client, but rather where you're connecting from geographically. That is, maybe Meta exposes these settings only when necessary to comply with laws or court orders in certain jurisdictions.

Where, exactly? I browsed through the account settings and didn't see anything obviously relevant. (Could be that whatever option you're talking about is available only to mobile users, whereas I only ever visit Instagram on a desktop.)

> We complied with standard responsible disclosure procedure throughout this work. We initiated responsible disclosure with GNU and Git on Jan 16th 2026…

Why would the author have disclosed the issue to GNU? As far as I know, they don't have anything to do with the development of Git. Perhaps it's because they run a Git server for their Savannah forge, but then again, so does pretty much every other forge out there, most of which are far more widely used.

Doesn't work for me. The file scraper crashes with the default Firefox Selenium driver, and with the Chrome driver it immediately quits, falsely reporting that it successfully downloaded all the files.

Does that script even work for you? When I run it, I'm prompted for my Yahoo! password, but after typing it in the program just spits out a "Login failed" message. The problem has been reported on the issue tracker but there's been no activity on it since February.