The final 5.1.0 for the Tigase XMPP Server is around the corner. While we are running the last tests you can grab Beta4 build which is most likely the same exact code we will publish as the final new version.....
Please note, the download section has been moved to our project tracking system which hosts all our projects and is based on Redmine.
As usually any comments are very welcomed.
Already in my career I've experienced enormous passion, burnout, extraordinary dedication to my team and projects, and depression. I'm sure many others have as well. Has it always been this way with technology? I often wonder if this rollercoaster is necessary, healthy, or normal.
I recently saw a recommendation for Soul of a New Machine, which tells the story of a team of engineers at Data General who built a new 32-bit computer in the late 1970s. The book is fascinating. Thirty year later, many of its descriptions of the project and the way the team worked and was treated could apply to any modern project.
The plot summary will no doubt sound familiar to you: A team of mostly young, mostly male engineers works grueling hours to build something amazing in too short an amount of time. They succeed, albeit a bit over their original schedule. Despite the project's commercial success, the team is denied both recognition and financial rewards and many end up leaving the company. Almost all of them ultimately enjoyed it and would (and did) do it again.
There were many pieces of this story that resonated with me.
On overworking Tom West, the manager of the team in the book, says:
That's the bear trap, the greatest vice. Your job. You can justify just about any behavior with it. Maybe that's why you do it, so you don't have to deal with all those other problems.
Why deal with the unpredictable world, when the controllable world of creation is available? It's code as escapist drug, and I love to get high on it. Mundane things like cleaning my house, and more serious ones like taking care of my health, are all easy to avoid while fixing bugs or starting a new project.
It's both possible and important to find a balance.
The team's secretary, who was much more than her title suggests, suffered and succeeded with the rest of the team. Even she says:
I would do it again. I would be very grateful to do it again. I think I would take a cut in pay to do it again.
Even as I recover from projects that burned me out, I am constantly thinking about how to do new ones. In fact, while I'm doing any project, I'm already thinking about doing another. This sounds like drugs again. But they are good drugs.
The book describes how some team members tormented the lone female engineer. This is something that still happens today, and it's terrible. And people then wonder why there are so few women in our industry.
In addition to that, at the end when they hand out the peer awards, their award to the woman was for putting up with them, not for any of her actual accomplishments.
Betty Shanahan was that lone woman, and it looks to me that she deserved more than just an award for thick skin. She's the CEO of the Society of Women Engineers, and she was "a member of the design team for the first parallel processing minicomputer and manager of hardware design for subsequent systems." She later moved to the business side of technology, and I wonder if that had anything to do with her having to put up with the Eagle team's harassment.
Often we judge things by their properties, but one can also rightly judge something by how it is made. Shoes made from child labor are less good than those made in other ways.
Kidder, the book's author, discusses this:
In The Nature of the Gothic John Ruskin decries the tendency of the industrial age to fragment work into tasks so trivial that they are fit to be performed ony by the equivalent of slave labor. Writing in the nineteeth century, Ruskin was one of the first, with Marx, to have raised this now-familiar complaint. In the Gothic cathedrals of Europe, Ruskin believed, you can see the glorious fruits of free labor given freely. What is usually meant by the term craftsmanship is the production of things of high quality; Ruskin makes the crucial point that a thing may also be judged according to the conditions under which it was built.
By this kind of measure, is the work many teams do good? Is the Eagle computer that Tom West's team built really a success since the team worked much overtime, suffered divorces and other problems, and in the end received little to no reward?
I think it's time for entrepreneurs and workers in our industry to demand better. Our outputs will be better if they are made sustainably, and not just by the measure above. In retrospect, maybe the reviewers of LA Noire should have taken into the account the trials of its developers; it certainly would not have fared well.
I want to hire resourceful people. I want to describe a general outline of a design and not have to describe it in intricate detail in order for them to build it.
It turns out that this is critical for happiness. If we're told exactly how to do something, it takes much of the creativity and fun out of the work.
Engineers are supposed to stand among the privileged members of industrial enterprises, but several studies suggest that a fairly large percentage of engineers in America are not content with their jobs. Among the reasons cited are the nature of the jobs themselves and the restrictive way sin which they are managed. Among the terms used to describe their malaise are *declining technical challenge; misutilization; limited freedom of action; tight control of working conditions*.
You must trust those you work with to be resourceful. If you don't trust them, you will end up micromanaging them into unhappiness, and you will also remove their valuable creative input from your product.
There is a balance to be struck with feedback. The Eagle engineers thought that the managers didn't appreciate their efforts, but in reality, some of this was them trying to stay out of the way. Kidder asked the Tom West's boss:
Had the Eagle project always interested him or had it grown in importance gradually?
"From the start it was a very important project."
Was he pleased with the work of the Eclipse group?
"Absolutely!" His voice falls. "They did a hell of a job."
But some members of the team felt that they had been rather neglected by the company.
"That doesn't surprise me," he says. "That's frequently the case. There's often a conflict in people's minds. How much direction do they want?"
I've had this same issue with investors as well. You don't want them to meddle with your company or your product, but you also want their advice and guidance. It's possible to go too far in either direction, but mostly you hear about stories where investors meddle too much. I personally think it's probably better to err on the side of too little help than to end up with too much meddling.
Even thirty years ago, the VCs had a bad rap. Tom West was asked in a Wired article years after the book's publishing why he stayed at Data General until he retired:
"You could do new products and companies within the company, rather than shag some venture capitalist and kill yourself for five years." To be an entrepreneur, he says, "you have to be interested in networking, even with fools."
This is another reason why I would prefer to bootstrap companies if at all possible.
Tom West ended up working on many interesting projects at Data General, but ultimately, none of them got the support or recognition they deserved. The other members of the Eagle team spread out and started or worked for new companies, and in general seemed much happier.
In the end, it's both a fascinating tale of heroism and creativity and a saddening tale of undervalued and underpaid engineers. I am both emboldened to keep following my passions and more mindful of its dangers. My troubles are not unique - not even modern. Thirty years after this book was written, I feel like it could have been written yesterday.
by Jack Moffitt (jack@metajack.im) at January 20, 2012 10:20
Critical Capabilities for Enterprise Instant Messaging and Presence (David Mario Smith / January, 10, 2012) report by leading analyst firm, Gartner, evaluated in 4 use case categories for enterprise IM & presence.
7 critical capabilities like chat, presence, clients, archiving, interoperability and integration, administration and conferencing help to assess the different vendors.
ProcessOne was recently evaluated in the enterprise IM and Presence category in an independent analysis, published on January 10, 2012, by leading industry analyst firm Gartner. This study complements other studies by Gartner such as the MarketScope for Enterprise IM and Presence published on July, 5, 2011.
As more enterprises use real-time messaging to ease collaboration internally and externally between employees and customer relationship, business processes are requiring more flexibility and real-time interaction, especially while employees, applications and connected things are fully mixed together.
A business environment, where all employees are connected through various devices, especially smartphones, is challenging for enterprises. Push notification tends to become extremely important as it enables processes to synchronize with employees again and promote real-time discussion and decision. This is why companies need seamless real-time chat and push interaction and it's great to see the top analyst firm rate and define ProcessOne in this way.
Twitter sees Google's latest Google+ feature, integration into Google search, as anti-competitive, and it probably is. However, it brings to the surface some real issues with the future of search and of data.
Twitter's argument:
We're concerned that as a result of Google's changes, finding this information will be much harder for everyone. We think that's bad for people, publishers, news organizations and Twitter users.
Google's response was:
We are a bit surprised by Twitter's comments about Search plus Your World, because they chose not to renew their agreement with us last summer (http://goo.gl/chKwi), and since then we have observed their rel=nofollow instructions.
People have been digging into the semantics of nofollow (see Danny Sullivan and Luigi Montanez), but there is a much bigger issue.
Google and other established and up-and-coming search engines have no real way to include lots of data in their index. It's easy to imagine that the lack of access to Twitter and Facebook data was a motivator for Google+ in the first place.
Lots of sites now generate enough data that it is unrealistic to crawl them. For example, Youtube has more new content every day than they allow anyone to crawl. Twitter is essentially the same. This means there is no way to index this data without special arrangements with the provider. Twitter has closely guarded their firehose of data, but at least they have some mechanism to obtain it. Youtube, as far as I am aware, has no such mechanism.
My team and I ran into this problem head on trying to build Collecta, a real-time search engine. Access to the data was a primary blocker for many features and product ideas, and over the too short life of that company, access became significantly more difficult, not easier.
Google can build an effective search, even a real-time one, for Youtube, but no one else can. Twitter can build search for their data, but few others can, and their data access policies can and do change on a whim.
If Google believes that microblogging data will improve their search product, then a reasonable strategy to obtain that data is to try and build their own microblogging service to generate it. I can't fault Google for trying. If I thought Collecta could have effectively competed against Twitter for their audience, I would certainly have attempted that as well.
Google, Twitter, Facebook and others are hoarding silos of otherwise public data. Not only is this artificially limiting the features of their products, but it squashes the potential for new and exciting search applications. The search services that have sprung up are limited to your own data, aggregate results from service-specific search APIs, exist at the mercy of data providers, or make do with a tiny subset of the data. I don't think Google could have built their own search engine if the Web were similarly hostile.
One could argue for requiring these bits of data to be openly available, but unlike the data of the past, this data is expensive to publish and consume. Most of these services may not even have a mechanism to publish the data, even internally. Simply receiving the Youtube or Twitter firehoses (and not counting video or image media) would require significant engineering effort, and the rate of data generation is only accelerating.
I think we must push for open access to data, even if it is costly. These data wars benefit very few. If things don't change, the future of search is dark.
by Jack Moffitt (jack@metajack.im) at January 12, 2012 10:12
The Comprehensive Erlang Archive Network brings Erlang community a complete packaging system and a simple way to manage several installations of Erlang.
CEAN 2.0 comes with Erlang R12B-5, R13B04, R14B04, and R15B, for Linux/Mac/Windows.
More than providing binary packages, now we provide an Erlang development/build/package framework.
This way you can even build any other Erlang version you need and build your own repositories.
The aim is to reach a production quality level repository of auto-generated Erlang packages, using a cross-platform framework.
The most valuable CEAN 2.0 features are:
See more on CEAN web site (cean.process-one.net).
Please post any issue or feature request on our Ticket Tracker.
Use the forum for any kind of request or help.
MatriX XMPP library for iOS and Android is in Beta status now. Both versions are based on MonoTouch and Mono for Android from Xamarin.
Using this technology you can easily port your existing MatriX based c# XMPP apps to iOS and Android and resuse most of your existing code and business logic.
When you are interested in Beta testing then please contact us.
As you’ll be aware if you’ve been following the XSF’s mailing lists and chatrooms, FOSDEM 2012 is coming, and that means it’s also time for the XMPP Summit 11.
A rough timetable is:
Friday 3rd February – XSF Interop Day (Hosted by Cisco in Diegem)
The testing to be done is being organized as I type on our mailing list at interop@xmpp.org
Saturday 4th February – XMPP Realtime Lounge at FOSDEM, XMPP Talks at FOSDEM
If you’ve some fun project to demo at our stand, the Realtime Lounge, or an exciting talk about XMPP and related topics, we still have speaking slots available – tell us your idea on the summit@xmpp.org mailing list. Talks start at 11:00, and run through to 19:00.
Sunday 5th February – XMPP Realtime Lounge at FOSDEM
More demos of unusual and inventive uses of XMPP throughout the day at the Realtime Lounge.
Monday 6th February – XMPP Summit 11 (Hosted by Cisco at Diegem)
Technical talks and discussion for the participants of the standards@xmpp.org mailing list.
All this, and evening entertainment too – on Friday, there’s the FOSDEM Beer Event (Look for the XSF logo projected onto the ceiling to find us there!), and on Saturday, we’ll have the XSF Dinner – free to XSF Members, and sponsors are always welcome – and very popular on the night!
If you’re coming, join the summit@xmpp.org mailing list and make yourself known – we’re busy organizing hotel deals, speakers, demos, and so on there, so you’ll be able to get the best deals we can wangle and be ahead of the game.
See you all there!
After many years building the reference XMPP chat server, we are now expanding to push as a platform, for ubiquitous realtime notifications.
First and foremost, thank you everyone, customers, partners for your trust and support during the past years. We would like to assure you that it has been well placed.
Look at what we have accomplished together so far, in your behalf:
We are now building a much more ambitious platform, the ProcessOne Push Platform, which intends to provide a self service, large scale, over-the-web notification platform. The platform is powering one of our new projects, that would change the experience people consume news, Upik, thanks to realtime personalized distribution. Especially in 2012 with the Olympics, the elections,...
If you want to learn more about ProcessOne Push Platform, you can join the live tutorial we will demonstrate on the 9th February (Webinar registration link).
2011 was the year of the emergence of group messaging, like TextOne, our prediction in 2012 is the year of push, as an ubiquitous realtime notification stream, coming at you, on your smartphone, computer...
2012 is going to be pretty exciting for us and we wish to build even more exciting new projects with you all.
We wish you all a happy new year, a great 2012!
Credits: Gare de Strasbourg, by Alexandre Prévot, under CC by-sa 2.0
We are pleased to announce the bugfix releases of ejabberd 2.1.10 and exmpp 0.9.9.
This release includes a few bugfixes and improvements. This is just a short list of them:
* Erlang/OTP compatibility
- Support Erlang/OTP R15B regexp and drivers (EJAB-1521)
- Fix modules update in R14B04 and higher
- Fix modules update of stripped beams (EJAB-1520)
* XMPP Core
- Fix presence problem in C2S after first unavailable (EJAB-1466)
- Fix bug on S2S shaper when TLS is used
- Prevent overload of incoming S2S connections
* XEPs
- BOSH: Get rid of useless mnesia transaction (EJAB-1502)
- MUC: Don’t reveal invitee resource when room informs invitor
- Privacy: Activate “Blocked Contacts” to current c2s connection (EJAB-1519)
- Privacy: Always allow packets from user’s server and bare jid (EJAB-1441)
- Pubsub: Add hooks for node creation/deletion (EJAB-1470)
- Shared Rosters: support groupname@vhost in Displayed Groups (EJAB-506)
- Vcard: Fix error when lowercasing some search results (EJAB-1490)
Check the Release Notes for a more complete list of changes: Release Notes for ejabberd 2.1.10
If you upgrade from ejabberd 2.0.5 or older, read carefully the release notes of ejabberd 2.1.0 too, because there were several changes in the installation path and the configuration options.
The list of solved tickets since the previous version is available on ProcessOne bug tracker: http://redir.process-one.net/ejabberd-2.1.10
ejabberd 2.1.10 is available as source code package and binary installers for Linux 32 bits, 64 bits, Mac OS X Intel, and Windows: http://www.process-one.net/en/ejabberd/downloads
exmpp home page: http://support.process-one.net/doc/display/EXMPP/ or easier to remember: http://exmpp.org/
Download exmpp 0.9.9 source code package from: http://download.process-one.net/exmpp/
You can also check the ProcessOne Labs page: http://www.process-one.net/en/labs/
Dear Community,
after some more weeks of testing, debugging and developing, we would like to ask for your support and publish the first beta of Spark 2.7.0. Ultimately, we would like to move Spark to Java 7, but that is currently not implemented via the installers. This will change in January after an update to the lastest version von Install4j provided by ej-Technologies.
You can find the nightly build for Windows here: http://bamboo.igniterealtime.org/browse/SPARK-INSTALL4J-543/artifact/JOB1/Instal l4j
About Java 7: Spark 2.7.0 will run with Java 7. Please interchange the bundled JRE (located at Spark-install-folder\JRE) against a Java 7 JRE or use the installer named spark_2_6_3_12555_online.exe and install Java 7 as default on Windows. Using Java 7 will stop Spark from stealing the focus, when a new message is received.
Important Note: Oracle has introduced a bug in Java 1.6.0 u 25-27 that prevents Spark from closing automatically during the log-off on the Windows plattform. This is not Spark related. This affects all users that install the Spark version without an included JRE.
About file transfer: Spark 2.7.0 beta 1 is fixing an big bug with file transfer. Spark 2.6.x has an programmatic error that was making IBB file transfer very unstable. Tim Jentz deserves a big credit for finding this after weeks of debugging. Great job Tim!!!
Spark 2.7.0 will also move to a standard implementation for IBB file transfer. As a result of moving to the standard IBB implementation, you may have issues with transfer between Spark 2.7.0 and Spark 2.5.8 on IBB. This is an unavoidable result of obeying the standard. IBB is the fall back implementation, if Bytestream is not an option. Hence IBB is not the regular transfer method as it is much slower than Bytestream.
About plugins: There were large scale changes in the way Spark is dealing internally with plugins/extensions. All Plugin developers are kindly ask to review, if their plugins are still working. This applies also to Fastpath. Feedback regarding issues with this are highly appreciated.
About GUI: The Spark developers are only supporting JTattoo Luna. There are several reports that other skins are not working properly. This applies especially to Substance. If you are experiencing any GUI bug, please check if JTattoo Luna is also having this issue and report it.
As a general statement, I would urge all professional users to use the customizing options of Spark to get rid of Substance in corporate environments. The dev team may ultimately decide to remove Substance for 2.7x in a future release.
About Mac and Windows7 64 bit: The next Mac release is NOT secured. We are looking for a developer who can provide a Mac beta release. The integration to Windows7 64 bit is ok, but the flashing notification in the tray may or may not work. A tester and developer (MS C++ Code) for this is also needed.
The change log for this beta is:
SPARK-1465 Checkboxes appear bigger then normal since the jtattoo update
SPARK-1464 When user accepts group chat invitation, status is always online
SPARK-1460 No group context menu on a right click
SPARK-1459 Update to the latest JTattoo version (Nov 2011)
SPARK-1452 If conferences tab is hidden, then Fastpath tab is hidden also
SPARK-1451 Vcard popup is not always showing up on mouse hover
SPARK-1450 When network connection is lost, chat window cannot be closed
SPARK-1449 UNC Path does not link to folder
SPARK-1445 Selecting 'Start a chat' in a group chat room opens an incomplete chat window
SPARK-1444 Subscription dialog shows the id value instead of the nickname
SPARK-1443 Privacy plugins cannot be accessed if we log into Spark through the IP address of the server
SPARK-1465 Checkboxes appear bigger then normal since the jtattoo update
SPARK-1464 When user accepts group chat invitation, status is always online
SPARK-1460 No group context menu on a right click
SPARK-1459 Update to the latest JTattoo version (Nov 2011)
SPARK-1452 If conferences tab is hidden, then Fastpath tab is hidden also
SPARK-1451 Vcard popup is not always showing up on mouse hover
SPARK-1450 When network connection is lost, chat window cannot be closed
SPARK-1449 UNC Path does not link to folder
SPARK-1445 Selecting 'Start a chat' in a group chat room opens an incomplete chat window
SPARK-1444 Subscription dialog shows the id value instead of the nickname
SPARK-1443 Privacy plugins cannot be accessed if we log into Spark through the IP address of the server
SPARK-1442 JabberVersion.java uses hardcoded value "Spark IM Client" for version name
SPARK-1441 ContactItem in shared group - right click popup menu performs copy when move is selected
SPARK-1440 Bug in ConferenceUtils.java that can break smack communication
SPARK-1439 Plugins are loaded in random order - plugins with no dependency has to be loaded first
SPARK-1438 Avatars are not scaled in user login/logout notification dialog
SPARK-1437 Bug in PrivacyManager that can break smack communication
SPARK-1429 Update French translation
SPARK-1427 Default Appearance/Colors cannot be overwritten through plugin;Group-Chat colors are hard-coded
SPARK-1423 typo error in LayoutSettings.java
SPARK-1422 persist vcard may throw file not found exception when jid is empty
SPARK-1421 Application version and application name are hardcoded
SPARK-1420 The messages in the set status message window is not getting deleted
SPARK-1419 Chat room configuration shows wrong roles for which presence is broadcast
SPARK-1418 Update simplified Chinese translation
SPARK-1414 Chat window is not flashing when receiving new message on Windows 7 64 bit
SPARK-1413 Update build.xml to check for Java 7
SPARK-1411 Sometimes file transfer indication is not updated on the receiving side
SPARK-1408 Remove "#" character next to Accounts button on the login screen
SPARK-1405 Improved last activity recognition
SPARK-1403 Enhance ability to extend core classes like ContactItem, ContactGroup, etc through plugin
SPARK-1400 Update to latest version Exe4J
SPARK-1381 Group Chat - Actions/Start a conference menu: propose bookmarked room (if any) instead of adhoc (random) room name
SPARK-1379 Support for XEP-0147
SPARK-1326 Make tabs position optional: TOP or BOTTOM; make search input appearance optional
SPARK-1324 SparkToaster showing avatars in real size
SPARK-1313 Enhance ability to overwrite spark properties values through plugin
SPARK-1215 Log out doesn't log out, it shuts down spark
SPARK-891 Typing notifications would be easier to see if also displayed near typing area
The beta release also includes a new Smack library that is based on Smack 3.2.1 plus the following bugfixes:
SMACK-362 smack throw NoSuchElementException if the muc#roominfo_subject has no values
SMACK-354 Provide milliseconds in timestamp colum debugwindow
SMACK-353 Thread leak in the FaultTolerantNegotiator
SMACK-350 Bytestream is not working in Spark 2.6.3 from XP to W7
SMACK-349 Smack's IBB sends too much data in a packet
SMACK-348 Documentation error - broken link
SMACK-346 Bug in return code for rejection handling in FileTransferManager
SMACK-343 Make Smack jar an OSGi bundle.
SMACK-338 IBB filetransfer doesn't work as expected
SMACK-336 There is an empty element in a SASL response
SMACK-335 Need to set file size and name for outgoing file transfer from input stream
SMACK-324 Investigate SASL issue with jabberd2 servers
SMACK-322 NPE in XMPPConnection
SMACK-263 Set file info in all send* methods
Expect a second beta in the first quarter 2012 that will include the latest final release of Smack
Please report issues in the Developer Forum
by Ignite Realtime Blog (communityadmin@igniterealtime.org) at December 23, 2011 19:46
We've created a new personalized push inbox for your iPhone and iPod Touch. We've understood that people want today is real time news.
Right after we powered on our smartphone, we are immediately connected. We are calling that, to be instant-on. From waking up, taking a bus, waiting in line, eating for lunch, having a meeting and going to sleep. We are always at a fingertip of a breaking news, an important email, an amazing post or even an incredible tweet. And we do not want to miss them. But we just want to be alerted personally in a simple manner so we can interact right after, by sharing, calling, posting, tweeting, whatever it is but reacting fast.
With that in mind, we've created a new personalized push inbox for your iPhone and iPod Touch. We've understood that people want today is real time news. That's why we've combined personalization with smartphone and identity with push capability into one single inbox so we can solve the paradigm of living news in real time.
| Upik.it (You pick it) | = Personalized (source selection) |
| + Push (Instant On) | |
| + Inboxes (Aggregated easy-to-read views) | |
| + Identified (You only) | |
| + Multi-device (Your 360° mobile environment) |
So to summarize, it's all about your news coming at you, using the notification capabilities of your iPhone or iPod Touch.
We've designed Upik to be easy to use, fast and remarkably efficient for everyone who is testing it for the very first time. There is still a lot to do to improve the overall experience. But bear in mind that we are fully committed to shaping a new smart content delivery to help you reduce your information overload.
We've added an inbox and a catalog so you can perform actions on your notifications
 Get alerted to new notifications |
 Scroll down your inbox |
