Hello,
Part of the solution is requiring x:data forms for registration. Yes, as
Matthias pointed out this will make life difficult for existing clients.
So we need to define a transition strategy. Clearly define how the
x:data-only registration works and set some goals for deprecating the
old wa
[EMAIL PROTECTED] schrieb:
I think if we want to solve this in a compatible way we should just
let the muc server block multiple nicks in the same room with only
differ in case (rephrase that in Stringprep section numbers, etc)
If a server works that way (and maybe announces with a status code o
[EMAIL PROTECTED] schrieb:
And i expect all the major servers to get this right, because they
use xml parsers that are xml compliant¹...
this is assumption is wrong.
There is also many XMPP software which is using its own XMPP/XML parsers
and DOM's because we have only a subset of XML and don'
Ralph Meijer schrieb:
I am curious which software this holds for. Most XMPP implementations
are based on expat, as far as I know. Sure they might have their own
DOM's (my Twisted XMPP stuff does), but that is irrelevant for parsing.
There is many software which is using expat, but there is also
Sergei Golovan schrieb:
I wasn't clear enough here. I mean "no sowtware generated XML with
CDATA". I can't count for all programs in the world, but all server
implementations use plain XML escaping.
i think this is solved now.
CDATA is in the RFC3923 which means the latest ejabberd commit is RF
This looks good to me.
There is a copy & paste error in example 5. I should be
instead of .
Alex
Hello,
i am for jabber:client because i don't like the namespace switching in
software.
But this does not help that much if we stick with other namespaces on
s2s connections forever.
Alex
Dave Cridland schrieb:
It's a principle of the thing with DFSG. I can understand their point of
view, but I don't think it's our job to adhere to their requirements,
either.
We need to ensure that our licensing is correct for what we require. If
we can accomodate Debian, great, but I suspect
Hello,
i recently finished my BOSH implementation and stumbled over 2 problems.
Most implementations send the stream features only once at the
beginning. Because of the missing stream headersin BOSH they send no
stream features after SASL authentication and other stream resets. This
caused me
Fabio Forno schrieb:
I don't get the problem, the XEP is clear and it requires the client
to send a restart in order to get new stream features. If the
implementations are broken it's more appropriate to ask the developers
to fix them than changing the XEP ;)
yes you are right. Maybe some inter
Peter Saint-Andre schrieb:
If there is interest in such an extension, I will write up a spec for it.
yes there is, +1 from me.
Alex
Tomasz Sterna schrieb:
Oh. I realized that I'm being to sparse.
I meant, "stopping reading for a while".
If you allow 10kb per second, you just read no more than 10kb in a
second and pause. Then after one second read another no more than 10kb.
The TCP buffering, timeouts and retransmission will
example 4 in XEP-0047 is using amp.
I think it shold be:
instead of:
because only the deliver condition is defined in XEP-0079 amp.
Regards,
Alex
Joe Hildebrand schrieb:
3b. If we specify an MTI algorithm, do we specify MD5 or SHA-1 or
something else?
Frankly, I don't care. MD5 is smaller, and probably more secure, but
has marketing issues, particularly with a vocal minority on this list.
We all have SHA-1 implementations for other t
Peter Saint-Andre schrieb:
The requesting entity MUST check the identities and supported
features against the 'ver' value by calculating the hash as described
under Generation of the ver Attribute and making sure that the values
match.
sorry missed this paragraph. Now i see why it m
Peter Saint-Andre schrieb:
This puts things in a bit of a different light. I might change presence
8+ times during a presence session, but I'd bet that most users don't do
change presence that often. Therefore it seems to me that plunking
n+os+v in caps is not evil from the perspective of bandw
Dave Cridland schrieb:
Point taken.
So let's make it unique for any given iq:version response. In fact, on
this basis, we can ditch v again, and make node be a URI unique to the
client, its version, and platform. Perhaps
http://psi-im.org/0.11/linux-2.6 or even
http://psi-im.org/janlcdanrfun
Peter Saint-Andre schrieb:
I'm fine with either a best-practices form of iq:version queries, or
just putting the n and v attributes (and optionally 'os') into caps.
Since we now have a XEP-0115 draft with n/v/os, let's go with that
unless anyone has a real major objection?
We'll run it up th
Tomasz Sterna schrieb:
I found e serious issue with FC 3921bis Managing Presence Subscriptions.
[...]
I would disallow them. I see no sense behind full jid subscription. This
would even confuse people. We said before that resources should be
unpredictable.
I do run some services on server
Fabio Forno schrieb:
...
- compression is not as bad as I thought and if time to market is
essential that's the only viable solution
see also my comments in the jdev thread, I think we should all hop one
one thread ;-)
http://mail.jabber.org/pipermail/jdev/2008-February/026157.html
I have don
Fabio Forno schrieb:
... Anyway I can anticipate that with zlib the size of a whole
message stanza is often shorter or minimally longer than the
uncompressed body alone: do we really need better performance?
I posted some stats in another thread before:
http://mailman.jabber.org/pipermail/jdev/
Peter Saint-Andre schrieb:
Hi Alex, that's helpful information. We have compression enabled at the
jabber.org service so perhaps you could get some new numbers with your
account there. :)
yes I can do that. The code must be still somewhere on my hd. I do a
search ;-)
Alex
Aki Niemi schrieb:
Is there currently a way for the client to put its connection into
dormant mode. For example, when my phone is in my pocket with the screen
locked, keeping the roster's status updated seems unnecessary. Yet, the
connection still needs to be live for incoming IMs and sessions.
Dave Cridland wrote:
2) Client says "I have the roster as of this point in time". Server says
"Here's all the changes since then.".
This is obviously the best option in terms of efficiency, but it, too,
has problems. The key issue is that roster entries won't die - instead,
they'll be maintai
Fabio Forno wrote:
I like this one, since it always has a backup when no sinchronization
is needed. Moreover the server can store only a window of changes, and
send the whole roster if the last known by the client is too old
+1, I don't think we want to keep all roster revisions from the
begin
Richard Dobson schrieb:
+1. I can't see any reason for the spec to require more than a
increasing version number.
I would prefer if it were just an opaque string, certainly as far as the
client in concerned there is no need for it to do anything other than
store the most recent version identi
Peter Saint-Andre schrieb:
Here is revised text:
The value of the 'version' attribute SHOULD be a non-negative
integer representing a strictly increasing sequence number that
is increased with any change to the roster (whether or not the
client supports this extension) but MAY be a u
Peter Saint-Andre schrieb:
1. Let's say you want to connect to a MUC service. Does it make sense to
have an SRV record for that? Such as:
_xmpp-groupchat._tcp.conference.jabber.org 5269 athena.jabber.org
2. Let's say you want to connect to a pubsub service that pumps out
notifications. How abou
Pedro Melo schrieb:
XMPP requires TLS. If you don't want to use TLS, you are using Jabber,
not XMPP. And then you should look for
I don't agree here. You should use TLS whenever possible, but its not
required.
Many XMPP software for embedded and mobile devices does not support TLS
because its
Justin Karneges schrieb:
On Friday 28 March 2008 10:46 am, Peter Saint-Andre wrote:
I've been chatting with someone off-list about mobile optimizations and
he suggested that we might want to build in the ability to seamlessly
switch between BOSH and TCP. For example you would use the TCP binding
Carlo v. Loesch schrieb:
Yes, that's why I started thinking about something better in 1990.
I understood there was no way for IRC to be 'fixed' because its design
is fundamentally flawed. XMPP is only syntactically flawed, which is
a much better starting point. And you can argue that's just my op
Pedro Melo schrieb:
Yes, that was not the point of this, it was only to show that this
problem is important now, and not "when we have 100k subscribers in the
future". The future is here now.
Thank Pedro for pointing this out. I was looking at the pubsub nodes on
jabber.org which is one of th
Ralph J.Mayer schrieb:
I had to learn these days that the presence server that comes with
the Cisco Unified Communications Manager uses SIMPLE and not XMPP
like I had hoped.
:(
Googeling for a comparison leads to
http://www.jabber.org/protocol/xmpp-simple.shtml
Looks like this page does not
Artur Hefczyc schrieb:
On 4 Apr 2008, at 12:05, Richard Smith wrote:
Johannes Wagener wrote:
Proposed XMPP Extension: IO DATA
I second this proposal.
I also second this proposal.
I have done lots of Jabber RPC stuff in the past. RPC is poorly
documented and supports only basic data types
Peter Saint-Andre schrieb:
If there are no objections to this idea, I'll write up a little XEP or
two about this.
+1 for getting rid of the stream restart. I started this discussion
several times in the past and never understood why we need them with TLS
and SASL ;-)
* this saves us some ro
The 2007-2008 XMPP Council and XSF Board of Directors were elected in
September 2007. Therefore we have to select the next Board and Council. XMPP
Council members must be elected members of the XSF, there is no such
restriction for the Board of Directors.
If you are interested in running for Board
Because the XSF Wiki is down right now this application period gets
extended and the meeting on May 2nd canceled.
I will send an update as soon as the Wiki is up again and we have a new
schedule.
Thanks,
Alex
-- Original Message --
From: "Alexander Gnauck"
To: "J
account please contact me directly per EMail.
Sorry for the inconvenience.
Thanks,
Alex
-- Original Message --
From: "Alexander Gnauck"
To: "Jabber Developer" ; "XMPP Standards list"
; "XSF Members"
Sent: 11.04.2017 16:47:47
Subject: Re: [Membe
/Membership_Applications_Q3_2017
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
The application period end on August 27th, 2017, so apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmp
/Membership_Applications_Q4_2017
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
The application period ends November 21st, 2017.
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabbe
/Membership_Applications_Q1_2018
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org__
/Membership_Applications_Q2_2018
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org__
/Membership_Applications_Q3_2018
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org__
/Membership_Applications_Q4_2018
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org__
thanks for the reminder Ralph.
Alex
-- Original Message --
From: "Ralph Meijer"
To: "XSF Members"
Cc: "XMPP Standards"
Sent: 01.11.2018 16:05:22
Subject: [Members] XSF Board and Council applications due November 4
Hi all,
As every year, we have elections coming up for the Board of
final reminder...
Alex
-- Original Message --
From: "Alexander Gnauck"
To: "XSF Members" ; "XSF Members"
Cc: "XMPP Standards"
Sent: 02.11.2018 12:51:27
Subject: Re: [Members] XSF Board and Council applications due November 4
thanks for th
I have setup the membership application Wiki page for the application
period Q1 2019
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community.
To apply, create a page about yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applicati
/Membership_Applications_Q2_2019
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmp
I have setup the membership application Wiki page for the application
period Q3 2019
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community.
To apply, create a page about yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applicati
/Membership_Applications_Q4_2019
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
The application period ends November 24th, 2019.
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmp
I have setup the membership application Wiki page for the application
period Q1 2020
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applicat
I have setup the membership application Wiki page for the application
period Q2 2020
Applications are encouraged from individuals who are actively involved
in the Jabber/XMPP community.
To apply, create a page about yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applications_Q2_202
I have setup the membership application Wiki page for the application
period Q3 2020
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applicat
I have setup the membership application Wiki page for the membership
application period Q4 2020
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
https://wiki.xmpp.org/web/Membersh
Hello,
another year went by and we have to elect the 2020-2021 XSF Board and
Council soon.
When you are interested in running for Board (business stuff) or Council
(technical stuff) for the 2020-2021 term, please create an appropriate
Wiki page by November 8th, 2020 and link it from here:
h
final reminder that the Board & Council application period closes by the
end of this week.
Alex
-- Original Message --
From: "Alexander Gnauck"
To: "XSF Members"
Cc: "Jabber Developer" ; "XMPP Standards list"
Sent: 29.10.2020 09:
I have setup the membership application Wiki page for the application
period Q1-2021
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applicat
I have setup the membership application Wiki page for the application
period Q2 2021
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applicat
Hello,
I have setup the membership application Wiki page for the application
period Q3 2021
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community.
To apply, create a page about yourself on the Wiki by August 1st:
https://wiki.xmpp.org/w
I have setup the membership application Wiki page for the application
period Q4 2021
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
https://wiki.xmpp.org/web/Membership_Applicat
Hello,
another year went by and we have to elect the 2021-2022 XSF Board and
Council soon.
When you are interested in running for Board (business stuff) or Council
(technical stuff) for the 2021-2022 term, please create an appropriate
Wiki page by November 7th, 2021 and link it from here:
h
-- Originalnachricht --
Von: "Alexander Gnauck"
An: "XSF Members" ; "XMPP Standards list"
; "j...@xmpp.org"
Gesendet: 20.09.2021 19:23:37
Betreff: [Members] Board & Council elections
Hello,
another year went by and we have to elect the 2021-2022 XSF Boar
-- Originalnachricht --
Von: "Alexander Gnauck"
An: "XSF Members" ; "XMPP Standards list"
; "j...@xmpp.org"
Gesendet: 27.10.2021 13:55:51
Betreff: Re: [Members] Board & Council elections
Just a reminder that we are coming closer to the deadline
I have setup the membership application Wiki page for the membership
application period Q1 2022
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
https://wiki.xmpp.org/web/Membersh
The XMPP Standards Foundation (XSF) is currently holding its quarterly
membership application period:
http://wiki.xmpp.org/web/Membership_Applications_October_2008
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page
The XMPP Standards Foundation (XSF) is currently holding its quarterly
membership application period:
http://wiki.xmpp.org/web/Membership_Applications_January_2009
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a p
Peter Saint-Andre schrieb:
Feedback is welcome, especially from Justin. :)
I will use IBB in a project for sending big data objects. So not files
directly. Because it well designed for splitting any data in chunks.
So we could add other examples and use cases than only file transfer to it.
;-)
Regards,
Alex
--
Alexander Gnauck
http://www.ag-software.de
xmpp:gna...@jabber.org
from other XEPs and show
this use cases in the IBB XEP. But there is already a small paragraph
about non file transfer related use cases.
Regards,
Alex
--
Alexander Gnauck
http://www.ag-software.de
xmpp:gna...@jabber.org
no ideas?
Alexander Gnauck wrote:
Example 208 shows the as child of
cauldronburn
Example 124 has the as child of
cauldronburn
which one is correct. I think the second one.
is missing in the schema of
Also if 208
Peter Saint-Andre wrote:
That's wrong. Will fix.
http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0045.xml?r1=2830&r2=2869
Thanks
Alex
allow anonymous
users because of security reasons.
I think we need a way to discover if a user is anonymous or not.
Or require the server to add some extra stamped info to the presence of
anonymous users.
Regards,
Alex
--
Alexander Gnauck
http://www.ag-software.de
xmpp:gna...@jabber.org
Philipp Hancke wrote:
Your server allows anonymous users to send messages to remote domains?
yes it does, and many others do. This is the default in ejabberd when
you enable anonymous logins. No idea if you can disable s2s for
anonymous users.
Regards,
Alex
--
Alexander Gnauck
http
page about
yourself on the wiki.
If you don't have a wiki account, send your name, preferred nickname and
email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
The application period ends on 22th April 2009 23:59h UTC, so apply today!
Regards,
Alex
--
Alex
about yourself on the wiki.
If you don't have a wiki account, send your name, preferred nickname
and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
The application period ends on 19th July 2009 23:59h UTC, so apply today!
Regards,
Alex
--
Alexander G
page about
yourself on the wiki.
If you don't have a wiki account, send your name, preferred nickname
and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
The application period ends on 28th October 2009 23:59h UTC, so apply today!
Regards,
Alex
--
Alex
XEP-0206 sais:
If the BOSH wrapper is not empty, then it SHOULD contain
...
One or more complete , , and/or elements
qualified by the 'jabber:client' namespace.
then there is a note which sais:
Many existing XMPP-specific implementations of BOSH clients and
connection managers do not sp
2010 at 23:59h UTC. So apply
today!
Regards,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org
November 2010 at 23:59h UTC. So
apply today!
Regards,
Alex
-- Alexander Gnauck
xmpp:gna...@jabber.org
We have setup the membership application Wiki page for the next
application period Q4/2011
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the wiki:
http://wiki.xmpp.org/web/Membership_App
I have setup the membership application Wiki page for the next
application period Q1/2012
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki:
http://wiki.xmpp.org/web/Membership_Appl
e. So apply now.
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org
/Membership_Applications_Q1_2013
If you don't have a wiki account, send your full name, preferred nickname
and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org
currently I have some issues with the kerberos principal in GSSAPI SASL
authentication.
What is the correct way for building the kerberos principal for
authentication in the client?
1) xmpp/xmppdomain@realm
2) xmpp/hostname@realm
with hostname I mean the host we are connecting the TCP socket t
> Anyone interested?
>
absolutely!!!
Alex
separate extension and namespace.
--
Alexander Gnauck
http://www.ag-software.de
xmpp:gna...@jabber.org
On Wed, Sep 4, 2013 at 6:34 AM, Jaussoin Timothée wrote:
> Le 22/08/2013 09:23, Jaussoin Timothée a écrit :
>
> Le 19/08/2013 11:24, Jaussoin Timothée a écrit :
>>
>>
ops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
Xmpp:gna...@jabber.org
smime.p7s
Description: S/MIME cryptographic signature
/Membership_Applications_Q3_2014
If you don't have a wiki account, send your full name, preferred nickname
and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
Xmpp:gna...@jabber.org
smime.p7s
Description: S/MIME cryptographic signature
/Membership_Applications_Q4_2014
If you don't have a wiki account, send your full name, preferred nickname
and email address to me or one of the other Sysops:
<http://wiki.xmpp.org/index.php/Sysops>
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauc
Wójcik
* Florian Zeitz
* Martin Hewitt
feel free to recruit new XSF members and push the message to other channels.
Regards,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org
/Membership_Applications_Q3_2015
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org
/Membership_Applications_Q4_2015
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org
/Membership_Applications_Q1_2016
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org
/Membership_Applications_Q2_2016
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmp
/web/Membership_Applications_Q3_2016
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/web/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmp
/Membership_Applications_Q4_2016
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org__
/Membership_Applications_Q1_2017
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
The application period ends January 15th, 2017.
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmp
/Membership_Applications_Q2_2017
If you don't have a wiki account, send your full name, preferred
nickname and email address to me or one of the other Sysops:
http://wiki.xmpp.org/index.php/Sysops
Apply now!!!
Thanks,
Alex
--
Alexander Gnauck
xmpp:gna...@jabber.org (subscription req
I have setup the membership application Wiki page for the application
period Q2 2022.
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki here:
https://wiki.xmpp.org/web/Membership_Ap
I have setup the membership application Wiki page for the application
period Q3 2022
Applications are encouraged from developers and others who are actively
involved in the Jabber/XMPP community. To apply, create a page about
yourself on the Wiki here:
http://wiki.xmpp.org/web/Membership_Appl
1 - 100 of 109 matches
Mail list logo