Subj : Re: ANSI Art Packs
To   : Deon
From : AKAcastor
Date : Mon Apr 01 2024 02:23 pm

 d> What I can do is, generate a unique 8.3 name, where the 
 d> 8 will be a filearea_id+file_id value in hex (to 
 d> clrghouz), and the .3 will the extension chopped to 3 
 d> chars. eg: 0A0001F3.ZIP, and while the file area and 
 d> description are left intact, outside of your BBS you'll 
 d> have no idea what the file is.
....
 d> Determining the 8 from the original filename by chopping 
 d> it would be (IMHO) dangerous since the probability that 
 d> it clashes with another name would be high (the mystic 
 d> updates comes to mind, where there 8 chars is the same 
 d> for windows, linux, pi from memory).

 d> I also have a function that converts a date into 4 chars 
 d> with 4 year precision, so I could take the first 4 
 d> chars, and make up the last 4 with that function - it 
 d> might have some resemblence of a name, and be unique for 
 d> at least 4 years. eg blndr2023d.zip might become 
 d> blnd3F12.zip.

IMO the latter method you mention - keeping the first 4 chars of filename and a datestamp for the rest - is the most desirable so far.  I don't prefer the entire filename being random (or rather based on an encoded area/fileid), ideally the filenames could remain somewhat recognizable IMO.


Tempted to do 6 characters and ~1 and call it a day a la Microsoft. haha ;)


Chris/akacastor

--- Maximus 3.01
 * Origin: Another Millennium - Canada - another.tel (21:1/162)

.