pdfmergely

30 ms·

1.
by pdfmergely 3mo ago
I appreciate the directness, and you are right. The design has not yet earned trust, and that is on where I am working in. For a tool people hand documents to, looking trustworthy and being trustworthy need to line up. Thank you for saying
2.
by pdfmergely 3mo ago
Ofc not the only one, and the expectation is reasonable. A repo is coming, and for a tool like this it arguably should have been there from the start. Thank you for the nudge.
3.
by pdfmergely 3mo ago
A fair question. There is no from scratch PDF engine here. It is @cantoo/pdf-lib, a maintained fork of pdf-lib, running client side in a Web Worker, with WebAssembly handling the heavier parts such as encryption. I am happy to go deepe
4.
by pdfmergely 3mo ago
Point well taken. I appreciate it. It is being worked on .
5.
by pdfmergely 3mo ago
Thank you
6.
by pdfmergely 3mo ago
Our merge is page-level, not form-aware. We copy the pages (including the visual appearance of form fields), but we don't merge the PDFs' AcroForm dictionaries. As a result, form fields typically aren't fillable after merging
7.
by pdfmergely 3mo ago
A good point . open the Network tab" isn't a real answer for most people, and "trust me" isn't either. Two things that don't depend on either: (1) the offline test is something anyone can do ,load the page, tu
8.
by pdfmergely 3mo ago
Fair point, I'll add an About/Contact page with who's behind it. It's a small solo project; there's no company entity yet, but also no account or server, so nothing of yours is collected — files are processed in you
9.
by pdfmergely 3mo ago
Author here. Quick note on how the "no upload" claim actually works, since it deserves scrutiny. There's no upload endpoint to send files to. When you pick a file, the browser hands the app the bytes directly; the work runs i
10.
Show HN: PDFMergely – In-browser PDF tools that never upload your files(pdfmergely.com)
18 points by pdfmergely 3mo ago|24 comments