Search results
Jump to navigation
Jump to search
- #REDIRECT [[:Category:Spec_Remarks]]36 bytes (4 words) - 17:51, 10 October 2019
- #REDIRECT [[:Category:Spec_Remarks]]36 bytes (4 words) - 17:52, 10 October 2019
- === Specification front === * Specs in last call383 bytes (50 words) - 11:03, 7 November 2008
- {{specs}}208 bytes (35 words) - 20:10, 20 April 2020
- [[Category:Spec_Remarks]]359 bytes (45 words) - 15:40, 10 October 2019
- {{specs}} ...popular method is to have users contact administrators, or some deployment-specific solution.330 bytes (49 words) - 20:51, 17 April 2020
- ...client and server side. I also have an important understanding of the XMPP specs since I had to "study" them to correctly implement our server and client s ...he knowledge and experience I gained after implementing many JEPs and XMPP specs both on the server and client sides.1 KB (200 words) - 21:48, 24 July 2010
- ...cretary, Treasurer, Executive Director, etc. I also [co-]authored a lot of specs, both XEPs and RFCs. ...years I was very active in the Internet Engineering Task Force (IETF) as a spec author, working group chair, member of the Internet Engineering Steering Gr2 KB (314 words) - 17:39, 5 October 2023
- ...one of its founding developers. I've also contributed to a variety of XMPP specs, and am mentioned in the RFCs.728 bytes (115 words) - 14:23, 24 May 2022
- RETIRED * Hardware specs: Dell Poweredge 1850(Dual P4 Hyperthreaded Xeon CPUs (2.8 Ghz), 4 GB mem, RETIRED * Hardware specs: Dell Poweredge 1850(Dual P4 Hyperthreaded Xeon CPUs (2.8 Ghz), 2 GB mem,3 KB (415 words) - 23:10, 4 June 2023
- ...Technical Review Team is to continuously improve the technical quality of specifications produced by the XMPP Standards Foundation. === Spec Reviews ===3 KB (426 words) - 18:42, 14 September 2017
- {{specs}}897 bytes (141 words) - 12:49, 23 April 2020
- ...one of its founding developers. I've also contributed to a variety of XMPP specs, and am mentioned in the RFCs.732 bytes (120 words) - 14:35, 15 May 2020
- * Justin to update the spec to reflect IRL discussion ...lements in message/presence (Justin to write first draft of best practices spec):5 KB (799 words) - 22:52, 27 January 2010
- * Heavily advocates XMPP's use in games and is working on a spec for out-of-band server advertising based on pubsub and MUC For the Copyleft Games Group (which PySoy is part of), I'm working on a spec for out-of-band gaming via XMPP/Jingle. I want to leverage compatibility a2 KB (352 words) - 18:38, 21 April 2009
- ...one of its founding developers. I've also contributed to a variety of XMPP specs, and am mentioned in the RFCs.825 bytes (140 words) - 06:37, 13 May 2019
- {{specs}}993 bytes (156 words) - 20:39, 17 April 2020
- ...cts on top of software which has real use and support in the community. We specialise in real-time communications, including IM, VOIP, video and collaborat ...dless of the underlying protocol, language or even license. As well as the spec itself, Collabora supports and develops the Jabber/XMPP backend as our main3 KB (461 words) - 13:41, 28 July 2010
- ...cretary, Treasurer, Executive Director, etc. I also [co-]authored a lot of specs, both XEPs and RFCs. ...years I was very active in the Internet Engineering Task Force (IETF) as a spec author, working group chair, member of the Internet Engineering Steering Gr3 KB (471 words) - 01:26, 31 October 2022
- ...ason to reapply for XSF membership. One of my main interests is making our specs more approachable to client (library) developers.1,022 bytes (152 words) - 16:50, 26 July 2021
- ...one of its founding developers. I've also contributed to a variety of XMPP specs, and am mentioned in the RFCs.963 bytes (158 words) - 22:41, 21 May 2021
- This event's goal is to produce tools (specs, implementations, etc.) for public XMPP services,1 KB (161 words) - 10:01, 11 April 2023
- ...and howto documents, but since 2001 I've concentrated on writing protocol specs -- mostly [http://xmpp.org/extensions/ XEPs] and [http://xmpp.org/rfcs/ R1 KB (175 words) - 23:06, 27 January 2010
- ...mostly focused on documenting existing protocols and writing new protocol specs. As a result I edited the XMPP RFCs and have also written dozens of XMPP E * Push more specs from Draft to Final (see [http://mail.jabber.org/pipermail/standards/2007-3 KB (536 words) - 02:35, 17 December 2020
- ...h with the standardization process. One of my main interests is making our specs more approachable to (future) client (library) developers.1 KB (180 words) - 20:36, 5 August 2023
- would like to specifically address while on the council. I suspect the answer is some mix of modifying the name of the document statuses, cre6 KB (994 words) - 14:32, 5 November 2020
- ...h with the standardization process. One of my main interests is making our specs more approachable to client (library) developers.1 KB (177 words) - 14:20, 27 July 2022
- ** Idee: Es gibt nur eines Spec -> Interoperabilität ** Hat [https://matrix.org/docs/spec/proposals Spec-Proposal-Prozess]3 KB (421 words) - 14:16, 23 July 2020
- I think that XMPP on the mobile, especially with project's like [https://github.com/rtreffer/AsmackService AsmackS ...ing on some of the social bits in XMPP. (Eventually I'd like to see a good spec for XMPP social, I just don't think we are there yet)1 KB (194 words) - 18:20, 28 February 2011
- ...nes. Has some been Obsoleted, or simply Updated? Also learn about Friendly specs! focus on specs3 KB (463 words) - 19:07, 12 October 2019
- ...be used for United Communications. I've provided feedback about the Jingle specs directly to Peter Saint-Andre instead of posting to the public discussion1 KB (227 words) - 21:09, 7 July 2008
- * finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability;1 KB (199 words) - 15:27, 22 March 2018
- ...sode, I work on the M-Link XMPP server. Needless to say a lot of XMPP and spec reading are involved here :)1 KB (210 words) - 07:47, 8 October 2013
- * both editing and writing specs * clarifying question: editorial or actually writing specs?5 KB (801 words) - 16:25, 3 January 2023
- * finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability;1 KB (216 words) - 17:26, 26 June 2017
- * Clean up the publish-subscribe specifications (XEP-0060, XEP-0163, XEP-0248) * Advance the server dialback specification (XEP-0220) to Draft1 KB (192 words) - 18:49, 3 August 2012
- ...al features of stable XEPs. This gives me a unique perspective on the XMPP specifications. There are also a fair number of specifications I'd like to see progress on. These include1 KB (229 words) - 23:24, 30 September 2010
- * improving Tigase's compatibility with XMPP specs and general interoperability,2 KB (237 words) - 17:07, 4 April 2024
- * improving Tigase's compatibility with XMPP specs and general interoperability,2 KB (237 words) - 12:16, 22 March 2023
- ...al features of stable XEPs. This gives me a unique perspective on the XMPP specifications. I'm quite active on the standards mailing list. There are also a fair number of specifications I'd like to see progress on. These include1 KB (227 words) - 18:22, 11 October 2011
- ...I work on the M-Link XMPP server team. Needless to say a lot of XMPP and spec reading (and suggesting cleanups in them) are involved here :)1 KB (258 words) - 11:00, 27 June 2014
- * finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability;2 KB (262 words) - 12:38, 28 March 2014
- * finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability,2 KB (257 words) - 12:18, 22 March 2019
- * we are very good at specifications, but only by developers for developers, we don't ask enough our u ...good and best practices already available on the market, both in terms of specs and implems <= PUSH FOR IMPLEMENS OF NEW XEPs, COLLECT FEEDBACK2 KB (272 words) - 13:01, 6 November 2017
- * [[Sprints/2020 March Duesseldorf|March 2020 Duesseldorf Spec Sprint]]1 KB (136 words) - 13:19, 26 February 2022
- * [http://code.google.com/soc/inkscape/about.html Inkboard Protocol Spec and Lib Conversion]1 KB (201 words) - 20:03, 24 July 2010
- * finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability,2 KB (298 words) - 15:54, 3 April 2020
- * finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability;2 KB (301 words) - 08:44, 7 April 2015
- * improving Tigase's compatibility with XMPP specs and general interoperability,2 KB (309 words) - 10:49, 12 April 2021
- ...any of the clients, servers or libraries lacking support (see the project-specific lists below). ...xperience with this method so that we can correct and advance the relevant specs, which are:21 KB (3,274 words) - 01:05, 18 December 2020
- ...od practices" to make things speak the same language. The interoperability spec will be a moving target with constant elaboration to enable true interopera ...nd doesn't cost a fortune to be compliant. And most importantly it is open specifications that is easy to find.2 KB (371 words) - 17:48, 1 November 2013
- * improving Tigase's compatibility with XMPP specs and general interoperability,2 KB (350 words) - 11:04, 25 May 2022
- * [http://code.google.com/soc/inkscape/about.html Inkboard Protocol Spec and Lib Conversion]2 KB (217 words) - 20:03, 24 July 2010
- ! Client !! Described Version !! Jingle Audio Spec !! Transport Methods !! Audio Codecs || ICE implementation || STUN/TURN dis ...freedesktop.org/wiki/ libnice] || DNS (for STUN), Google Jingle Info, user specified || Yes (via libnice) || No2 KB (244 words) - 19:23, 5 August 2019
- ...mostly focused on documenting existing protocols and writing new protocol specs. As a result I edited the XMPP RFCs and have also written dozens of JEPs.2 KB (318 words) - 02:37, 17 December 2020
- ...SF discussions and other business, I have a few goals that I would like to specifically address while on the council: ...e the legacy [https://xmpp.org/extensions/xep-0136.html Message Archiving] spec (which I will revisit once MAM has been debated).2 KB (387 words) - 00:57, 28 October 2017
- My passion is programming, and I am specializing in the topics of low-level hardware development and post-quantum cr I have largely contributed to the recent versions of the OMEMO XEP, especially the cryptographic details.2 KB (402 words) - 13:14, 14 February 2023
- == XMPP Specifications == ...is my reason to apply for XSF membership. My main aim would be making our specs more approachable to client (library) developers.3 KB (413 words) - 10:47, 9 August 2020
- ...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:3 KB (418 words) - 18:09, 4 June 2014
- ...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:3 KB (418 words) - 17:50, 14 October 2013
- ...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:3 KB (418 words) - 15:55, 3 September 2012
- ...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:3 KB (418 words) - 18:19, 2 July 2011
- ...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:3 KB (419 words) - 20:24, 3 August 2010
- ...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:3 KB (421 words) - 08:51, 8 September 2009
- * it needs to be specified more clearly: what is packet relay? * usage of relay on XMPP network is discouraged. right now the spec says you SHOULD allow relaying (since you MAY decide not to allow it). Let'3 KB (445 words) - 01:09, 18 December 2020
- ...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:3 KB (480 words) - 19:46, 24 July 2010
- ...even needed - no real consensus as it may be too implementation enironment specific two aspects of conferencing12 KB (2,032 words) - 03:29, 2 March 2014
- ...ther) discussions on the XMPP mailing lists. However, my official protocol spec contributions remain limited to the following XEPs:3 KB (527 words) - 19:47, 24 July 2010
- === Specs === ...tations from Joe on some of the new XEP's he would like to see worked on (especially Carbons, XEP-0280) and then we had some demos of &yet's [http://otalk.3 KB (527 words) - 16:52, 26 December 2023
- ..., multi-user chat (XEP-0045), publish-subscribe (XEP-0060), and the Jingle specs (XEPs 166, 167, 176, 234, etc.). In 2009 I co-authored "XMPP: The Definiti3 KB (488 words) - 23:43, 27 September 2015
- == Base Specifications == This specification. Defines how provisioning, the management of4 KB (490 words) - 17:42, 13 April 2013
- Some need specs, some need implementation/deployment. No specific conclusion/action.13 KB (2,032 words) - 01:14, 18 December 2020
- ...gs communicate. In order to make it happen we must work for provide robust specs in area of rather new development: ...(we are working on and RSS/Atom mobile reader and we think that there few aspects that need standardization)4 KB (641 words) - 23:16, 27 January 2010
- ...t, David Durand's Palimpsest model, some of the Tiny SVG spec and the XMPP specs. * Read documentation again, mainly other XEPs and a few old mailing lists, especially about writing the XEP.18 KB (2,927 words) - 01:01, 18 December 2020
- ...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:4 KB (696 words) - 19:49, 24 July 2010
- ...he same DOM. Basic groups communication primitives are part of first level spec.4 KB (624 words) - 13:41, 28 July 2010
- ...mmands in Mellium to draw forms. Also we'll discuss some problems with the spec and how they could be resolved.4 KB (603 words) - 20:34, 14 December 2021
- == Base Specifications == This specification. Defines how provisioning, the management of5 KB (610 words) - 10:30, 13 June 2013
- ...Peter, though). I've also been actively reviewing the 3920bis and 3921bis specs. I've been involved in the formation of a number of XEPs (and more are com * 198 is specced, and is starting to see use - we need to push for this.4 KB (763 words) - 12:56, 21 September 2010
- This page lists known issues with the Publish-Subscribe specifications ([http://xmpp.org/extensions/xep-0060.html XEP-0060], [http://xmp * The section mentions that a '''body''' element can be provided and used to specify ''natural-language text regarding the affiliation change''.5 KB (692 words) - 09:32, 5 April 2015