We are also pleased to announce that the PSES2013 (Pas Sage en Seine 2013, in Paris) has invited us to present Movim at this event! => You can meet us on the saturday 22th June from 6.30PM to 7.30PM
Xiph.org has just posted the second in its
series of videos on digital media concepts and techniques. It's
packed with information and demonstrations, and you're sure to learn a huge
amount. As an added bonus, it's hosted by Monty, the creator of Ogg Vorbis
(and many other amazing things). You couldn't ask for a more qualified
teacher.
We want to offer a transcript in the conference for the visually impaired and its translation to English. To do this, we need volunteers to make this work incredibly long and boring, that is impossible for a single person to achieve this goal.
Recently the jabber.org IM service has been the victim of massive and repeated denial of service attacks. The admin team strongly suspects that these attacks are related to the widespread and abusive use of jabber.org accounts by "customers" of KBot, a program for cheating at the DarkOrbit game. Even if the DoS attacks prove to be unrelated to KBot, the admin team has decided that use of jabber.org to communicate with KBot violates the jabber.org service policy. Although we are in the process of updating the service policy to more clearly define how this kind of usage is abusive, the dire nature of the current threat has forced us to take more immediate action. Therefore, we are disabling the accounts of every jabber.org user who communicates with KBot, and we have disabled new account registration to prevent further communication between jabber.org users and KBot. We do not take this step lightly, but given the current circumstances we have no other choice.
The previous DDoS attack has started again. As before, fallback measures are in place, but if your IM client doesn't handle DNS SRV records correctly then you might not be able to connect.
We have posted proposed changes to the policy that governs use of the jabber.org IM service. Details, links, and instructions for providing feedback can be found in our post to the juser@jabber.org email list, see http://mail.jabber.org/pipermail/juser/2012-August/006869.html.
We were able to completely restore service today. However, it is quite possible that the denial of service attack could be launched again at any time. If you were unable to connect during the outage, we recommend that you consider using a different IM client or reporting a bug to the developers of the IM client you use, since standard DNS fallback and XMPP reconnection methods should have been sufficient to keep you online after the first few hours of the attack.
Today we have experienced a distributed denial of service attack against the jabber.org IM service. Although the web server and email server are running fine, we have been forced to take the IM service offline until your (volunteer!) admin team has time to determine appropriate countermeasures. UPDATE 2012-08-12: We've made some DNS fixes and some clients are now able to connect.
The security certificate that we installed in December used a SHA-256 fingerprint, which theoretically is more secure but which some existing software can't handle yet. Therefore we have installed a corrected certificate using a SHA-1 fingerprint. If you've been receiving a certificate warning for the last few months, you shouldn't receive those anymore.
In response to several recent instances of abuse, we have disallowed non-ASCII characters in new accounts registered at the jabber.org IM service. This policy does not apply to existing accounts.
ejabberd 2.1.9, ejabberd 3.0.0-alpha-4, and exmpp 0.9.8 have been released, after several months of development. They contain a lot of bugfixes, improvements and some new features.
ejabberd 2.1.9
This release includes a lot of bugfixes and improvements. This is just a short list of them:
New SASL SCRAM-SHA-1 authentication mechanism (EJAB-1196)
ejabberd 2.1.7, and ejabberd 3.0.0-alpha-3, and exmpp 0.9.7 have been released, after a few months of development. They contain a lot of bugfixes, improvements and some new features.
If you have ejabberd running in a public server, please update it immediately: those releases contain a security fix that disables entity expansion completely to prevent billion laughs DoS attack (CVE-2011-1753).
ejabberd 2.1.7
This release contains many bugfixes, improvements and a few new features.
Smack 3.2.0 Beta has been released on February 3, 2011. It has been well over 2 years since the last release, but much work has been done to fix bugs and add new features. There are still other issues to be worked on, as there will always be, but it is time to start a new roadmap for Smack.
The starting point will be this release with the intent to produce a more regular release cycle. I will try to outline a roadmap for future releases in the near future based on the current set of issues, feedback within the forums and of course developer contributions.
Spark 2.6.0 RC1 has been released on November 17, 2010. It was a long period of silence since the last Beta 2 release and even longer since the latest Final release. But the work was continued, one project leader changed the other. There were a lot of changes in the code, both seen in the UI (color changes, additional options and buttons) and under the hood (lots of proprietary code replaced with open source analogs). Some new features were introduced, bugs fixed, and of course some new bugs introduced As i said, the work is constantly continued by 3-6 volunteer contributors. The plan is to release RC2 in December and then the Final release next year in January. Meanwhile we ask the community to try out RC1 and report about the issues in the forums.
There is no official changelog still, so i will just give a link to a list of 2.6.0 bugs in the tracker, 90% of them are fixed already.
Important note before upgrading! In 2.6.0 RC1 user's profile path has been changed to ..Username\Application Data\Spark (Windows XP), ..Username\AppData\Roaming\Spark (Vista/Win7) or $HOME/.Spark (Linux). If you want to use same preferences and have old history, copy user's profile folder to a new location and Spark will pick it up. Old location was just the ..Username\Spark. There is no automatic import option in the installer so far and it is not known if there will be one. So keep this in mind.
We are pleased to announce the release of XIFF 3.0.0! This major release includes many bug fixes, improvements, and features over the previous beta release, including Digest-MD5 support and removal of all Flex dependencies for pure AS3 project support. This release also includes a new class namespace (igniterealtime instead of jivesoftware). You can view the full change log here.
We have just released Tinder 1.2.2, which is a maintenance release. It fixes a number of bugs, features improved performance and has a number of new features.
Stanza acknowledgement is finally done, including representation in the GUI. You can see a short demonstration of the feature in the video below where I'm chatting with Matthew Wild, one of Prosody's main developers. He developed a module for Prosody that implements parts of Stream Management. This made my client side implementation much more easier to test.
The idea is simple: the status icon in the top left corner is replaced with a throbber animation, known to users from recent OSes and browsers, as long as there are messages that haven't been acked by the server.
Psi will at least request an ack after half a minute. However only if there's something to acknowledge for the server.
This week is mid-term evaluation of the Google Summer of Code projects. SCRAM support and stanza acknowledgement, which is the most important part of the Stream Management XEP, are both finished including GUI.
Stanza acknowledgement is finally done, including representation in the GUI. You can see a short demonstration of the feature in the video below where I'm chatting with Matthew Wild, one of Prosody's main developers. He developed a module for Prosody that implements parts of Stream Management. This made my client side implementation much more easier to test.
The idea is simple: the status icon in the top left corner is replaced with a throbber animation, known to users from recent OSes and browsers, as long as there are messages that haven't been acked by the server.
Psi will at least request an ack after half a minute. However only if there's something to acknowledge for the server.
This week is mid-term evaluation of the Google Summer of Code projects. SCRAM support and stanza acknowledgement, which is the most important part of the Stream Management XEP, are both finished including GUI.
We have just released Tinder 1.2.1, which is a bugfix release. Users of the AbstractComponent implementation that was added in 1.2.0 are advised to update.
I'm happy to announce the release of version 1.2.0 of Tinder. This new version brings interesting new features, a number of bugs fixes and general performance improvements. The complete set of changes can be found here. The blogpost that announced the new release can be found here
Version 0.3 of XEP-0227: Portable Import/Export Format for XMPP-IM Servers has been released.
This document specifies a file format for importing and exporting user data to and from XMPP-IM servers.
The changelog is:
Modified to include feedback received during the initial Last Call. Added sections for privacy lists and incoming subscriptions, as well as text on XInclude security. (wh)
Version 0.12 of XEP-0181: Jingle DTMF has been released.
This specification defines an XML format for encapsulating Dual Tone Multi-Frequency (DTMF) events in informational messages sent within the context of Jingle audio sessions, e.g. to be used in the context of Interactive Voice Response (IVR) systems. Note
The changelog is:
Corrected definitions and schema to make it clear that the code attribute contains one and only one character representing a DTMF tone. (psa)
Version 1.2 of XEP-0175: Best Practices for Use of SASL ANONYMOUS has been released.
This document specifies best practices for use of the SASL ANONYMOUS mechanism in the context of client authentication with an XMPP server.
The changelog is:
Provided more detailed recommendations regarding usage restrictions for anonymous users, including the concept of different deployment types; added note about the user/anonymous service discovery identity. (psa)
Version 0.7 of XEP-0168: Resource Application Priority has been released.
This document defines an XMPP protocol extension to indicate the presence priority of XMPP resources for applications other than standard XMPP messaging.
Version 0.3 of XEP-0197: User Viewing has been released.
This document defines an XMPP protocol extension for communicating information about the television shows, movies, or other videos that a user watches.
The changelog is:
Modified namespace in accordance with protocol versioning policies. (psa)
Version 1.1 of XEP-0136: Message Archiving has been released.
This document defines mechanisms and preferences for the server-side archiving and retrieval of XMPP messages.
The changelog is:
Moved JID matching text to a dedicated section and clarified matching rules; described implementation notes regarding server interpretation of archiving preferences and conversation tracking. (at/psa)
Version 2.1 of XEP-0085: Chat State Notifications has been released.
This document defines an XMPP protocol extension for communicating the status of a user in a chat session, thus indicating whether a chat partner is actively engaged in the chat, composing a message, temporarily paused, inactive, or gone. The protocol can
Version 0.1 of XEP-0274: Design Considerations for Digital Signatures in XMPP has been released.
This document discusses considerations for the design of Digital Signatures in XMPP,
including use cases and requirements. The document also discusses various ways XML Digital
Signatures could be used in XMPP.
The changelog is:
Initial published version as accepted for publication by the XMPP Council. (psa)
Version 0.1 of XEP-0273: Stanza Interception and Filtering Technology has been released.
This specification defines an XMPP protocol extension that enables a client to exercise control over the XML stanzas it will receive from the server by instructing the server to intercept and filter inbound stanzas.
The changelog is:
Initial published version as accepted for publication by the XMPP Council. (psa)
Version 2.0 of XEP-0203: Delayed Delivery has been released.
This specification defines an XMPP protocol extension for communicating the fact that an XML stanza has been delivered with a delay, for example because a message has been stored on a server while the intended recipient was offline or because a message is
The changelog is:
Per a vote of the XMPP Council, advanced specification from Draft to Final; also addressed a security concern about forged timestamps that was provided during the Call for Experience. (psa)
Version 2.3 of XEP-0077: In-Band Registration has been released.
This specification defines an XMPP protocol extension for in-band registration with XMPP-based instant messaging servers and other services hosted on an XMPP network (such as groupchat rooms and gateways to non-XMPP IM services). The protocol is extensibl
The changelog is:
Clarified that fields for "first" and "last" in fact always represent given name and family name, respectively. (psa)
Version 2.0 of XEP-0202: Entity Time has been released.
This specification defines an XMPP protocol extension for communicating the local time of an entity, including the time in UTC according to the entity as well as the offset from UTC. The time format itself conforms to the dateTime profile of ISO 8601 defi
The changelog is:
Per a vote of the XMPP Council, advanced specification from Draft to Final. (psa)
Version 0.4 of XEP-0220: Server Dialback has been released.
This specification defines the Server Dialback protocol, which is used between XMPP servers to provide identity verification. Server Dialback uses the Domain Name System (DNS) as the basis for verifying identity; the basic approach is that when a receivin
Version 0.4 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:
Update label catalogs to include user input selector. (kdz)
Version 0.3 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:
Major update to make Jingle S5B inherit more features from ICE and ICE-TCP. Added priorities and candidate identifiers. Renamed streamhost element to candidate element. Updated candidate selection to use priorities, and it is now required for both clients to send a candidate-used or candidate-error notification. Defined type attribute to differentiate between various kinds of candidates. More clearly described how S5B negotiation is completed, including an activated notification from responder to initiator when the candidate used is a proxy. Noted reuse of fast-mode methodology from S5B optimization specification. Because of incompatibilities with the previous version, changed the namespace to urn:xmpp:jingle:transports:s5b:1. (dm/psa/jk)