maniazi83

3 ms·

1. 1.▲
   by maniazi83 7mo ago

   One thing we noticed while building OCR is that accuracy drops heavily with low-resolution scans and rotated documents. GPU acceleration helped speed, but preprocessing ended up being the bigger challenge. Curious how others handle that.
2. 2.▲
   GPU-Accelerated OCR API for Documents, Images and PDFs(docpose.cloud)

   2 points by maniazi83 7mo ago|1 comments
3. 3.▲
   by maniazi83 7mo ago

   This is seriously impressive. Emulating x86 + stubbing enough Win32 APIs in the browser is not trivial. How are you handling system calls that expect filesystem or registry access? Are those fully stubbed/mocked, or mapped to some in-b
4. 4.▲
   by maniazi83 7mo ago

   One thing we intentionally avoided was long-term storage. Many file tools quietly retain inputs longer than users expect. Our default model is: Source deleted immediately after processing Converted output expires after 24h Logs retained up
5. 5.▲
   by maniazi83 7mo ago

   Extra context: the goal was to be concrete (data lifecycle, retention, logs) rather than generic “we take security seriously” language. If there’s any security review question you’d expect answered on this page (sandboxing detail, threat mo
6. 6.▲
   Show HN: Cloud file conversion security model (S3-only, 24h retention)(docpose.cloud)

   2 points by maniazi83 7mo ago|2 comments