[Req] SFV lock

[darko]

LOCK (GOOD) SFV, like in projectzs for gl:

- user uploads sfv
- ioB does a few little checks to see if the sfv is correct
- if sfv is correct ioB 'locks' it (chmod)

- if sfv is incorrect (weird file names and such) -> rename to .bad

- when user tries to overwrite/resume sfv: tell him sfv is locked and good sfv has already been uploaded


this will fix a well known problem on io:
when you fxp sfv files from a linux env (gl) to io (windows) sfv files are sometimes RESUMED causing ****ups (this is cuz linux/windows use diff method to handle txt)

[Harm]

We all know that *nix and windows handle text files differently.
But that shouldn't have any influence on ioBanana since it handles both formats.
In fact, except when .sfv fails to transfer (and is 0byte), I've never seen any problem when transferring between glftpd and ioFTPD.

Can you give details about this kind of problems ? Examples would help.

[Zer0Racer]

??

[VFS]
..
Resume = *.sfv !*


Or turn off resume all together
Resume = * !*

[darko]

an other nice one would be grp/mp3 gerne bans in the zipscript
like

- iob_banned_groups = "P00PMP3, SHITDVDR"
- iob_mp3_not_allowed_genres = "Folk, Rock, RnB"

- user ups mp3 with Folk tag
- zipscripts reads the id3 1/2 tag (after upload)
- if in list -> delete (remove creds) - msg user: not allowed genre
if not in list -> allow

[darko]

Originally posted by Zer0Racer
??

[VFS]
..
Resume = *.sfv !*


Or turn off resume all together
Resume = * !*

ah yes thats an option too i guess, thnx


btw harm:

problem mainly accurs when 2 users, 1 fxp'ing from ioftpd site to my site and 1 fxp'ing from gl site, are fxp'ing the same release and both up sfv

[Harm]

This kind of check would only be done once the files are transferred and thus wouldn't save your bw.
Better solution: nuke non allowed genres and ppl will stop uploading them

[darko]

Originally posted by Harm
This kind of check would only be done once the files are transferred and thus wouldn't save your bw.
Better solution: nuke non allowed genres and ppl will stop uploading them

thats what i do now
...but its xtra work...


btw.. an other suggestion (im on a roll today!)

disallow mp3's > $size for example:

- max_allowed_mp3_size = 200mb
- user uploads big mp3 liveset from 300 mb
- ioB deletes and takes credits (or autonuke)

cuz some mp3 sites disallow livesets > 200mb for ex.
saves nukers work too