benmxrt

7 ms·

1.
Show HN: MephistoVault – Zero-storage P2P file transfer via WebRTC(mephistoshares.online)
1 points by benmxrt 7mo ago|0 comments
2.
by benmxrt 7mo ago
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 renderi
3.
Show HN: MephistoMail – A RAM-only, tracker-free disposable email client
4 points by benmxrt 7mo ago|2 comments
4.
Show HN: MephistoMail – A RAM-only, tracker-free disposable email client(mephistomail.site)
4 points by benmxrt 7mo ago|0 comments
5.
by benmxrt 9mo ago
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!
6.
by benmxrt 9mo ago
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.wa
7.
Show HN: FileZen – Client-side PDF and Video tools using WebAssembly(filezen.online)
2 points by benmxrt 9mo ago|3 comments
8.
Show HN: MephistoMail – RAM-only ephemeral email with client-side privacy tools(mephistomail.site)
3 points by benmxrt 9mo ago|0 comments
9.
by benmxrt 9mo ago
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. lesso
10.
by benmxrt 9mo ago
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 wit
11.
by benmxrt 9mo ago
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.
12.
by benmxrt 9mo ago
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
13.
by benmxrt 9mo ago
I’m genuinely overwhelmed by the traffic (hitting 145+ concurrent sessions!) and the deep technical feedback from this community. As a solo developer, seeing Mephisto being analyzed so thoroughly is incredible. If you support the idea of a
14.
by benmxrt 9mo ago
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
15.
by benmxrt 9mo ago
I want to be completely transparent here. Mephisto currently utilizes a few different upstream providers (including Guerrilla Mail and 1secmail) via a custom proxy layer to ensure high availability. The goal of this project isn't to bu
16.
by benmxrt 9mo ago
That is an intriguing feature request. Most disposable services avoid outgoing mail entirely to prevent being abused for spam, but a strict 'Reply-Only' policy (where you can only send to the address that just emailed you) is a cl
17.
by benmxrt 9mo ago
Wow, thank you so much! That means a lot coming from this community. I'm trying to keep it as lean and purposeful as possible. Glad the implementation resonated with you!
18.
by benmxrt 9mo ago
That’s a very fair point. Showing the full list makes it easier for automated scrapers to blacklist the whole pool. I’m considering moving to a 'Random Rotation' by default, and only revealing the domain picker for advanced users.
19.
by benmxrt 9mo ago
You're right that the current beta uses Guerrilla Mail as the upstream provider for mail delivery. My 'Zero-Persistence' and 'No-Cookie' claims specifically apply to the Mephisto layer: we don't store your data
20.
by benmxrt 9mo ago
That is a valid point. Currently, the backend keeps them in RAM mainly to support multi-device syncing (like the QR handoff feature) during an active session. If a user scans the QR code to open the same inbox on mobile, the backend needs t
21.
by benmxrt 9mo ago
Absolutely agree with both of you. I just deployed an update that includes a domain picker directly in the address bar. Users can now manually choose from 8 different domains (including .net, .org, .la, and .info) to bypass blanket filters
22.
by benmxrt 9mo ago
Great question. The emails are stored in volatile RAM on the backend only for the duration of the active session. To ensure a smooth experience if you accidentally navigate away or refresh, I’ve recently implemented IndexedDB local caching
23.
by benmxrt 9mo ago
That is a great point, and it's definitely on the roadmap. The "cat and mouse" game between disposable email services and site filters is constant. I'm currently looking into rotating a pool of less common TLDs to keep t
24.
Show HN: Mephisto – A RAM-only, ad-free disposable email PWA built with React(mephistomail.site)
21 points by benmxrt 9mo ago|34 comments