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 call
    383 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 Gr
    2 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 a
    2 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 main
    3 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 Gr
    3 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/ R
    1 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, cre
    6 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 specs
    3 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 discussion
    1 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 Draft
    1 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 include
    1 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 include
    1 KB (227 words) - 18:22, 11 October 2011

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)