1. Forum
  2. fsxNet
  3. BBS

  • file_id.diz - was IcyBoard 0.1.6 release

    From Mindsurfer@21:3/119 to paulie420 on Tue Oct 7 10:42:38 2025
    Re: Re: IcyBoard 0.1.6 release
    By: paulie420 to Omnibrain on Mon Oct 06 2025 18:35:07

    Hey - one last thing... can you please include FILE_ID.DIZ in your release .zips??? It helps when uploading to bbSes... I know, I know; but it would be nice.
    pAULIE42o

    I wish file_id.diz would be more widely accepted and used. Especially with scene releases or art packs, etc., how often is it not even a zip archive, making it impossible to add a file_id.diz in the first place, or if there is one, people get creative with it but don't include any information about the release.
    It's a real shame that file_id.diz is given so little attention.
    Oh, and when file_id.diz is actually used for information about the release, the standard height and width of 10x45 is definitely not adhered to (although I think a little more height would be okay).

    Mindsurfer
    --- SBBSecho 3.28-Linux
    * Origin: FuNToPiA BBS - telnet://funtopia.synchro.net:3023 (21:3/119)
  • From Omnibrain@21:2/150 to Mindsurfer on Tue Oct 7 02:55:32 2025
    I wish file_id.diz would be more widely accepted and used. Especially
    with scene releases or art packs, etc., how often is it not even a zip archive, making it impossible to add a file_id.diz in the first place,
    or if there is one, people get creative with it but don't include any information about the release.
    It's a real shame that file_id.diz is given so little attention.
    Oh, and when file_id.diz is actually used for information about the release, the standard height and width of 10x45 is definitely not
    adhered to (although I think a little more height would be okay).


    I agree with that - however let's think back how it was in the 90'.
    I was in a group (LiQUiD) when I made let's say a PPE I was not alone there were people which made GFX, DOCS etc. so in some way it was more professional back then. It's harder to pay attention to everything when you're alone - esp. if you're a slacker like me - haha.

    Today we sw devs just use github and the feature list is basically just the commits. But I agree that something could be improved there - I'll try to find a solution. Maybe a file_id.diz can be generated better.

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)
  • From phigan@21:3/195 to Mindsurfer on Tue Oct 7 14:09:43 2025
    release, the standard height and width of 10x45 is definitely not
    adhered to (although I think a little more height would be okay).

    Ugh, I hate when those things are more than like 4-5 lines!

    --- Mystic BBS v1.12 A48 (Raspberry Pi/32)
    * Origin: https://13leader.net (21:3/195)
  • From paulie420@21:2/150 to Mindsurfer on Tue Oct 7 18:27:20 2025
    I wish file_id.diz would be more widely accepted and used. Especially
    with scene releases or art packs, etc., how often is it not even a zip archive, making it impossible to add a file_id.diz in the first place,
    or if there is one, people get creative with it but don't include any information about the release.
    It's a real shame that file_id.diz is given so little attention.
    Oh, and when file_id.diz is actually used for information about the release, the standard height and width of 10x45 is definitely not
    adhered to (although I think a little more height would be okay).

    jACK pHLASH or xtqr did a nice Blog Post about the FILE_ID.DIZ format... I'll try to find the link - or if it was jP, I'm sure he could link it.

    It was a good read... wait; it MAY HAVE been the dev of ENiGMA.5 - someone did, tho.



    |07p|15AULIE|1142|07o
    |08.........

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)