I’m excited to introduce Paperweight, a local-first open-source desktop app I’ve been building to help people understand and reduce their digital footprint.
Your inbox is a paper trail of every company that has ever had your data. Every account you created, every service you tried, every online purchase. It’s all connected to your email. Most people have 100+ accounts they’ve forgotten about, each a potential security, or privacy risk. For me the final push was the Odido data breach in the Netherlands. I hadn’t been a customer for more than 8 years, but all my data was still in their systems.
What it does:
- Account inventory — Maps every company that has ever emailed you, with risks classifications and recommendations for action.
- Bulk unsubscribe — Find and unsubscribe from any marketing and mailing lists (auto RFC 8058 where supported).
- Breach alerts — Alerts when any company you’ve been in contact with has been breached (via HaveIBeenPwned).
- GDPR requests —
... Show more...I’m excited to introduce Paperweight, a local-first open-source desktop app I’ve been building to help people understand and reduce their digital footprint.
Your inbox is a paper trail of every company that has ever had your data. Every account you created, every service you tried, every online purchase. It’s all connected to your email. Most people have 100+ accounts they’ve forgotten about, each a potential security, or privacy risk. For me the final push was the Odido data breach in the Netherlands. I hadn’t been a customer for more than 8 years, but all my data was still in their systems.
What it does:
- Account inventory — Maps every company that has ever emailed you, with risks classifications and recommendations for action.
- Bulk unsubscribe — Find and unsubscribe from any marketing and mailing lists (auto RFC 8058 where supported).
- Breach alerts — Alerts when any company you’ve been in contact with has been breached (via HaveIBeenPwned).
- GDPR requests — Generates pre-filled GDPR requests in multiple languages.
Supports Gmail, Outlook, Apple Mail, Proton (via Bridge) and any other email provider via IMAP.
Privacy approach:
Everything runs on your machine. Email content, credentials, and connection details never leave your device. No telemetry, no cloud sync, no analytics. The code is fully open source and auditable on GitHub.
Most alternatives in this space all require your to share your data through their services. Some of them have actually been caught selling your data. Paperweight is the only tool I’m aware of that does this entirely local and is open-source.
Website
- paperweight.email/
Feedback welcome! Thanks
Paperweight scans your inbox to map your digital footprint, then helps you take back control and delete your data. Local-first and open source. - wslyvh/paperweight
GitHub
warmaster
in reply to wslyvh • • •Great project. Thanks for sharing, and cool you chose to open source some / all of it. That said...
Are the paid features open source too? If so, then it's really open source.
If the paid features are not open source, then the project does not grant the 4 freedoms the FSF requires to recognize the project as open source.
This is commonly known as open core (or open washing?).
I'm not giving advice on what you should do, I'm only pointing out a possible incoherence between what you say and what you made.
Encom
in reply to warmaster • • •wslyvh
in reply to Encom • • •wyldrstallyns
in reply to wslyvh • • •Hol'up. "All code is there" after one pays to access it, you mean?
edit: Ah, it feels like that other place, where downvotes are kbarbarians' impotent ire. The perfect environment for valid questions. Love to see it.
warmaster
in reply to wyldrstallyns • • •AtHeartEngineer
in reply to warmaster • • •wslyvh
in reply to warmaster • • •wyldrstallyns
in reply to warmaster • • •wslyvh
in reply to warmaster • • •Thanks for the reply! And good question. Yes, all code, including all paid features are open source too. Not just open core. There's nothing proprietary. Some of the paid features are gated behind a license check, but it's all part of the same repo and MIT licensed. It's all there to inspect or fork if you want. The perpetual license however helps support development and gives the convenience of a ready-made build.
We actually moved recently from GPLv3 to MIT to be fully permissive.
warmaster
in reply to wslyvh • • •This is great, you got yourself a new customer!
Local-only and fully FOSS, I truly appreciate it!
I'll subscribe as soon as I get on my rig!
wslyvh
in reply to warmaster • • •AtHeartEngineer
in reply to wslyvh • • •pcouy
in reply to wslyvh • • •Can you explain how this is a good thing for users ? From my own (admittedly limited) understanding of licenses, the main difference between GPL and MIT is that MIT allows freeriding off open source project by making closed-source forks.
wslyvh
in reply to pcouy • • •ohshit604
in reply to wslyvh • • •5 contributors, 2 of which are “Ai”’s.
I suspect a -
-- Infected repo.
Definitely a cool project if it’s not though!
AtHeartEngineer
in reply to ohshit604 • • •ggtdbz
in reply to AtHeartEngineer • • •The post text is dripping with it but I haven’t looked at the code. A lot of my complaining about slop is how people for whom English is not a strong language over-depend on it, kind of never developing a voice over time. Instead sounding like the Burger King support bot.
I wouldn’t even know if the code was machine generated. I never tried that so I don’t recognize it if it’s not glaring.
Code is out there though so maybe someone can port it into a Thunderbird addon or something. I think this is a very cool project
TrueDahn
in reply to ohshit604 • • •Axolotl
in reply to TrueDahn • • •They finally replied
lemmy.ml/comment/25776478
Also, i can see why they wouldn't answer to such a comment, opening the comments and seeing a big ass image of a "SLOP" sign does not feel good at all, especially after you spent time making the thing
wslyvh
2026-05-20 08:56:18
They finally replied
lemmy.ml/comment/25776478
Also, i can see why they wouldn't answer to such a comment, opening the comments and seeing a big ass image of a "SLOP" sign does not feel good at all, especially after you spent time making the thing
wslyvh
2026-05-20 08:56:18
LemmyFeed
in reply to wslyvh • • •wslyvh
in reply to LemmyFeed • • •Sure, like most projects I use AI assistance a lot for most of my work these days, ngl. Its helps me plan, research and code new ideas/features and makes a lot of my work easier. Having said that, I fully understand and share people's feelings about yolo, vibe-coded slop. I've been a software engineer for 20+ years. AI helps with a lot, but also feels like the honeymoon phase is wearing off actually. It doesn't give me the joy of building stuff. I still test, review and ship everything myself. You can check my Github history that I've been doing this way before recent AI hype.
Either way, the idea and execution is 100% me. I'm building something I want, use, and care about myself. Whether I've used AI is not too relevant, imo. It's that all alternatives have been caught selling your data (Unroll), heavily rely their centralized services or require you to give up your data in order to remove it. Which is ironic. Paperweight is the only tool I’m aware of that does this entirely local and is open-source.
P.S if its quality you're worried about, Paperweight has been
... Show more...Sure, like most projects I use AI assistance a lot for most of my work these days, ngl. Its helps me plan, research and code new ideas/features and makes a lot of my work easier. Having said that, I fully understand and share people's feelings about yolo, vibe-coded slop. I've been a software engineer for 20+ years. AI helps with a lot, but also feels like the honeymoon phase is wearing off actually. It doesn't give me the joy of building stuff. I still test, review and ship everything myself. You can check my Github history that I've been doing this way before recent AI hype.
Either way, the idea and execution is 100% me. I'm building something I want, use, and care about myself. Whether I've used AI is not too relevant, imo. It's that all alternatives have been caught selling your data (Unroll), heavily rely their centralized services or require you to give up your data in order to remove it. Which is ironic. Paperweight is the only tool I’m aware of that does this entirely local and is open-source.
P.S if its quality you're worried about, Paperweight has been audited through Google's CASA assessment and Apple's developer verification (admittedly, not a super high bar).
icelimit
in reply to wslyvh • • •Ai is just the next iteration of tool advancement. Woodworking by hand into power tools making the same thing but shunning it because you didn't put the requisite sweat into it; Photoshop vs hand painting/real pictures; assembly coding vs compilers/high level code.. it's all the same tune.
We tie greater emotional/perceived value to 'hard work' put into something without discussing the time saving, the RSI benefits and so on.
AtHeartEngineer
in reply to wslyvh • • •wslyvh
in reply to AtHeartEngineer • • •AtHeartEngineer
in reply to wslyvh • • •pathos
in reply to wslyvh • • •wslyvh
in reply to pathos • • •dave
in reply to wslyvh • • •MonkderVierte
in reply to dave • • •Either way, you should reduce the active subscribtions and use it as a spamhole (because it 100% was in some leaks already). Never "delete" an old E-Mail address, they can be used to hijack your accounts.
And maybe forward the phishing mails to your countries @antiphishing address.
dave
in reply to MonkderVierte • • •This was on a custom domain, and I started off with xyz-1@domain.com, and when it became saturated I moved to -2, -3, etc. But then got lazy and used my current ‘version’ to sign up for things I’d want to keep, not just any old random stuff. So now it’s a mix, and much better ways of doing that exist, like +tagging and hide-my-email services.
I even wondered about setting up a catch-all account on the domain so I can just invent them on the fly, and then when one becomes spammy, create an ‘actual’ account as a spamhole.
wslyvh
in reply to dave • • •Migrating 20+ year inboxes are definitely a pain. I did it a while ago, and tried to stay on top of it better since. As said below, never fully delete an old-email address. Others might be able to hijack the old account and impersonate you. Use a custom domain so you can easily switch providers if ever needed. A catch-all or aliases work great, but check if it allows to send from it. Especially for verification (e.g. delete an account) you often need to verify or send from the origin email. I stopped unique addresses per website. I'd keep a few just to separate "official" things, from general use/registration, and stuff I don't trust.
Paperweight sort of gives you an overview of services, but I'd recommend to do this more gradually otherwise you'd probably go crazy. Whenever you sign up, check your email and change to one of the addresses above. After a year or so, you likely have done most important once (that at least require you to login). You could probably just keep the others as is, with your old email for legacy. But only use the new address(es) moving forward.
... Show more...Migrating 20+ year inboxes are definitely a pain. I did it a while ago, and tried to stay on top of it better since. As said below, never fully delete an old-email address. Others might be able to hijack the old account and impersonate you. Use a custom domain so you can easily switch providers if ever needed. A catch-all or aliases work great, but check if it allows to send from it. Especially for verification (e.g. delete an account) you often need to verify or send from the origin email. I stopped unique addresses per website. I'd keep a few just to separate "official" things, from general use/registration, and stuff I don't trust.
Paperweight sort of gives you an overview of services, but I'd recommend to do this more gradually otherwise you'd probably go crazy. Whenever you sign up, check your email and change to one of the addresses above. After a year or so, you likely have done most important once (that at least require you to login). You could probably just keep the others as is, with your old email for legacy. But only use the new address(es) moving forward.
Hope that helps!
apotheotic (she/her)
in reply to wslyvh • • •Edit: oh huh I missed that it's ~~not FOSS~~ paid. 69 bucks for a "perpetual" license that only gets updates to v1 is a bit dire
youmaynotknow
in reply to apotheotic (she/her) • • •wslyvh
in reply to apotheotic (she/her) • • •apotheotic (she/her)
in reply to wslyvh • • •wslyvh
in reply to apotheotic (she/her) • • •exist
in reply to wslyvh • • •MonkderVierte
in reply to exist • • •TrippingBalls
in reply to MonkderVierte • • •MonkderVierte
in reply to TrippingBalls • • •Axolotl
in reply to wslyvh • • •wslyvh
in reply to Axolotl • • •Axolotl
in reply to wslyvh • • •You can use CI/CD on codeberg but it's use is limited, you will have to fill a form so that the staff can deem if your use case is appropiate, they sadly have little resources and CI/CD is kinda costly
docs.codeberg.org/ci/
You can also self-host your own CI and link it to codeberg id you want to do resource intensive stuff
It's actually a legit concern, everyone uses softwares because it's more convenient for them, even if i am a big fan of "if you can, you should compromise a little" philosophy i can totally see why someone wouldn't want to use a inconvenient software for them
Working with Codeberg's CI | Codeberg Documentation
docs.codeberg.orgmoopet
in reply to wslyvh • • •Quick correction point:
Not all email providers use IMAP
wslyvh
in reply to moopet • • •icelimit
in reply to wslyvh • • •