this post was submitted on 08 Jan 2025
146 points (100.0% liked)

Selfhosted

45345 readers
1209 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Just discovered this cool project, thought i'd share it here.

AliasVault is an end-to-end encrypted password and alias manager that protects your privacy by creating alternative identities, passwords and email addresses for every website you use. Keeping your personal information private.

Link to website: https://www.aliasvault.net/

Link to source code (MIT Lisense): https://github.com/lanedirt/AliasVault

For those wondering how the alias feature works:

AliasVault includes a built-in email server that allows you to create unique email addresses (aliases) for different services. When someone sends an email to your alias, it's received directly in AliasVault, helping you maintain privacy and reduce spam.

you are viewing a single comment's thread
view the rest of the comments
[–] NaibofTabr@infosec.pub 33 points 2 months ago* (last edited 2 months ago) (13 children)

Ah, if all of your email aliases trace back to your personal, locally hosted server, of which you are the only user, on presumably your personally owned domain, it will not be private... well private in the sense that it's just you I guess... but super duper identifiable - because it's just you. At which point why bother with the aliases.

[–] Dark_Arc@social.packetloss.gg 24 points 2 months ago (1 children)

As someone that uses a custom domain for the majority of his email, it's not really a privacy thing, it's a control thing.

I have hundreds of unique unpredictable email addresses and I can disconnect them at will to stop spam.

[–] starshipwinepineapple@programming.dev 9 points 2 months ago* (last edited 2 months ago)

Agreed, though i do think it's a privacy thing. Many people use privacy and anonymity interchangeably but they are different things.

The options are:

  • use a single email. If it is leaked you need to update hundreds of accounts or risk falling for a malicious email
  • use a catch-all email and each service gets a separate email, but you can't turn off receiving mail at a specific address unless you use a sieve filter. This doesn't stop people from just guessing random addresses.
  • use specific aliases for each service. Idk about this specific project but usually you can turn off receiving mail at an alias. So if a company gets a data breach i just change my email (or close the acct), then i turn off the old alias.

I did the catchall for a few years but have been doing aliases for 5+ now. In the end, the only people/ companies who have my email are the ones I want.

load more comments (11 replies)