Please put your comment here and tell me what would you like to implement in the final version of glu.
Thank you.
Please put your comment here and tell me what would you like to implement in the final version of glu.
Thank you.
Version 0.1 of XEP-0271: XMPP Nodes has been released.
This specification more clearly defines the nature of nodes as used in the Service Discovery and Publish-Subscribe extensions to the Extensible Messaging and Presence Protocol (XMPP).
The changelog is:
Initial published version; per Council discussion changed local to localpart. (psa)
Version 1.0 of XEP-0249: Direct MUC Invitations has been released.
This specification defines a method for inviting a contact to a multi-user chat room directly, instead of sending the invitation through the chat room.
The changelog is:
Per a vote of the XMPP Council, advanced specification from Experimental to Draft. (psa)
- fixed: auto DND when fullscreen window is open now goes off only if this fullscreen window is active
- fixed: some memory leaks
- fixed: slider value is now displayed in tooltip (eg. Priority)
- big improvement in handling different locations (resources) of a contact
- interpretation of “/me” command
- distinguish colors in chat: each contact has different color![]()
- bookmark editing, auto-join implemented
- chat window has now tray icon (not in taskbar if minimized)
- added User Activity information
- added Roster Exchange capability (receive contacts only)
- fix: sort in chatroom roster now by name
You may or may not have noticed that Jabbim offers a service called ‘VIP Facebook Transport’. This transport works as a gateway between Jabbim and Facebook Chat. No more chatting in the cumbersome web-based interface! Use your favorite desktop or mobile XMPP-compatible client to chat with your Facebook friends.
Until recently, this service has been only available for so-called ‘VIP’ users (those who support Jabbim service financially). From now on, the service is free for every Jabbim user.
For the best experience we recommend registering with the service using clients such as Jabbim or Psi, which make adding a large number of new contacts convenient. Otherwise, you might end up with many unnamed contacts you will have to rename manually.
Notes:
Version 1.0 of XEP-0198: Stream Management has been released.
This specification defines an XMPP protocol extension for active management of an XML stream between two XMPP entities, including features for stanza acknowledgements, stream resumption, and throttling notifications.
The changelog is:
Per a vote of the XMPP Council, advanced specification from Experimental to Draft. (psa)
Version 1.0 of XEP-0177: Jingle Raw UDP Transport Method has been released.
This specification defines a Jingle transport method that results in sending media data using raw datagram associations via the User Datagram Protocol (UDP). This simple transport method does not provide NAT traversal, and the ICE-UDP transport method sho
The changelog is:
Per a vote of the XMPP Council, advanced specification from Experimental to Draft. (psa)
Version 1.0 of XEP-0176: Jingle ICE-UDP Transport Method has been released.
This specification defines a Jingle transport method that results in sending media data using raw datagram associations via the User Datagram Protocol (UDP). This transport method is negotiated via the Interactive Connectivity Establishment (ICE) methodol
The changelog is:
Per a vote of the XMPP Council, advanced specification from Experimental to Draft. (psa)
Version 1.0 of XEP-0167: Jingle RTP Sessions has been released.
This specification defines a Jingle application type for negotiating one or more sessions that use the Real-time Transport Protocol (RTP) to exchange media such as voice or video. The application type includes a straightforward mapping to Session Descript
The changelog is:
Per a vote of the XMPP Council, advanced specification from Experimental to Draft. (psa)
Version 1.0 of XEP-0166: Jingle has been released.
This specification defines an XMPP protocol extension for initiating and managing peer-to-peer media sessions between two XMPP entities in a way that is interoperable with existing Internet standards. The protocol provides a pluggable model that enables t
The changelog is:
Per a vote of the XMPP Council, advanced specification from Experimental to Draft; also required inclusion of the creator attribute per list consensus. (psa)
Jabbim Team proudly announces the newest service – Jabbim robot Shorty. As you can guess from his name, his primary purpose is to shorten your long URL. This is very useful in Twitter and similar services. Try it and … you will love it!
Let's take a quick tour how to use him.
How to start with shorty
Shorty will speak with every XMPP/Jabber user (Google Talk included). Just add the contact shorty@jabbim.com to your roster. That's all. Really simple, huh?
How to use him to shorten long URL
Well, you will have to make really good friendship with him. Just kidding. Shorty's not suspicious. Simply send him your URL as a chat message and he will reply to you immediately.
History and usage of links
You read well, Shorty remembers your shortened URLs and statistics of usage. You will see how much the link is used and you can use the short URL again and again. Simply write him message with text „last“ and you will get the list (which is empty when you start using Shorty, by the way). That's very addictive!
How many people use Shorty?
The number of people depending on Shorty is growing day by day. Simply write him „stats“ message and he will praise himself.
That „jdem.cz“ URL is awful! How can I change it?
Don't worry, Shorty supports multiple „shortening engines“. You can freely choose the one you will use. List of currently offered engines is sent when you send „help engine“ message to Shorty. For changing an engine use e.g. „engine jabb.im“ message where jabb.im stands for shortening service. You can get currently used engine by simple „engine“ message sent to shorty.
Help, I'm lost!
Calm down, dusk is far enough. You can write „help“ message to Shorty or „help command“ where command stands for one of commands mentioned here. Or you can visit us in the multiuser chat (MUC) on jabber@conf.netlab.cz and we will help you.
Try Shorty, it's for free and it's cool!
Version 0.2 of XEP-0268: Incident Reporting has been released.
This specification defines methods for incident reporting among XMPP server deployments.
The changelog is:
Added more detailed information about the solution element; removed the suggestion element since the solution element can be used by both reporting entities and receiving entities; added notes about processing of incident reports by receiving entities. (mw/psa)
Version 2.0 of XEP-0199: XMPP Ping has been released.
This specification defines an XMPP protocol extension for sending application-level pings over XML streams. Such pings can be sent from a client to a server, from one server to another, or end-to-end.
The changelog is:
Per a vote of the XMPP Council, advanced status to Final. (psa)
Version 1.1 of XEP-0025: Jabber HTTP Polling has been released.
This document defines an XMPP protocol extension that enables access to a Jabber server from behind firewalls which do not allow outgoing sockets on port 5222, via HTTP requests.
The changelog is:
Per a vote of the Jabber Council, changed status to Deprecated. (psa)
Version 1.3 of XEP-0023: Message Expiration has been released.
This specification documents an historical protocol that was used to specify expiration dates for messages; this protocol has been deprecated in favor of XEP-0079: Advanced Message Processing.
The changelog is:
[See revision history] (psa)
Version 1.3 of XEP-0011: Jabber Browsing has been released.
This document defines a way to describe information about Jabber entities and the relationships between entities. Note: This document is superseded by XEP-0030: Service Discovery.
The changelog is:
[See revision history] (psa)
Version 1.4 of XEP-0003: Proxy Accept Socket Service (PASS) has been released.
This document defines a method for relaying media via proxies on the Jabber/XMPP network.
The changelog is:
[See revision history] (psa)
This release is the first after big changes due to metacontacts, so it contains mostly fixes:
And there is a new logo.
Version 2.0 of XEP-0138: Stream Compression has been released.
This document defines an XMPP protocol extension for negotiating compression of XML streams, especially in situations where standard TLS compression cannot be negotiated. The protocol provides a modular framework that can accommodate a wide range of compr
The changelog is:
Per a vote of the XMPP Council, advanced status to Final. (psa)
Version 1.0 of XEP-0237: Roster Versioning has been released.
This specification defines a proposed modification to the XMPP roster protocol that enables versioning of rosters such that the server will not send the roster to the client if the roster has not been modified, thus saving bandwidth during session establi
The changelog is:
Per a vote of the XMPP Council, advanced specification to Draft. (psa)
Version 1.4 of XEP-0091: Legacy Delayed Delivery has been released.
This specification provides historical documentation of the jabber:x:delay namespace, which has been deprecated in favor the urn:xmpp:delay namespace defined in XEP-0203.
The changelog is:
[See revision history] (psa)
Version 1.2 of XEP-0090: Legacy Entity Time has been released.
This specification provides historical documentation of the jabber:iq:time namespace, which has been deprecated in favor the urn:xmpp:time namespace defined in XEP-0202.
The changelog is:
[See revision history] (psa)
Version 1.4 of XEP-0022: Message Events has been released.
This document defines an XMPP protocol extension used to request and respond to events relating to the delivery, display, and composition of messages.
The changelog is:
[See revision history] (psa)
In the time of social networks, every person have multiple accounts in different services across the internet. Jabber supports transport to lot of them, so metacontact functionality makes an order in your roster.
Small number (clickable) indicates how many contacts is contained in metacontact.
Basically you have only one item for each person consisting from different internet accounts. Implementation in glu is very straightforward.
Just drag & drop one contact to antoher one and they are merged into one metacontact. If you wish to detach an account from metacontact, just open metacontact list dialog box using context menu.
Dialog box allows to remove contact from metacontact or set one contact / account as main. Main contact is always preferred way how to communicate with your friend, but if it is unavailable, first available account is used instead.
Metacontacts are based on xmpp standard, so you may leverage this in other jabber clients like gajim or jabbim.
Version 0.1 of XEP-0270: XMPP Compliance Suites 2010 has been released.
This document defines XMPP protocol compliance levels for 2010.
The changelog is:
Initial published version, copied and modified from XEP-0242 and XEP-0243. (psa)
Version 0.1 of XEP-0269: Jingle Early Media has been released.
This specification defines a Jingle application type for negotiating one or more sessions that use the Real-time Transport Protocol (RTP) to exchange media such as voice or video. The application type includes a straightforward mapping to Session Descript
The changelog is:
Initial version, copied from XEP-0167. (dc/psa)
Version 1.0 of XEP-0256: Last Activity in Presence has been released.
This specification defines a way to use the Last Activity extension in XMPP presence notifications.
The changelog is:
Per a vote of the XMPP Council, advanced specification to Draft. (psa)
We are happy to announce a new release of Openfire. The new release includes an important security fixe. Existing installations should update to this version. The complete set of changes can be found here.
Download Openfire from: http://www.igniterealtime.org/downloads/index.jsp
Enjoy!
Openfire Team
by Ignite Realtime (gaston@jivesoftware.com) at May 01, 2009 23:02
Version 0.1 of XEP-0267: Server Rosters has been released.
This specification defines a convention for trust between XMPP server deployments.
The changelog is:
Initial published version. (psa)
Version 1.8 of XEP-0124: Bidirectional-streams Over Synchronous HTTP (BOSH) has been released.
This specification defines a transport protocol that emulates the semantics of a long-lived, bidirectional TCP connection between two entities (such as a client and a server) by efficiently using multiple synchronous HTTP request/response pairs without re
The changelog is:
Removed secure attribute because it did not solve the problem it was intended to solve; added security consideration regarding link between connection manager and application server; changed "stanza" to "payload" for disambiguation with XMPP; clarified design objectives and relationship to similar technologies; corrected several errors in the schema. (psa/jm)
In a couple of nights I was thinking about improvements in the way of social services.
In antoher couple of nights I was doing it.
YouTube video player: If the YouTube link is recognized, there is a red “T” to start video in a sepaerate window. Link works as usual.
Activities: There is a new list of activities. It contains message changes, headline messages, mood changes and user tune changes. You can easily filter out different categories. If you use some “blog-style” transport and got regular messages instead of headline, just open context menu and use “Treat as Blog”. All messages will go to the Activities. Anyway, you can normally chat with this contact when you open a chat window.
Load older messages: If you wish to go back in time (because glu doesn’t load all messages from history), you can click on a button on the top of chat view – the arrow. Previous 80 messages is loaded int view.
Finally glu stores all contact settings like Hidden or Treat As Blog or Custom name on server instead od local database. It means you have same setting sfor all glu n your computers.
There were also some bugs fixed (avatar is now loaded even for contacts in offline state).
Version 0.2 of XEP-0266: Codecs for Jingle RTP Sessions has been released.
This document describes implementation considerations related to voice and video codecs for use in Jingle RTP sessions.
The changelog is:
Added information about the Dirac video codec. (psa)
Since now, you can use full text search over all message in one-to-one chats. It is really fast and the only limit is 1000 messages if the filter is too weak.
Another improvement makes “Now playing” feature more reliable and stable. You only need to download AMIP plugin into one of your favourite players. If you don’t want to publish this information, just disable AMIP.
| Winamp 2.x & 5.x |
| foobar2000 0.9.x |
| iTunes 4.7+, 5.x, 6.x, 7.x, 8.x |
| QCD 4.x & QMP 1xx |
| Winamp 3.x |
| foobar2000 0.8.3 |
Version 0.6 of XEP-0255: Location Query has been released.
This specification defines an XMPP protocol extension for querying a compliant server or service for information about the geographical or physical location of an entity.
The changelog is:
Defined registry; added nic type from list discussion. (psa)
Version 0.2 of XEP-0264: File Transfer Thumbnails has been released.
This specification defines a way for a client supply a preview image for a file transfer.
The changelog is:
Add paragraph in security section about protecting agains malicious thumbnail dimensions in offer. Fixed a typo. (ml)
Version 0.1 of XEP-0265: Out-of-Band Stream Data has been released.
This specification defines how to send parts of an XML stream over a direct connection between peers. This allows to send large stanzas or binary data without blocking the XML stream for other stanzas.
The changelog is:
Initial published version. (psa)
Version 1.0 of XEP-0263: ECO-XMPP has been released.
This specification defines best practices and protocol modifications that will reduce the energy consumption of XMPP systems and thereby help to save the planet.
The changelog is:
What do you do when it's 3a.m., you're sleepy, hungry, have hardly ventured your nose out of the door for the whole day, and someone pops up in your contact list who also happens to be to a serious Ubiquity hacker?
Why, of course you gently coerce him into helping you write your first Ubiquity command. About an hour of more sleep deprivation later, the im Ubiquity for Firefox/SamePlace has somehow come into existence (click image to enlarge):
The command is available through this GitHub gist and works on SamePlace development branch. (And yes, all it takes to publish a Ubiquity command on GitHub is pasting into a text area. You can even fork it with a single click and keep editing it on the web, without git. Sweet.)
Version 0.7 of XEP-0235: OAuth Over XMPP has been released.
This specification defines an XMPP extension for delegating access to protected resources over XMPP, using the OAuth protocol. In the language of OAuth, a User can authorize a Consumer to access a Protected Resource that is hosted by a Service Provider; t
The changelog is:
Changed protocol namespace from urn:xmpp:tmp:oauth to urn:xmpp:oauth:0 to conform to XMPP Registrar policies; clarified protocol flow and error handling; corrected examples. (psa)
Version 0.3 of XEP-0258: Security Labels in XMPP has been released.
This document describes the use of security labels in XMPP. The document specifies how security label metadata is carried in XMPP, when this metadata should or should not be provided, and how the metadata is to be processed.
The changelog is:
Add text regarding default bg/fg colors. Correct examples. (kdz)
Probably the feature that hooked people the most in Firefox 3 was the awesome bar. And for good reasons: what once required browsing through bookmarks, or re-googling faintly recalled keywords, or (heaven forbid) typing a whole URL, now only takes a bunch of keystrokes.
With that in mind, why not also cut on the amount of actions to perform when pinging friends, and make instant messaging a little more "instant"? Not a big deal if your whole contact list fits the screen and you can always reach everyone with a click, but for me and for most people I know, that time is long past.
So here's a touch of awesomeness for your contacts:

