[jdev] [OT] XMPP icons
Sander Devrieze
s.devrieze at pandora.be
Mon Jul 7 15:47:25 CDT 2008
2008/7/7 Peter Saint-Andre <stpeter at stpeter.im>:
> naw wrote:
>>
>> El Viernes 04 Julio 2008, Sander Devrieze escribió:
>>>
>>> 2008/7/4 Pedro Melo <melo at simplicidade.org>:
>>>>
>>>> Hi,
>>>>
>>>> in case you need XMPP logo icons, I converted the SVG to PNGs
>>>> 512x512, 256x256, 128x128 and 64x64, both regular and crushed, with
>>>> alpha channel.
>>>>
>>>> You can find them here:
>>>>
>>>> http://www.simplicidade.org/me/xmpp.html
>>>>
>>>> and in a ZIP here:
>>>>
>>>> http://www.simplicidade.org/me/xmpp.zip
>>>>
>>>> I've also sent them to Peter, in case he wants to make this available
>>>> at the xmpp.org site.
>>>
>>> Please find attached another version of the logo. There also exists a
>>> Tango version which you can find in Pidgin. PS: if someone could
>>> contribute an Oxygen version of the logo for Coccinella that would be
>>> really fine!
>>
>> But the official icon for applications should be the jabber bulb, or the
>> xmpp X? should the apps be renamed from "jabber client" to "xmpp client"?
>>
>> I think that most apps use the bulb and are called "jabber client" but
>> pidgin doesn't, wich is a bit confusing.
>
> IMHO:
>
> Jabber is to XMPP as the Web is to HTTP.
Right
> Geeks talk about HTTP, but end users talk about web browsers and web sites.
Wrong. When end users read "http://www.example.org/", they will
*associate* this with the address of a website!
> Geeks talk about XMPP, but end users talk about Jabber clients (or just IM
> clients).
Semi-wrong: the part between brackets is right.
> Therefore I think it is best for end-user clients to use the term "Jabber".
> This is more user-friendly and less geeky for Aunt Tillie.
Neither "Jabber" not "XMPP" should be used IMHO. Let them use the term
"instant messaging", but make them *associate* the term "XMPP" with
"instant messaging". When people (both geeks and end users) see the
term "XMPP" and/or the logo on a website or in some software, they
should directly associate it with interoperability, open standard,
instant messaging, not getting locked in a walled garden, and so
forth.
Summary:
1) "HTTP" versus "XMPP": association with open standard for Web/IM
2) globe logo versus XMPP wings logo: association with open standard for Web/IM
3) Web/website/web browser/web server/... versus Instant
messaging/instant messaging address (or Contact ID)/instant messaging
client/instant messaging server: what people use in daily life
4) Goal of using the XMPP wings logo or the term "XMPP": get people to
actually *associate* both with the one and only good way of
interroperable instant messaging ;-) So, people don't need to actually
call your service/client/server an "XMPP service"/"XMPP client"/"XMPP
server". People only should make the association that your
service/client/server is interroperable/open/open standard/good/not
evil/great/fantastic/amazing/you know
> That said, I am an individualist and I value decentralization, so if
> particular IM clients want to call it XMPP instead of Jabber, that's their
> business. But I reserve the right to boycott them. :)
That's your right, but it's also my right to try to change your mind ;-)
--
Mvg, Sander Devrieze.
More information about the JDev
mailing list