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

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