That’s hilarious. I’m guessing its a result of an auto-redacter which is set to redacts urls or something? since the original would be
--enable-largefile
Enable support forlarge files (http://www.sas.com/standards/large_
file/x_open.20Mar96.html) if the operating system requires special compiler
options to build programs which can access large files. This is enabled bydefault, if the operating system provides large file support.
I can’t see any obvious keywords there, it would be very telling to be able to determine what theye filtering on, if we had enough unredacted/redacted pairs to find out
That’s hilarious. I’m guessing its a result of an auto-redacter which is set to redacts urls or something? since the original would be
--enable-largefile Enable support for large files (http://www.sas.com/standards/large_ file/x_open.20Mar96.html) if the operating system requires special compiler options to build programs which can access large files. This is enabled by default, if the operating system provides large file support.Large files huh? “Large” like “4k videos of blackmail material” large or what are we talking here?
Fedora just runs my large 4k videos of totally not pirated movies just fine, I’ve never had a file too large to access.
I can’t see any obvious keywords there, it would be very telling to be able to determine what theye filtering on, if we had enough unredacted/redacted pairs to find out
there is another URL at the end of the document without redaction.
yea I’m not sure, maybe something to do with the term SAS but yea not enough unredacted stuff to really know.