Using [email protected] or name*pod.com for Diaspora
I start this discussion becouse i think this must be discussed.
The question is basically use some specific name for diaspora which is it easy identify as diaspora name.
When you see [email protected] any user identify it as email. But is it not easy identify it as diaspora name, you must know the pod name and you must know this is name and not email.
Idea of this is using something as: name*pod.com which any can identify as diaspora name. Noone can say email now.
I know the discussion about sending emails to messages on pod, but this isn't solution of recognition diaspora name.
The new name can be used on business card, on webpages as contact, on billboards, in TV ads and many more.
Do you think this is good idea?
Jonne Haß Mon 5 Aug 2013 10:03AM
I think the majority disagrees with you for the reasons already stated. If you still feel strong about it open a proposal.
NicoAlto Mon 5 Aug 2013 10:23AM
I disagree too because I think user@pod is logical. Why waste time to change this ?
goob Mon 5 Aug 2013 12:42PM
I like the aesthetics of user*pod.org as something unique to Diaspora, but I think it introduces too many potential problems, both technical and in terms of human misunderstanding, when there isn't really a problem in the current situation to be solved.
Maciek Łoziński Tue 6 Aug 2013 7:22AM
On your business card you can always write:
"email: [email protected]
jabber: [email protected]
diaspora: [email protected]"
And having @ in the identifier is good if we decide to implement a chat in Diaspora using XMPP.
Poll Created Thu 8 Aug 2013 8:06AM
Use user*pod.com redirection? Closed Thu 22 Aug 2013 7:08PM
Results
Results | Option | % of points | Voters | |
---|---|---|---|---|
|
Agree | 3.3% | 1 | |
Abstain | 0.0% | 0 | ||
Disagree | 96.7% | 29 | ||
Block | 0.0% | 0 | ||
Undecided | 0% | 253 |
30 of 283 people have participated (10%)
nio
Thu 8 Aug 2013 8:09AM
I think redirection is good idea
Alex
Thu 8 Aug 2013 8:16AM
I think it's just not necessary and may lead to confusion since *'s are usually used as wildcards.
Alex
Thu 8 Aug 2013 8:17AM
I think it's just not necessary and may lead to confusion since *'s are usually understood as wildcards.
Jonne Haß
Thu 8 Aug 2013 8:23AM
This would actually complicate the user experience as it's confusing to have two standards. Also I don't like adding a dozen special cases to the code.
nio · Sun 4 Aug 2013 9:59PM
Send any feedback, suggestion, many peoples, many opinions ;)