Add Email Aliasing page #2409
Merged
Add Email Aliasing page #2409
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request has been mentioned on Privacy Guides. There might be relevant details there: https://discuss.privacyguides.net/t/email-aliasing-on-separate-page/16921/13 |
✅ Deploy Preview for privacyguides ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
rollsicecream
force-pushed
the
email-aliasing-page
branch
from
885956f
to
69b9b0d
Compare
freddy-m
added
the
c:providers
rollsicecream
force-pushed
the
email-aliasing-page
branch
from
69b9b0d
to
13db0ea
Compare
|
Awesome, thanks for this. Part of this PR will have to be removing them from |
rollsicecream
force-pushed
the
email-aliasing-page
branch
from
13db0ea
to
656091f
Compare
|
@jonaharagon Done! As you requested. |
rollsicecream
force-pushed
the
email-aliasing-page
branch
from
656091f
to
822ee4c
Compare
|
It comes from iStock : https://www.istockphoto.com/en/photo/secure-mail-on-digital-screen-gm486272596-72895153 |
|
I think that presents too much of a risk/problem for us. Replacing with a photo by Joel Dunn at https://unsplash.com/photos/black-and-white-abstract-painting-f3Ug9b50KwI (it's metaphorical lol) |
jonaharagon
force-pushed
the
email-aliasing-page
branch
from
f3b853c
to
63d0362
Compare
jonaharagon
pushed a commit
to rollsicecream/privacyguides-fork
that referenced
this pull request
Mar 13, 2024
jonaharagon
force-pushed
the
email-aliasing-page
branch
from
63d0362
to
4fbe7ea
Compare
jonaharagon
added a commit
to rollsicecream/privacyguides-fork
that referenced
this pull request
Mar 13, 2024
Co-Authored-By: Jonah Aragon <jonah@triplebit.net>
jonaharagon
force-pushed
the
email-aliasing-page
branch
from
4fbe7ea
to
a60564e
Compare
jonaharagon
approved these changes
Mar 13, 2024
dngray
approved these changes
Mar 14, 2024
dngray
force-pushed
the
email-aliasing-page
branch
from
1fcc4d9
to
53c5091
Compare
dngray
added a commit
to rollsicecream/privacyguides-fork
that referenced
this pull request
Mar 16, 2024
Co-Authored-By: Jonah Aragon <jonah@triplebit.net> Co-Authored-By: Daniel Gray <dngray@privacyguides.org>
dngray
force-pushed
the
email-aliasing-page
branch
from
53c5091
to
04d65a2
Compare
Co-Authored-By: Jonah Aragon <jonah@triplebit.net> Co-Authored-By: Daniel Gray <dngray@privacyguides.org>
dngray
force-pushed
the
email-aliasing-page
branch
from
04d65a2
to
2b88698
Compare
|
This pull request has been mentioned on Privacy Guides. There might be relevant details there: https://discuss.privacyguides.net/t/email-aliasing-on-separate-page/16921/25 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this PR:
Add Email Aliasing page
Remove all E-Mail alias services from "Email Services" page and move them to that new page.
For now, this doesn't have any criteria since we are in discussion here : https://discuss.privacyguides.net/t/email-aliasing-on-separate-page/16921
When the discussion will come to an end, the necessary changes will be done to this PR. Let's say it's a "prototype".