We've understood that you want real time news coming on your iPhone, with no effort and no need to browse the web. That's why we've included time-saving features
 Instant-viewed notification |
 All your sources in a split view |
We've designed Upik app to help you organize your notification flow so you just use your inbox like a "rubik's cube" and never miss key notifications
 Sorted view by source |
 Read your notification later |
We hope the Upik app makes you feel the notification differently and joins the brave new world of push content distribution. It is available in the AppStore today and works on all devices running iOS4.3+.
We are still in private beta so ask for an invitation on Upik.it launch site: http://launch.upik.it/.
For more information, check out our support center or contact us at Upik@process-one.net
Enjoy yourselves and give us your feedbacks on social networks.
The Upik team
Dear Community!
Another year has passed for this open source project and various developers have contributed significantly to nearly all of our projects. We were able to finally release Openfire 3.7 and Spark 2.6.3 under Apache 2.0 license. The most important Smack library has also seen several releases and last but not least the good old instant messaging gateway Kraken returned to us. Some great innovations were presented like SparkWeb/Redfire, Websocks and Candy. I really would like to thank all developers involved by contributing code and all users and system admins that went through this year. A very special thank you goes to Daryl Herzmann who keeps the servers healthy and Wroot for outstanding work in the forum. I would also like to single out Guus der Kinderen for his insights in Openfire architecture and the release of Openfire 3.7.
Merry Christmas to all of you and a happy, healthy and sucessful 2012
by Ignite Realtime Blog (communityadmin@igniterealtime.org) at December 23, 2011 07:04
USA Today anticipates move to realtime press.
USA Today is really aware of the increasing importance of realtime for press. They decided to distribute iPad and iPhone to journalist as a way speed news generation and gathering process.
At ProcessOne, we have been building since months the needed tools and infrastructure to empower the move to realtime newswire, from news production to news consumption.
The infrastructure is powered by ProcessOne Push Platform (P1PP) and the end user facing tools is called Upik, currently in private beta. Do not hesitate to contact us (upik at process-one.net) if you want to join the beta.
We are thus very happy to see this good move in the press and are already in good position to make the news realtime.
Leak shows Gannett stockpiling thousands of iPhones, iPads for journalists
http://www.appleinsider.com
This are great news for the XMPP community. Microsoft has added XMPP client support to their Windows Live servers. You can read the announcement here.
Microsoft does not support any of the mandatory SASL mechanisms SCRAM, DIGEST-MD5 and PLAIN. Instead they have implemented their own X-MESSENGER-OAUTH2 SASL mechanism. This means that all existing XMPP Software is not able to connect to their server without code changes or updates.
I have updated the MatriX library to support the X-MESSENGER-OAUTH2 SASL mechanism. You can download the latest binary here.
Here is an example how you can connect to Windows Live Messenger with MatriX.
The XMPP domain is messenger.live.com. Microsoft has the proper SRV records, so MatriX discovers the hostname automatically. All you have to do is subscribe to the OnBeforeSasl event and disable the the automatic SASL mechanism selection and choose the X_MESSENGER_OAUTH2 mechanism for authentication. Additional you have to pass SaslProperties which include your access token.
var xmppClient = new XmppClient {XmppDomain = "messenger.live.com"};
xmppClient.OnBeforeSasl += xmppClient_OnBeforeSasl;
xmppClient.Open();
private void xmppClient_OnBeforeSasl(object sender, SaslEventArgs e)
{
e.Auto = false;
const string ACCESS_TOKEN = "your_access_token";
e.SaslMechanism = SaslMechanism.X_MESSENGER_OAUTH2;
e.SaslProperties = new LiveMessengerProperties
{
AccessToken = ACCESS_TOKEN
};
}
Of course you must retrieve your access token before you can connect with MatriX.
Some additional useful resources from Microsoft:
<iq type='get'
from='hag66 at shakespeare.lit/pda'
to='darkcave at shakespeare.lit'
id='find45'>
<query xmlns='http://jabber.org/protocol/disco#info'
node='files'>
<identity category='filesys' type='file' name='file1' />
</query>
</iq>
<iq type='result'
from='darkcave at macbeth.shakespeare.lit'
to='hag66 at shakespeare.lit/pda'
id='find45'>
<query xmlns='http://jabber.org/protocol/disco#info'
node='files/somefile'>
<identity category='filesys' type='file' name='file1'
hash='552da749930852c69ae5d2141d3766b1'/>
</query>
</iq>
<iq type='get'
from='hag66 at shakespeare.lit/pda'
to='darkcave at shakespeare.lit'
id='find46'>
<query xmlns='http://jabber.org/protocol/disco#info'
node='files'>
<identity category='filesys' type='file' name='file1'/>
<x xmlns='jabber:x:data' type='get'>
<field var='ssn' type='text-single' label='Social Security Number'>
<regex>([0-9]{3})-([0-9]{2})-([0-9]{4})</regex>
</field>
</query>
</iq>
Planet Jabber is an aggregate of personal weblogs of Jabber/XMPP developers and contributors.
See Planet Jabber News for general and project news.
Last updated:
January 27, 2012 17:38
All times are UTC.
The maintainer of this Planet is Ralph Meijer. He can be contacted at ralphm@ik.nu (Jabber and e-mail).
Powered by:
