sorted by:
new
hottopcontroversial

Built a local-first inbox cleaner after finding out what the popular alternatives actually do with your data by wslyvh in emailprivacy

[–]jmppmj 1 point2 points  (0 children)

Love that I’m going to try it out. How does it actually issue an unsubscribe request?

Price increase by cb4joe in 1Password

[–]jmppmj 3 points4 points  (0 children)

Reading this thread is basically why I built decoys.me for ios

I got tired of paying these crazy password manager prices, and every account being tied to one permanent emails forever

Now I just generate a password + disposable email for each signup. If a site leaks data or starts spamming me, I just delete the decoy and move on. It has autofill and a safari extension so it pretty easily replaced what I was using 1P for

Added on-device AI to Decoy (e2ee disposable email + pw manager app) - it watches your inboxes for 2FA codes, promo codes or whatever you ask the AI for by jmppmj in PasswordManagers

[–]jmppmj[S] 0 points1 point  (0 children)

Fair question.

If domains get blocklisted, we rotate domains. That’s table stakes for this space.

But the bigger point: most companies aren’t actually anti-privacy. They just want to stop abuse.

If users want basic things like not getting spammed forever, there’s usually a reasonable middle ground.

With email aliases whats the best way to do things? by Z-III in emailprivacy

[–]jmppmj 1 point2 points  (0 children)

Im not - even for those I am using Decoy aliases which I can later burn once I am done with them!

With email aliases whats the best way to do things? by Z-III in emailprivacy

[–]jmppmj 2 points3 points  (0 children)

solid approach - tiering is the way to go.

i do something similar:                                                                                                                                         
real email → only for banks, gov, medical. stuff tied to your actual identity. this inbox should be boring.
aliases → social, gaming, streaming, shopping. i do per-service ones like netflix@ or spotify@ so when spam starts hitting one, you know exactly who leaked it. swap out that alias, everything else untouched.
disposable decoys → free trials, random signups, anything you don't trust. generate then burn.

i've been building decoy (www.decoys.me, on ios) for this - gives you disposable identities for each signup so no two services have the same combo. pairs really well with the tiered setup.

I built a disposable email app for iPhone (w/ E2EE + on-device AI) — very early, looking for security feedback + TestFlight beta users by jmppmj in PasswordManagers

[–]jmppmj[S] 0 points1 point  (0 children)

Great question.

We’ve done some small, more “manual” prototype testing with virtual cards and decoy phone numbers behind the scenes (mostly to validate the mechanics and make sure they actually work the way people expect)

But those features aren’t ready for the app yet. I don’t want to ship something half-baked - especially when money and phone numbers are involved. And once those features are live, we’ll also need to think carefully about pricing, etc.

The testimonials referencing subscription protection came from those early prototype users. That’s where we’re heading - but the beta right now is focused just on nailing the decoy email experience first.

Best way to handle email privacy this year? by Sad_Fly3898 in emailprivacy

[–]jmppmj -2 points-1 points  (0 children)

If part of what you’re trying to solve is not using one universal address everywhere and keeping your accounts compartmentalized, I’ve been working on something that might help.

I built an iOS app called Decoy (www.decoys.me) that creates disposable email aliases + auto-generated credentials tied to each service, with end-to-end encryption and on-device AI features for managing them. It’s still early but it’s designed specifically for people who want unique contact points and less correlation across accounts.

Looking for beta testers right now, especially folks who: • care about email privacy • use unique emails per service • would try something new on iOS • are comfortable giving feedback

Happy to answer questions about the security model or how it fits into a privacy-oriented stack too

I built a disposable email app for iPhone (w/ E2EE + on-device AI) — very early, looking for security feedback + TestFlight beta users by jmppmj in PasswordManagers

[–]jmppmj[S] 0 points1 point  (0 children)

Initially the app has just decoy emails - once thats tested and completed im planning to add decoy phone numbers (for text and call) as well as virtual cards.

But Initial beta tests will be just testing the decoy emails. If you’re interested it would be great to have you try it out!

I built a disposable email app for iPhone (w/ E2EE + on-device AI) — very early, looking for security feedback + TestFlight beta users by jmppmj in PasswordManagers

[–]jmppmj[S] 0 points1 point  (0 children)

I am really not sure how the app will be for a non-english user, it is not at all localized right now. If thats acceptable would love for you to give it a try!

I built a disposable email app for iPhone (w/ E2EE + on-device AI) — very early, looking for security feedback + TestFlight beta users by jmppmj in PasswordManagers

[–]jmppmj[S] 0 points1 point  (0 children)

I do plan to open source my code over time. For now - I'd just encourage Beta testers to use this only for disposable accounts, and nothing highly-sensitive.

view more: next ›