Goodies available through the development branch as usual.
Question: as this kind of minimal text-interface opens up a rich array of possibilities, what else do you imagine doing through it? Searching in previous chats? Adding and removing contacts? More?
Version 1.2 of XEP-0047: In-Band Bytestreams has been released.
This specification defines an XMPP protocol extension that enables any two entities to establish a one-to-one bytestream between themselves, where the data is broken down into smaller chunks and transported in-band over XMPP.
The changelog is:
[See revision history] (psa/jk)
Sometimes, the wisdom about “small, incremental changes” just has to fly out of the window, so last week I began landing the most drastic changes to SamePlace user interface since the Firefox extension contest.
Here's a teaser of 1) the dashboard, 2) the chat panel, 3) the stream panel (click to enlarge):
The dashboard is 100% XUL and extensions can easily add widgets. Its backbone is (unsurprisingly) a <widget>
element. So far the dashboard hosts the Account, Contacts and
Settings widgets.
Chats are the same as in the old interface but now they get their own panel and more screen space.
The stream panel aggregates direct messages and status changes from all contacts and services: Jabber, GMail, MSN/AIM/ICQ or whatever you're connecting to through server-side transports, Twitter (well, as soon as that's re-enabled in devel branch), and anything that will be available through local connectors. You can “mute” status changes from contacts you don't care about; direct messages get a catchier visual style so you don't miss them. It's written in XHTML, JavaScript, and jQuery.
The stream panel is where most interesting things interaction-wise will happen. We've barely scratched the surface.
If you want a test drive, install the package for the devel branch.
Do you like it? Do you hate it? Do you imagine a better way? I'd love to hear your thoughts.
Version 0.2 of XEP-0261: Jingle In-Band Bytestreams Transport has been released.
This specification defines a Jingle transport method that results in sending data via the In-Band Bytestreams (IBB) protocol defined in XEP-0047. Essentially this transport method reuses XEP-0047 semantics for sending the data and defines native Jingle me
The changelog is:
Minor changes to track modifications to XEP-0166; updated security considerations for consistency with other transport methods; added section on service discovery. (psa)
Version 0.2 of XEP-0260: Jingle SOCKS5 Bytestreams Transport Method has been released.
This specification defines a Jingle transport method that results in sending data via the SOCKS5 Bytestreams (S5B) protocol defined in XEP-0065. Essentially this transport method reuses XEP-0065 semantics for sending the data and defines native Jingle met
The changelog is:
Minor changes to track modifications to XEP-0166; updated security considerations for consistency with other transport methods; added section on service discovery. (psa)
Version 0.9 of XEP-0189: Public Key Publishing has been released.
This specification defines a method by which an entity can publish its public keys over XMPP.
The changelog is:
Required specification of an algorithm for elements with hashes; removed fingerprint in ; added sign request; added guidelines for key management; improved examples; changed namespace from urn:xmpp:tmp:pubkey to urn:xmpp:pubkey:0. (dm/psa)
Version 0.3 of XEP-0232: Software Information has been released.
This document specifies an extended data format whereby XMPP service discovery responses can include detailed information about the software application that powers a given XMPP entity for including detailed data about the in service discovery responses.
The changelog is:
Per Last Call feedback, removed icons for presence states; redefined the icon field to use media element per XEP-0221. (psa)
Version 0.1 of XEP-0262: Use of ZRTP in Jingle RTP Sessions has been released.
This specification defines a Jingle application type for negotiating one or more sessions that use the Real-time Transport Protocol (RTP) to exchange media such as voice or video. The application type includes a straightforward mapping to Session Descript
The changelog is:
Initial published version. (psa)
Version 0.2 of XEP-0247: Jingle XML Streams has been released.
This specification defines a Jingle application type for establishing direct or mediated XML streams between two entities over any streaming transport. This technology thus enables two entities to establish a trusted connection for end-to-end encryption o
The changelog is:
Adjusted text and examples to reflect Jingle-XTLS, Jingle-IBB, and Jingle-S5B; moved stream security to Jingle-XTLS; moved basic stream setup from XEP-0246 to this document; changed examples to use Jingle-IBB as the transport; clarified stream opening and closing as well as session termination. (dm/psa)
Version 0.9 of XEP-0234: Jingle File Transfer has been released.
This specification defines a Jingle application type for transferring files between two entities. The protocol provides a modular framework that enables the exchange of information about the file to be transferred as well as the negotiation of parameters
The changelog is:
[See revision history] (psa)
Version 0.4 of XEP-0215: External Service Discovery has been released.
This document specifies an XMPP protocol extension for discovering services external to the XMPP network.
The changelog is:
Revived the spec by popular demand; updated namespace to use XMPP URN; defined registry process and several initial entries. (psa/ml)
Now we have a lot of bugfixes and possibility to send and receive private messages from MUCs.
by steelspace (noreply@blogger.com) at February 13, 2009 17:46
Version 0.2 of XEP-0257: Client Certificate Management for SASL EXTERNAL has been released.
This specification defines a method to manage client certificates that can be used with SASL External to allow clients to log in without a password.
The changelog is:
[See revision history] (dm)
I tried to somehow use more of the free space left in the list and I decided to change the contact item layout. I think it makes it very compact but still focused on the avatar picture.
I also fixed some problems and bugs and added drag&drop support to the list.
by steelspace (noreply@blogger.com) at February 09, 2009 17:11