Hello,
Say :
- You, john, set up your familyname[.]com with Google for members of your family.
You love the domain but then you would personaly use yourself another provider which is more expensive
- You can't move your familyname[.]com from Google (easier for everyone, cheaper...)
- All other good TLD are taken for your familyname (.net, .co, .me, .org, regional...)
- You can forward those email messages sent to john@familyname[.]com somewhere else
What do you do :
1 - Go to another provider with a less known TDL, like .cc.
=> Then you would reply to incoming email sent to john@familyname[.]com with john@familyname[.]cc
2 - Go to another provider and alter your familyname[.]com to familynameS[.]com
=> Then you would reply to incoming email sent to john@familyname[.]com with john@familynames[.]com
Which one is best, which one looks less awkward ?
Does the ".cc" reply address add confusion ? Or does the extra "s" look weird ?
Thank you
Say :
- You, john, set up your familyname[.]com with Google for members of your family.
You love the domain but then you would personaly use yourself another provider which is more expensive
- You can't move your familyname[.]com from Google (easier for everyone, cheaper...)
- All other good TLD are taken for your familyname (.net, .co, .me, .org, regional...)
- You can forward those email messages sent to john@familyname[.]com somewhere else
What do you do :
1 - Go to another provider with a less known TDL, like .cc.
=> Then you would reply to incoming email sent to john@familyname[.]com with john@familyname[.]cc
2 - Go to another provider and alter your familyname[.]com to familynameS[.]com
=> Then you would reply to incoming email sent to john@familyname[.]com with john@familynames[.]com
Which one is best, which one looks less awkward ?
Does the ".cc" reply address add confusion ? Or does the extra "s" look weird ?
Thank you
