{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreian75ekyzpwwio2xxcsv3ezb4cdyrvlpxfg4vxqhp7e3dkcicxnym",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mo5ohe5f6da2"
  },
  "path": "/t/aliasvault-open-source-e2ee-password-email-alias-manager/24436?page=11#post_213",
  "publishedAt": "2026-06-13T05:59:54.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "@aliasvault.net"
  ],
  "textContent": "Hi, happy to hear you’ve been using AliasVault for such a long time already!\n\n> Is there any way I can mass select login/alias to move them to a folder in bulk?\n\nIt’s not possible yet, but bulk operations on login and email items is a feature that’s being actively worked on and will be added in one of the next releases to all apps . Likely within 2 weeks or so.\n\n> Is it correct that if someone enter the same email address I’ve used, they will be able to access the mails? For example, if I created unseen@aliasvault.net, can someone use the same email address unseen@aliasvault in their AliasVault account?\n\nAliasVault’s private email addresses (`@aliasvault.net` for the cloud-hosted server) are cryptographically tied to the user that first claimed it. All email that is received for that alias is encrypted with the specific user’s encryption key, and so can only be read by that user. So in your example, if somebody else would try to re-claim an already used private email address, they will get to see an error that this email alias has already been claimed and cannot access it. Email claims are permanent, so even if you disable an alias (e.g. delete it), others still won’t be able to re-use it.",
  "title": "AliasVault: Open-Source E2EE Password & (Email) Alias Manager"
}