benmxrt

Thanks for reporting this! The issue was caused by the email HTML content not being properly normalized before rendering - some emails from services like emailprivacytester.com return complex nested structures that triggered a React rendering error. I've pushed a fix that safely handles all edge cases (non-string HTML arrays, nested objects in header fields, etc.). Should be live shortly. Really appreciate you testing with edge cases like this!

Just pushed a hotfix for this. It was a missing headers issue blocking the WASM workers. The black screen issue should also be resolved now. Thanks for the heads up!

OP here.

I built this because I was frustrated with existing file tools requiring uploads for simple tasks like merging PDFs or converting a video.

FileZen is a 100% client-side tool built with React and WebAssembly.

Tech Stack: - ffmpeg.wasm for video/audio processing (running in Web Workers to avoid blocking UI). - pdf-lib for document manipulation. - Vite + React for the frontend.

The main challenge was handling memory limits in the browser (especially specifically on iOS Safari) when processing larger video files.

It's currently an MVP and completely free. I'd love to hear your thoughts on the WASM performance and if you encounter any crashes on mobile devices.

guilty as charged lol i tried way too hard to sound like a professional dev and ended up sounding like a bot... guess that backfired. im honestly just a solo dev who is totally overwhelmed by everyone watching my every move right now. lesson learned: less polish, more me. thanks for the reality check

guilty of using ai studio for the fast prototype lol but the 145 users today caught me off guard... im working on a clean production build right now to move away from the google cdn stuff. just trying to build a better ui for these apis without all the bloat and tracking! thanks for the heads up

thanks for the links sixtyj. the cat and mouse game with these lists is never ending... i agree that the ethical use cases like whistleblowing are why these tools need to exist. its a tough balance to keep them accessible but not abused.

nah its just me lol english isnt my native language so i tried way too hard to sound professional and clear... guess i overdid it and sounded like a bot. im just super nervous with 145 users right now my heart is still racing trying to keep up

You hit the nail on the head. From an SMTP perspective, 'replying' is functionally identical to 'sending,' which is why most disposable mail services are strictly receive-only.

The moment you allow outbound traffic, you risk being weaponized as an open relay for spam. To implement a safe 'Reply-Only' feature, Mephisto would need a sophisticated validation layer that cryptographically links the outbound reply to a specific, recently received message ID. Even then, rate-limiting would have to be extremely aggressive. For now, staying receive-only is a deliberate choice to protect the service's reputation and ensure 100% uptime.