Monkey, please explain a rule

"Also no containers of any form, it makes it so MODs can't verify that the material is allowed here."

Please explain what a "container" is.
Thank you.

I hope you don't mind me replying.

The new addition to the rules, refers to CCF, RSDF and DLC files, or similar files which require external software or decrypter in order to be used.

humlan

Nothing to add.

You see containers very often in conjunction with certain link protectors, which aren't allowed for exactly this reason:

eg. linksave:



Monkey D. Ruffy

I'm confused.

I personally can't stand those container files, and have never DL-ed a single one because I resent someone trying to make me install software to access their content.

But I'm confused about the rationale for the rule as stated. How does a container prevent mods from looking at what has been posted?

Can't you just use the software to open the container file and get the same links and DL the files just like with any other posted link? It's an extra step that I don't want to take myself, but how exactly are mods prevented from "verify[ing] that the material is allowed here"?

Am I missing something about these container files? As I said, I have never used them, but I thought they were simply a fancy kind of link encryption that required decoding software, after which the links to the files are just regular links on the same old filehosters.

billyellis wrote:

The same as you said.

Not every mod wants to install software.

I use jdownloader and I've dld. lots of container files, but not everybody wants to.

It's too much time consuming for the staff, because you have to download the complete material and check it afterwards.

Container can be very useful, but would cause trouble for the staff.

Therefore not allowed.

Monkey D. Ruffy

Got it. I didn't know if there was something feature of the container files that I didn't know about.