Hi DM,

Wondering about how files are considered "new" to the system. I like to see when something new has been uploaded, and usually see that when I grab a QWK packet which includes notifications of new uploads. What I'd like to see a change in is usually an issue with FTN file echos, where a file is uploaded with a name that has been uploaded before. A common one is something like INFOPACK.ZIP which may come in weekly from an FTN distribution echo. Since it's the same filename as before, it doesn't get recognized as a new file when added to the file base by the TIC processor (TickIT). It always keeps the originally uploaded date, instead of the new file date. Here's a screenshot which shows the issue pretty well:

https://imgur.com/a/Y15Cypc


Is there a way to use the "File Date" instead of the originally "Uploaded" date in the logic to detect a new file? I can put in a git feature request if you'd like, but thought I'd just ask here first to see if it's possible. Thank you.

---
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

Re: "New" File logic
By: Gamgee to Digital Man on Sat May 17 2025 08:46 pm

> Hi DM,
>
> Wondering about how files are considered "new" to the system. I like to see
> when something new has been uploaded, and usually see that when I grab a QWK
> packet which includes notifications of new uploads. What I'd like to see a
> change in is usually an issue with FTN file echos, where a file is uploaded
> with a name that has been uploaded before. A common one is something like
> INFOPACK.ZIP which may come in weekly from an FTN distribution echo. Since
> it's the same filename as before, it doesn't get recognized as a new file
> when added to the file base by the TIC processor (TickIT). It always keeps
> the originally uploaded date, instead of the new file date. Here's a
> screenshot which shows the issue pretty well:
>
> https://imgur.com/a/Y15Cypc

>
> Is there a way to use the "File Date" instead of the originally "Uploaded"
> date in the logic to detect a new file? I can put in a git feature request
> if you'd like, but thought I'd just ask here first to see if it's possible.

Yes, it's possible (e.g. TickIt.js could use the FileBase.update() instead of the FileBase.add() method in this case) and yes, a gitlib feature request/issue would be helpful.
--
digital man (rob)

Sling Blade quote #9:
Doyle Hargraves: Morris here is a modern-day poet, kinda like in olden times.
Norco, CA WX: 56.2øF, 82.0% humidity, 3 mph SSW wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

-=> Digital Man wrote to Gamgee <=-

> Wondering about how files are considered "new" to the system. I like to see
> when something new has been uploaded, and usually see that when I grab a QWK
> packet which includes notifications of new uploads. What I'd like to see a
> change in is usually an issue with FTN file echos, where a file is uploaded
> with a name that has been uploaded before. A common one is something like
> INFOPACK.ZIP which may come in weekly from an FTN distribution echo. Since
> it's the same filename as before, it doesn't get recognized as a new file
> when added to the file base by the TIC processor (TickIT). It always keeps
> the originally uploaded date, instead of the new file date. Here's a
> screenshot which shows the issue pretty well:
>
> https://imgur.com/a/Y15Cypc

>
> Is there a way to use the "File Date" instead of the originally "Uploaded"
> date in the logic to detect a new file? I can put in a git feature request
> if you'd like, but thought I'd just ask here first to see if it's possible.

DM> Yes, it's possible (e.g. TickIt.js could use the FileBase.update()
DM> instead of the FileBase.add() method in this case) and yes, a gitlib
DM> feature request/issue would be helpful.

Will do, thank you.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL