• feature request: ability to govern number of files downloadable per da

    From xbit ops@1:103/705 to GitLab issue in main/sbbs on Tue Jun 10 16:11:16 2025
    open https://gitlab.synchro.net/main/sbbs/-/issues/938

    Would like the ability to govern _number_ of files downloadable per day per security level and per directory.
    --- SBBSecho 3.27-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Jun 10 23:19:14 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/938#note_7341

    Can you elaborate on how you think this would work?

    And why it's better to limit the total number of files rather than total number of bytes downloaded?
    --- SBBSecho 3.27-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From xbit ops@1:103/705 to GitLab note in main/sbbs on Wed Jun 11 13:38:53 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/938#note_7344

    Yes sir... I don't just look at files by size for its importance. A very small file (say a txt file with the reg-code for yankee trader) could have much more value than a large door game that doesn't work.

    After re-reading my request i should state i'm not looking to replace downloaded bytes, just adding the option of DLPD (downloads per day) if the sysop wishes.
    --- SBBSecho 3.27-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Jun 11 14:10:32 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/938#note_7345

    So are you thinking of a new ARS keyword (e.g. "DLT" for "Downloads today") that a sysop could use in their directory "Download Requirements" strings? e.g. "DLT NOT 100" would allow download from that directory if the user had not yet downloaded 100 files today (not withstanding other download requirements like credits, etc.).

    You also said "per security level" in your request, so that would be something different than a "per directory" requirement like I outlined here.
    --- SBBSecho 3.27-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Jun 11 14:18:18 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/938#note_7346

    Also to clarify, when you say "per day" - you don't mean within the past 24 hours but rather since the previous midnight in the BBS's time zone, yes?
    --- SBBSecho 3.27-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From xbit ops@1:103/705 to GitLab note in main/sbbs on Wed Jun 11 16:14:32 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/938#note_7349

    Thinking this though it may be difficulty/confusing to place a d/l quota on both the directory/liberty level an security level.

    I think the best place for this would be Security Options > Security Level Values location. It seems to fit right into Time per day, Time per call, calls per day, etc. For example I may want to allow security level 50 20 downloads per day and level 60 50 downloads per day.

    And the "per day" would = the BBSes day. Each callers quota would reset at Midnight. Using the example above, a level 50 caller that downloads 20 files at 23:45 can call again at 00:05
    and download another 20.
    --- SBBSecho 3.27-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Jun 11 22:11:21 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/938#note_7351

    Let me know how that works for you.
    --- SBBSecho 3.27-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Thu Jun 12 19:57:38 2025
    https://gitlab.synchro.net/main/sbbs/-/issues/938#note_7369

    Okay, you're running git SHA C122DDD88, that's new enough: https://gitlab.synchro.net/main/sbbs/-/commits/master

    It should be working.
    --- SBBSecho 3.27-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Novedades:

Servidor de Quake 3 Arena Online! - Conectate a ferchobbs.ddns.net, puerto 27960 y vence con tu equipo!