Re: Advertising xmpp

2008/1/6, Luke -Jr <lukedashjr.org>:
> On Saturday 05 January 2008, Sander Devrieze wrote:
> > /me pokes once more the XSF regarding standardize
the use of one of
> > these: Jabber/XMPP/Talk/something else
>
> I don't think this is a good idea. Better to break the
barrier that people are
> assuming of different services being incompatible. I
stick to "standards
> compliant" and give examples like Jabber, Google
Talk, Gizmo, etc.
> Instead of e-mail address, should we be saying AOL vs
SMTP address?

We call it "email address" and not "Dashjr
address", for instance,
right? People know what you mean with "This is my email
address.",
"This is an email client", and "This is an
email service".

Current problem: Pidgin, Adium and maybe some others call it
"XMPP";
Google and Live Journal call it "Talk", differet
Jabber clients call
it either Jabber, Jabber ID, JID or something else. Clients
like
Pidgin and Adium even find it necessary to add fake entries
for Google
Talk and Live Journal because WE HAVE A BRANDING PROBLEM
(sorry for
yelling). End users get confused by the use of all these
different
names that mean the same...how are we going to fix this? By
doing
nothing? IMO the wait and see strategy is not what we need.

Process:
1) XSF tells it has to be called <fill in something>
(+ optionally a logo)
2) Pidgin, Adium, Psi, Gajim, Google Talk, Coccinella, Live
Journal,
Apple, ejabberd, Tigase, Tkabber, Kopete, jabber.org, and so
forth can
adopt this name (and the logo if there is one)
3) All non-geek end users can easily see all these software
and
services are *compatible* in no time
4) In the long run end users will start to associate this
name with
what we offer and they will find it obvious that all IM
services and
IM software are compatible.
5) If there are still closed IM networks like AIM/MS/etc,
non-geek end
users will start to bother the support staff of these
services with
questions like "How can I connect with Psi to your
service?".

> > ** maybe for some people too general
>
> "IM address" works, but I do think there
should be something more generic.
> After all, SMTP may one day be replaced with XMPP, and
when I get around to
> it, I will probably be porting some games to use XMPP
for server browsing and
> chat.

What about the "Contact ID/address" suggestion?

-- 
Mvg, Sander Devrieze.
_______________________________________________
JAdmin mailing list
JAdminjabber.org
http:/
/mail.jabber.org/mailman/listinfo/jadmin
FAQ: http://ww
w.jabber.org/about/jadminfaq.shtml
_______________________________________________

On Sunday 06 January 2008, Sander Devrieze wrote:
> 2008/1/6, Luke -Jr <lukedashjr.org>:
> > On Saturday 05 January 2008, Sander Devrieze
wrote:
> > > /me pokes once more the XSF regarding
standardize the use of one of
> > > these: Jabber/XMPP/Talk/something else
> >
> > I don't think this is a good idea. Better to break
the barrier that
> > people are assuming of different services being
incompatible. I stick to
> > "standards compliant" and give examples
like Jabber, Google Talk, Gizmo,
> > etc. Instead of e-mail address, should we be
saying AOL vs SMTP address?
>
> We call it "email address" and not
"Dashjr address", for instance,
> right? People know what you mean with "This is my
email address.",
> "This is an email client", and "This is
an email service".

I have an IM address, lukedashjr.org
If someone asks what service, I run my own IM service, but
it is compatible 
with any standards-compliant IM services.
_______________________________________________
JAdmin mailing list
JAdminjabber.org
http:/
/mail.jabber.org/mailman/listinfo/jadmin
FAQ: http://ww
w.jabber.org/about/jadminfaq.shtml
_______________________________________________