It's not a single file unless it's tar'd or compressed or whatever. It's completely normal to distribute software projects as some form of archive. This is doubly true for a "leak" like this where you want the single file to spread around.
I agree that it would be nice to have it browsable online, like in a github repo or whatever, but that's a separate issue.
> It's completely normal to distribute software projects as some form of archive
Again, I think you're missing my point
>> normalizing a requirement to download files that can issue exploits -- when there are easy alternatives that make this unnecessary -- just helps create the exact type of environment that scammers thrive in
Yes, it is "normal" and that is exactly the problem.
Ask yourself this
Is there a reasonable alternative?
Is downloading necessary?
I think you'll find that the answer to both is unambiguously "no." I think you'll also recognize that having the readable source __also__ unambiguously creates higher utility.
So you don't need to explain to me that this stuff is normal because I already understand that (and am actively demonstrating a knowledge of this). I realize communication isn't always obvious, but if someone is telling you that you're missing the point of what they're saying, please consider that you might actually be missing the point rather than doubling down. Even if you aren't, someone telling you that indicates that somewhere there's a miscommunication, and that needs to be resolved.
I would prefer that it is distributed as a zip. It allows me to easily get the entire file, and hash it to make sure it's the same file as other people are getting, and have an archive of it.
I would also like to be able to browse it online, but this is a usability issue for strictly when I'm intending to read it in a browser alone.
As to your final paragraphs referring to communication and me "explainig to you that this stuff is normal", you specifically said that "We don't want to normalize unnecessary behavior" which implies that you do not think it is already normalized. You're also implying that I should have altered my interpretation of your words when you said that I was missing your point, even though you didn't say I was missing your point until the same reply.
In any case, I think I understand your POV regarding archives, and I disagree.
> I would prefer that it is distributed as a zip. It allows me to easily get the entire file, and hash it to make sure it's the same file as other people are getting, and have an archive of it.
I mean hosting it on any GitHub alternative makes this possible too. We also get better archival because when things change, we can see. Considering this says "Part 1" I expect things to change. History tracking is better for archival.
> you specifically said that "We don't want to normalize unnecessary behavior" which implies that you do not think it is already normalized.
That's not accurate. Here's a counter example "We don't want to normalize clickbait headlines." Clickbait headlines are already normalized, that does not mean we want them to be nor does it mean we should accept them and not fight against them. I'm sure you can find many other similar examples.
I agree that it would be nice to have it browsable online, like in a github repo or whatever, but that's a separate issue.