We just released a new version of TextOne iOS messaging client.
This is a version improving compliance with iOS 7 (and introduce a new and lighter design). It also improves networking stack and time to connect / retrieve messages.
It also fixes a long standing crash issue on launch that could sometime happen.
It can be downloaded from Apple App Store: TextOne on Apple AppStore.
Two months after the previous huge release, we are keeping the pace with a new feature packed version. We added major improvements regarding to SIP support, Carbon copy, stream management and added Riak as a new supported database.
ejabberd Community 14.07 includes several improvements and many bugfixes over the previous 14.05 release:
- SIP Outbound (RFC 5626) support
- New option always_record_route
- New options record_route and routes
Carbon Copy (XEP-0280)
- Don’t log MUC messages with hint
- Don’t carbon copy messages with hint
- Let is_carbon_copy/1 recognize carbons
- Don’t send XEP-0280 v1 copies back to sender
Stream Management (XEP-0198)
- XEP-0198: Terminate session if stanza queue becomes too large
- XEP-0198: Don’t exit on socket send failure
- XEP-0198: Don’t drop session on failed resume
- XEP-0198: Check whether routed packets are stanzas
- Riak support
Install and config
- New options log_rotate_count, log_rotate_size and log_rate_limit
- html guide is now generated when building source tarball
- Use p1_utils, and move treap.erl to p1_utils
- Get rid of p1_mnesia file
- old release notes are not installed anymore
- Don’t “forget” listener options
- Always enable STUN at compile time
- Do not check for Erlang apps at configure time
- Add –enable-riak configure flag
- Add tests for stream management
- Add tests for mod_carboncopy
- Add tests for mod_caps
- Improve MUC test cases
- Travis CI: Enable Riak tests
- Add Riak backend to the testing suit
- The test suite no longer fails without –enable-transient_supervisors.
- MUC messages with ~ were not logged (EJAB-1696).
And many bugfixes all over the source code.
This release requires at least Erlang/OTP R15, and works perfectly with R16B03, and will work with R17 if Riak support is disabled (–disable-riak).
When building from Git, “make install” now fails if you do not run “make doc” before due to doc/guide.html no longer being in the repo. If you don’t have necessary tools to build the guide, just pick the one from ejabberd sources tarball.
As usual, the release is tagged in the Git source code repository on github
The source package and binary installers are available at ProcessOne
If you suspect you found a bug, search or fill a bug report in Jira
Mongrel2 is a fast and simple HTTP & WebSocket server that communicates to backend workers via ZeroMQ. It does one thing and does it very well, making it an ideal part of a componentized architecture. The code is event-driven, allowing it to support thousands of concurrent connections and also asynchronous behaviors. These properties are especially important to realtime applications.
Fanout has been one of the most active contributors to the Mongrel2 project over the past year, adding features such as TLS SNI and improved streaming capability. We've also been working on making the server easier for people to get started with. And with that, we are proud to announce official packages for Debian and Ubuntu!
Mobile apps now allow businesses to be more responsive to users than ever before, but this interaction has created new customer expectations. While a mobile app must fulfill its core function, it must also continue a dialog with its users to remain relevant. Doing so requires ongoing, intelligent, targeted outreach to customers and an extension of customer-service strategy into the app itself.
Brands and businesses that develop mobile applications must be aware of the demands and limits of an increasingly sophisticated mobile audience, build a communications strategy that spans the appropriate communications channels, and play to the strength of each channel.
In-App communication gathers as a whole three mobile oriented channels:
- Native Push Notification services.
- In-app notifications.
- In-app chat.
Together, they form the three main components of brand realtime user relationship management on mobile. Today, those three approaches are your best bet to establish a strong communication channel that provides a real value to your users.
The field is quite new and we are glad to be able to share with GigaOM the first research on brand engagement through in-app communication.
The document gives examples, insights and best practices to tighten the links with your mobile application user base and provide them the best value at the right time.
We are pleased to make this report available for free to people interested in Boxcar Push Notifications Service. Join our mailing list focused on leveraging in-app communication for brands to receive report download link »
(Do not worry, it’s low traffic, no spam, we only care about the value we give you).
Report is also available to GigaOM subscribers.
Forms are important for military operations, and there is often a need to handle forms quickly and share with a large number of users, such as Medical Evacuation (MEDEVAC) alerts.
XMPP based open standard instant messaging is widely used by military organizations and is a sensible framework for sharing forms. Our new whitepaper [Military Forms using XMPP], published on the Isode website today, looks at the requirements for military forms and how the XEP-0346 “Forms Display and Publishing”(FDP) can be used to provide real time military forms. It looks at how capabilities provided by M-Link support military forms using FDP, and how gateways can enable integration with other services. FDP is supported in the most recent R16.2 release along with FDP Management in M-Link Console.
We have created a military forms demonstration web site using FDP and Isode’s demonstration Web FDP client. To use this demonstration you will require information on the demonstration accounts. Please contact email@example.com for access to this information.
If you wish to set up an FDP system, this is explained in our FDP Evaluation Guide which will show you how to set up a basic XMPP Form Display and Publishing (FDP) configuration using Isode’s M-Link server, Isode’s Demonstration web client and Isode’s FDP Demonstration Desktop Client.