With great pleasure we want to announce a new public service brought to you by yaxim.org - the yax.im (read: Yaks’ IM) public XMPP server.
To register with it, open your XMPP client (e.g. yaxim), choose a JID of your liking that ends with @yax.im, like firstname.lastname@example.org and activate “Register new account”.Server Details
The service is running the recent Prosody 0.9 XMPP server written in Lua. Many thanks go to the dedicated Prosody developers.
yax.im is reachable via IPv4 and IPv6 (if your client does not support SRV resolution, use yaxim.boerde.de as the server name, port 5222) and is hosted in Berlin, Germany. It features several extensions important for mobile clients:
- XEP-0198: Stream Management for mobile client connections
- XEP-0199: XMPP Ping set to ping you every 5 minutes, with a 2 minutes timeout
- XEP-0280: Message Carbons for keeping multiple parallel client connections in sync
Certain JIDs are barred from registration (you need to specify at least two letters, and test and admin, among some others, are disallowed).Transports and Services
So far, yax.im offers a built-in XEP-0045: MUC component at chat.yax.im with the yax.im service and yaxim app support chat room email@example.com. Feel free to bother us with any issues you might have with either the app or the server.
The server is not offering any transports. This might change if a transport implementation for XMPP or any proprietary service appears that has a credible security audit.
In the meantime, you are free to use whatever external transport you are used to.
Timothée and Vincent will be at the Cité des sciences, in Paris, to give a conference about the project. Named “Movim, réseau social et décentralisation”, you’ll be able to see the last version of the software and have a look on the decentralization advantages.
The podcast will be published as soon as possible.
Joachim is in the US (San Francisco specifically) and would love to get together with anyone from the XMPP and/or IoT community!
His original goal was to attend the Doing IoT with XMPP meetup. Either way you should poke him on the members@ mailing list to at least find a pub and raise a pint or three!
The XSF held it’s annual meeting the 29th of October and we voted for Council and Board
I’m happy for two reasons, first that my friend and coworker at &yet was elected to the Council and that I was again elected to the Board.
With all of the activity in the web space and all of the people now realizing that the internets need security and that XMPP is already a federated, secure suite of protocols - it will be a very busy year I think.
Peter Saint-Andre has created a Manifest for others to join, debate and discuss about a plan for upgrading the XMPP network to always-on, mandatory, ubiquitous encryption.
To quote Peter:
In short: we owe it to those who use XMPP technologies to improve the security of the network (and thanks to Thijs Alkemade, we now have better ways to test such security, using the newly-launched “IM Observatory” at xmpp.net). Although we know that channel encryption is not the complete answer, it’s the right thing to do because it will help to protect people’s communications from prying eyes.
Every year the members of the XSF get together to vote on the current quarter’s new and renewing members and to also elect who will become members of the Technical Council and who will server on the Board of Directors.
This year that meeting was held on the 29th of October, 2013 and Alexander has recorded the details in a on the XSF site.
The 13th XSF Technical Council for the 2013/2014 term are:
- Matthew Wild
- Lance Stout
- Kevin Smith
- Tobias Markmann
- Philipp Hancke
The 2013/2014 Board will consist of:
- Dave Cridland
- Ralph Meijer
- Laura Gill
- Mike Taylor
- Simon Tennant
Please congratulate them if you run across any but also please help us make this another great year for the XSF.
Earlier this year we announced the open source Pushpin project, a server component that makes it easy to scale out realtime HTTP APIs. Just what kind of scale are we talking about though? To demonstrate, we put together some code that pushes a truckload of data through a cluster of Pushpin instances. Here's the output of its dashboard after a successful run:
Before getting into the details of how we did this, let's first establish some goals:
- We want to scale an arbitrary realtime API. This API, from the perspective of a connecting client, shouldn't need to be in any way specific to the components we are using to scale it.
- Ideally, we want to scale out the number of delivery servers but not the number of application servers. That is, we should be able to massively amplify the output of a modest realtime source.
- We want to push to all recipients simultaneously and we want the deliveries to complete in about 1 second. We'll shoot for 100,000 recipients.
TechNet is an annual event organised by AFCEA Europe (Armed Forces Communications & Electronics Association) to highlight IT developments in the military sector. TechNet 2013 was held on 23/24 October at the Lisbon Congress Centre. This year the focus was on connecting coalition forces and bringing high-end IT capabilities to deployed forces using mobile devices.
Normally we attend these events to listen to the talks and network with other attendees. This year we were invited by our friends at HP Autonomy to share their stand for a joint HP/Isode demonstration showing Autonomy analysis of M-Link chat files.
M-Link can provide chat log archives, which can be configured to audit all messages sent either by user, by MUC room, or both. The archives are stored in an XML-like syntax on disk.
The TechNet demonstration showed how a link between M-Link’s chat log files and Autonomy could enable the analysis of real-time chat data to search for developing patterns, sentiment and intention.
Both Isode and HP Autonomy will be showing this demo at future events.