Firefox Relay에 대한 리뷰
Firefox Relay 제작자: Firefox
p6 님의 리뷰
Nov 1st, 2020;
Without the ability to reply using the Firefox relay alias, the very purpose to use Relay is moot!
I contacted a car dealership using one of my aliases. However, I had to reply using my own personal email, which got captured by the dealership, and I am now permanently entered in his distribution list.
So, what is the point?
--------------------------------------------------------------
I would like to have the option to create my own prefix email, using the @relay.firefox.com. Without the limitation of 5 aliases.
In this manner, I can control which email is being spammed, example:
I create an account with a new entity; I create the specific alias:
-Mynametag.newentity@relay.firefox.com
If I start to receive junk mail from "newentity", then I delete the alias.
I have done that for many years, unfortunately, it means that I need to create a new email address each time I enroll, which means my computer currently reads tens of email addresses.
So you should give the option to the user to create his own alias, and remove the limit of 5.
Edit on July 31st, 2020:
To avoid collisions, or similar prefixes, you can always have a validation running at creation time; I also add a string to make my alias unique, such as the date at which I create it:
20200731NewEntity@p6.firefox.com
This has two benefits: I can organize my email aliases list in chronological order, increasing or decreasing, and I always keep track of the date at which I created the alias.
Without the ability to reply using the Firefox relay alias, the very purpose to use Relay is moot!
I contacted a car dealership using one of my aliases. However, I had to reply using my own personal email, which got captured by the dealership, and I am now permanently entered in his distribution list.
So, what is the point?
--------------------------------------------------------------
I would like to have the option to create my own prefix email, using the @relay.firefox.com. Without the limitation of 5 aliases.
In this manner, I can control which email is being spammed, example:
I create an account with a new entity; I create the specific alias:
-Mynametag.newentity@relay.firefox.com
If I start to receive junk mail from "newentity", then I delete the alias.
I have done that for many years, unfortunately, it means that I need to create a new email address each time I enroll, which means my computer currently reads tens of email addresses.
So you should give the option to the user to create his own alias, and remove the limit of 5.
Edit on July 31st, 2020:
To avoid collisions, or similar prefixes, you can always have a validation running at creation time; I also add a string to make my alias unique, such as the date at which I create it:
20200731NewEntity@p6.firefox.com
This has two benefits: I can organize my email aliases list in chronological order, increasing or decreasing, and I always keep track of the date at which I created the alias.
개발자 답글
5년 전에 게시됨Thanks for the feedback. Creating custom local parts will definitely lead to collisions in the future, so we have an issue filed to support "catch-all" subdomains for aliases: https://github.com/mozilla/fx-private-relay/issues/55
E.g., you could make up any alias you want like newentity@p6.firefox.com.
E.g., you could make up any alias you want like newentity@p6.firefox.com.
리뷰 2,166개
- 5점 만점에 5점MY AMERICA INC 님, 하루 전
- 5점 만점에 5점Firefox 사용자 19140627 님, 5일 전
- 5점 만점에 5점Firefox 사용자 19140137 님, 5일 전
- 5점 만점에 5점Firefox 사용자 17657480 님, 7일 전
- 5점 만점에 5점Firefox 사용자 14153561 님, 8일 전
- 5점 만점에 5점Firefox 사용자 18849678 님, 12일 전
- 5점 만점에 5점Firefox 사용자 19082444 님, 13일 전
- 5점 만점에 4점Firefox 사용자 18223698 님, 13일 전
- 5점 만점에 5점علي الخلقي 님, 18일 전
- 5점 만점에 5점Firefox 사용자 18206070 님, 18일 전
- Mozilla's Mask email addresses are incompatible with a lot of websites. Which is a major inconvenience. Also, because of this service, a ton of important emails get filtered to my Gmail's SPAM folder. Setting up an email address for non-personal use is quite easy and the ability to reply is not hidden behind a paywall.