Hi everybody,
I'd like to suggest to change the URL for aSmack - which is the Smack
port for Android - to another repository. The current link is to Rene
Treffer's initial asmack repository, which hasn't seen any updates in
the last 2 years. I'd really like to thank Rene for his work here! It
On 12.10.2012 03:30, Tomasz Sterna wrote:
Hello.
Does anyone have an idea, why Smack (the Java client library) is
producing these invalid challenge response:
response xmlns=urn:ietf:params:xml:ns:xmpp-sasl=/response
Notice the single = character in place of empty data.
Single =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
I have registered asmack.org and setup a redirect to the github site
of aSmack. This gives me more control about the home of aSmack and
makes it easier if we want to switch from github to something else.
Please update the link from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02.06.2013 15:24, Simon Tennant wrote:
BTW, thanks for looking after ASmack. It's a great improvement that
Rene Treffer and now you did to the original Smack library. Highly
recommended for anyone looking to run native XMPP to an Android
Hi,
I recently added support for Privacy Lists (XEP-0016) in my Android
app and ran into some problems.
The major problem first: If a session is created with a privacy list,
that has a disallow fall-through and another rule that allows
everything from JIDs with subscription 'both', then you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03.06.2014 09:15, Stefan Karlsson wrote:
Yes. Very nice! Iam hoping this means more developers time on
keeping smack* updated aswell :-)
That is already taken care of since a few months. What's still lacking
is contribution or at least
On Wed, Aug 27, 2014 at 3:50 AM, Elvir Bahtijaragic el...@bahtech.com
wrote:
Initially it started as an efficient load testing client for testing
Openfire - we are able to simulate 15000 clients on a xlarge instance on
AWS. Other XMPP clients were unable to handle a large number of XMPP
On 03.02.2015 12:53, Michael Weibel wrote:
It looks as if you'd need to use the stream: prefix for features but
you shouldn't/mustn't use it for error.
What makes you think that you need to use a prefix (or String 'stream'
as prefix) when using features?
- Florian
On 02.02.2015 18:39, Michael Weibel wrote:
Hi all,
MongooseIM currently sends stream:features as „features“ for websockets
connections and strophe.js doesn’t recognize this currently[1].
How I read the RFC is that both behaviours (stream:features or just
„features“) are correct:
On 11.02.2015 14:27, lu...@zauberstuhl.de wrote:
Hi, I am new and I hope that is the right mailing list for questions
like this.
It is the right mailing list. But there is also the
j...@conference.jabber.org MUC, which is also a good place to ask questions.
Nice to see that someone is working
On 05.09.2014 21:40, Tobias Kräntzer wrote:
Am 03.09.2014 um 16:30 schrieb Florian Schmaus f...@geekplace.eu:
The question is, how should the items in the collections be mapped
between the two APIs. remoteStorage is tree based and PubSub is
somehow „list-based“.
Isn't PubSub with XEP-248
On 12.03.2015 12:19, Kevin Smith wrote:
Hi folks,
On 4 Mar 2015, at 18:07, Kevin Smith kevin.sm...@isode.com wrote:
Mentors: I need your teaser ideas please (Thanks to Simon for getting his
up)!
I’ve just done an audit of the ideas page for teaser tasks as student
applications are
On 29.03.2015 20:43, Matthew Wild wrote:
On 29 March 2015 at 15:25, Florian Schmaus f...@geekplace.eu wrote:
The Ignite Realtime community is very happy and proud to announce the
release of Smack 4.1, our open source XMPP client library. Since Smack
4.1 is not binary compatible with Smack 4.0
4.0.0..4.1.0
631 Florian Schmaus
4 Vyacheslav Blinov
3 Anno van Vliet
3 Daniele Ricci
2 Georg Lukas
2 Júlio Cesar Bueno Cotta
2 lucastucchi
2 vito-c
1 Abmar Barros
1 Anno
1 Chris Deering
1 Christoph Fiehe
1 Gilles Cornu
On 01.07.2016 16:22, Marcel Waldvogel wrote:
> For reliability requirements over wireless connections: don't use BOSH;
> do use Stream Management (XEP-0198)
Exactly. And if you want the BOSH advantage over XMPP's TCP binding,
i.e., using standard HTTP(S) ports, then use XMPP's WebSocket binding
marks a milestone for Smack, but before I got into the
exciting new features, I'd like to thank the various contributors:
$ git shortlog -sn 4.1.0..4.2.0
459 Florian Schmaus
8 Fernando Ramirez
3 Anno van Vliet
3 Tibo-lg
3 damencho
3 ramabit
2 Andrey
Given the latest discussions at council@/standards@ ([1] 5.) I think it
is time for a short inquiry of XMPP server behaviour in the wild. Please
answer the following questions:
1. What is the name of the server you develop?
2. Is the carbons state restored after a stream resumption (XEP-0198)?
We are happy to announce that the XMPP Standards Foundation (XSF) is
applying as Google Summer of Code (GSoC) organization.
Open source projects are now able to add their XMPP-related project ideas to
https://wiki.xmpp.org/web/GSoC/2019/Project_Ideas
Interested parties are also invited to join
jXMPP [1], a FOSS XMPP-base library, has just been extended by a
testframework for "XMPP-Strings". Currently, this is limited to Local-,
Domain- and Resourceparts and the various XMPP address types, but may be
extended to future Strings found in XMPP-land.
The testframework comes with a corpus of
19 matches
Mail list logo
