If you don’t have an account already, you need to use DDG extension for the first time to sign up then you can remove it later and sign in to Qwacky.
I will try find a workaround in the future to make a sign up option in Qwacky so you don’t have to use DDG extension at all.
Understood! I thought it was possible to create an alias from the beginning (“to generate & manage DuckDuckGo email aliases!”), so it’d be helpful if you could clarify this point in the product explanation 
Thank you for the clarification! Misspellings like this were expected in any write-up related to the project, since English is not my native language.
I will do my best 
v1.2.0 is finally here!
And it’s my favorite one so far!
This is really how i wanted it to be from the first release, To be even more secure and privacy respect by using minimal and optional permissions and a way to toggle them on/off, But since it was my first time making a chrome extension i couldn’t make it then, so yeah hopefully nothing brakes after this update 
Approved in Firefox and still pending in Chrome
Here is the Changelog:
Kudos for the great project. Default DDG requiring the installed extension created a bit of friction, so I just made do w/ my main @duck.com email address (and 4-5 free anonymous mozmail ones from Firefox)
This extension let’s me spread out my emails indiscriminately again so that it’ll be harder to create a profile on me. Great work!
Im glad you found it useful!
I get new alias basically with a single command:
curl -s -X POST -H “Authorization: Bearer APIKEY” -H “Content-Type: application/json” https://quack.duckduckgo.com/api/email/addresses | jq -r ‘“(.address)@duck.com”’
I’m still pretty new to using DDG Alias — I’ve been using it for about a month now — and I thought it would be great to have a way to manage them, so I’m really glad I found this extension! I do have one question, though. Maybe this feature already exists and I just missed it, or maybe there’s a reason it hasn’t been added yet.
Is there (or will there be) a sync feature? For example, if you use multiple browsers like Brave and Firefox, or if you dual boot between Windows and Linux, it would be great to see your list of aliases across all setups. As far as I understand, if I want to keep everything in sync right now, I have to do it manually by exporting and importing a JSON/CSV file.
this does require quite the server code @Omar will have to make let alone how to make it privacy friendly or respecting without say some company buying Qwacky and breaking that privacy friendly/respecting model PTSD of Skiff (which in this case would need to do E2EE but how is a completely different question, proton/firefox style most likely but how can it be done without unencrypted bits before at rest leaking in the even of say law enforcement warrant [See tuta law enforcement situation]) [Haven’t even mentioned needing to be properly secured as well]
let me make it clear, im not saying that Qwacky will be bought out, not my point, my point is, let’s hypothetically say Qwacky was bought out with the server code in tact, how can the privacy of users be retained in that scenario, that’s the way to think of it
Thank you, I’m glad you found the extension!
Here’s a good news, Im already working on such a feature!
And i know how useful would it be to have it, since I’m a Qwacky user too😁
Currently I’m learning the syncing system in both Chromium and Firefox browsers, I will drop it soon as an (experimental) feature because it needs more work and testing!
Unfortunately i can’t promise with a specific estimated date because of my work schedule, i will post here as soon as it drops.
Thanks for the thorough explanation!
Just to clarify, from what I understand, this wouldn’t require external Qwacky servers. The extension would use the browser’s built-in storage.sync API.
However, you raise a valid point about privacy. Let me break down what would happen:
Firefox: Extension data syncs through Firefox Sync (requires Firefox account). Firefox encrypts data locally with keys derived from your account password. (E2EE by default).
Brave: Extension data syncs through Brave Sync (no account required). Brave encrypts data with keys from your sync chain code. (E2EE by default).
Chrome: Extension data syncs through Chrome Sync (requires Google account). By default, You can enable a custom sync passphrase in Chrome settings for E2EE, but most users don’t set this up.
Thanks for your quick response — I really appreciate it!
I finally found the time to write back and share some thoughts. I think the extension is great overall. A sync option would be very handy, though I understand if it’s less secure or technically challenging. But If you say you already work on it then I will look forward to it.
It would also be nice to have a search feature, so you can easily look through all your email aliases using the names you’ve assigned to them, for exmaple if you have 50 or smth this would be helpful.
Another useful improvement could be if deleting an alias which leads to automatically disable it — similar to how clicking “disable” in a DuckDuckGo email header works. Or even better would be a simple enable/disable toggle for aliases. So you can enable/disable it really quick.
These are just some ideas I came up with that might help improve the already great extension. I hope they’re useful in some way! I imagine the search feature might be easier to implement, while the delete/disable functionality could be a bit more complex — or maybe not possible at all. Either way, I just wanted to share what came to mind. And if any of these features are already implemented and I simply missed them, please pardon me!
Hi @Omar
Can you add a naming feature to accounts to make them easier to distinguish if using multiple accounts instead of the account email address?
Hi @Omar I just got a duck address, activated it etc and installed the DDG extension and your Qwacky extension and I get this error - NetworkError when attempting to fetch resource - when trying to sign in to Qwacky.
Any idea why that might be happening?
I have a ton of protections installed/in use - UBlock Origin, DNS 0ver HTTPS, Cloudflare Warp pseudo VPN, Celenity’s Phoenix hardening, Adguard Home DNS blocking.
I assume it might be one of those things above blocking something. But the DDG extension works, and I still got the error when I turned off or disabled UbO, and when I uninstalled or disabled the DDG extension.
Any thoughts or help would be appreciated.
Thanks!
Sorry to hear you’re having issues!
What browser are you using?
Could you try installing it on a different browser as a starting point for debugging
Thanks for getting back to me! No worries…it is probably the crazy layers of protections I have set up.
I am using Firefox, sorry forgot to mention that.
I can try it on Librewolf or Mullvad. Or maybe a different Firefox profile. I do not have any mainstream/non privacy focused/Vanilla/chromium browsers installed.
It worked in Librewolf! So obvi it is something in my Firefox set up.
I suspect Phoenix. I will ask the dev about it.
I’m glad you figure it out, And hopefully you fix it in your main browser
Thanks. Any thoughts on what might be causing the issue with hardening approaches like Phoenix/Arkenfox?
I’m not sure, I use vanilla Firefox with only in-browser settings tweaks