admin b8672a44d0 feat(worker): forward on allowsForwarding channels regardless of file type or listing success ...

tryForwardArchiveSet only attempted the no-download forward path for
ZIP/RAR/7z archives, and bailed to download+reupload whenever the
ranged listing failed — even though the channel already grants
forwarding permission and forwarding a message costs nothing
regardless of what's inside it. Standalone DOCUMENT/STL/3MF
attachments never got a chance at the forward path at all.

Now any file on a forwarding-enabled channel is forwarded directly;
when there's no listing to derive a content hash from (non-archive
types, or ranged-listing failures), dedup falls back to
remote.unique_id identity — deriveForwardContentHash, crcFingerprint,
and compareFingerprints already degrade to this safely for
empty/incomplete entries, so there's no risk of unrelated files
colliding as false duplicates. Inner-file indexing is simply skipped
for these cases, matching the existing accepted limitation for
RAR/7z rebuild placeholders.

2026-08-13 18:52:34 +02:00

..

src

feat(worker): forward on allowsForwarding channels regardless of file type or listing success

2026-08-13 18:52:34 +02:00

Dockerfile

feat: add preview management, channel controls, invite polish, and recovery

2026-03-22 00:09:59 +01:00

package-lock.json

test(worker): add vitest harness

2026-07-23 11:18:57 +02:00

package.json

test(worker): add vitest harness

2026-07-23 11:18:57 +02:00

tsconfig.json

feat: add Telegram integration with forum topic support and creator tracking

2026-02-24 16:02:06 +01:00

vitest.config.ts

test(worker): add vitest harness

2026-07-23 11:18:57 +02:00