Search results

Jump to navigation Jump to search
  • Does anyone actually read these? I guess I'll find out.
    75 bytes (13 words) - 12:25, 20 November 2013
  • ''Thanks for taking the effort and reading'' To read more thorough on my xmpp history look on user page
    1 KB (219 words) - 15:50, 22 September 2021
  • ...ractions for 'write a message', 'read a message', 'respond to a message', 'read contact details' (last online time, status message etc.), 'open chat of con === Relevant readings ===
    2 KB (260 words) - 21:22, 5 February 2024
  • * client / message state sharing (what messages have been read, reminders for messages, etc.)
    535 bytes (83 words) - 17:00, 2 August 2023
  • ...nd to get more involved with XSF. Since then, I've lurked in the XSF chat, read the smart things people say, and said very very little. A year ago, I was c ...contribution to Openfire. I've learned that most problems are solved by re-reading XEP-0045 or XEP-0060. Where I hope to build to courage to contribute any
    1 KB (222 words) - 16:24, 18 October 2022
  • | somewhere in Hamburg (read announcements)
    656 bytes (95 words) - 21:17, 23 May 2021
  • ...[mailto:linkmauve@linkmauve.fr linkmauve@linkmauve.fr] by email. You can read more about who I am in my [[Emmanuel_Gil_Peyrot_Application_2018|latest mem I already served Council in 2016-2017, and honestly I think I didn’t do a good job
    2 KB (305 words) - 21:13, 4 November 2018
  • After reading a recent post on the mailing list (regarding XSF members being able/will
    590 bytes (100 words) - 09:57, 31 January 2018
  • * '''Reading the Entries''': The Inbox view will show all the entries received (i.e. === Reading the Entries ===
    3 KB (455 words) - 01:08, 18 December 2020
  • I've no idea, quite honestly. Nobody ever reads these things anyway. Well, I'm writing both the questions and the answers. The reader is assumed to be an interested third party to the discussion, really.
    2 KB (345 words) - 13:43, 28 July 2010
  • === What did I already do ? === * Read both of the XMPP protocols specification
    4 KB (658 words) - 22:16, 24 July 2010
  • ''Relevant readings:'' [https://wiki.gnome.org/Projects/Vala/Tutorial Vala Tutorial]<br/> ''Relevant readings:'' [http://ogp.me/ OpenGraph protocol]<br/>
    8 KB (1,326 words) - 07:02, 11 March 2021
  • * rtfm -- read the friendly manual * tldr -- too long, didn't read
    2 KB (453 words) - 18:48, 17 September 2008
  • To read more thorough on my xmpp history look on user page
    821 bytes (145 words) - 20:01, 29 September 2020
  • * Read some more about Qt * Have been reading "C++ GUI Programming with QT". Good book.
    7 KB (1,119 words) - 01:59, 17 December 2020
  • There already exists a protocol ([https://xmpp.org/extensions/xep-0070.html XEP-0070]) w ** general: Reading docs, setting up wiki, etc.
    8 KB (1,092 words) - 00:59, 18 December 2020
  • ...professionals to take their chance and have their say. When '''YOU''' are reading this feel welcome to sign up, too! ...professionals to take their chance and have their say. When '''YOU''' are reading this feel welcome to reach out!
    7 KB (1,188 words) - 20:08, 3 January 2024
  • * I tend to read the XEPs before voting on them. * I tend to challenge and propose alternatives when I don't believe a XEP's ready.
    2 KB (423 words) - 11:13, 2 October 2011
  • * I tend to read the XEPs before voting on them. * I tend to challenge and propose alternatives when I don't believe a XEP's ready.
    2 KB (421 words) - 14:22, 15 September 2012
  • * I tend to read the XEPs fairly thoroughly before voting on them. * I tend to challenge and propose alternatives when I don't believe a XEP's ready.
    2 KB (416 words) - 09:27, 13 October 2014
  • * I tend to read the XEPs fairly thoroughly before voting on them. * I tend to challenge and propose alternatives when I don't believe a XEP's ready.
    2 KB (416 words) - 15:42, 25 September 2013
  • The following guidelines are strict rules that need to be read and followed by any user of the jabber.org server and services to be aware ...d that people have good manners, it isn't absolutely necessary for them to read these guidelines. They are informatory and provide us (and you) with rights
    3 KB (526 words) - 20:52, 24 July 2010
  • I tend to read the XEPs before voting on them. I tend to challenge and propose alternatives to when I don't believe a XEP's ready.
    4 KB (763 words) - 12:56, 21 September 2010
  • If you are interested in how I became involved in XMPP, please read my [[Matthew Wild January 2008|initial application]]. In particular my long
    943 bytes (151 words) - 22:39, 6 January 2018
  • ...ated in creating some of the last newsletters by collecting news and proof reading.
    960 bytes (161 words) - 10:37, 20 July 2021
  • ...ticipated in creating some of the newsletters by collecting news and proof reading.
    973 bytes (156 words) - 16:54, 26 July 2023
  • ...ticipated in creating some of the newsletters by collecting news and proof reading.
    973 bytes (156 words) - 20:55, 2 August 2022
  • ...o extend it and give you some clear steps to follow instead of a having to read through a formal specification. # On subsequent messages you have to check if you already have sessions for all device tuples and only query the bundle for missing
    3 KB (548 words) - 12:48, 15 April 2023
  • * Inbox/Unread/Bind2 // INBOX // Reconnection: 19 * Meetups / Sprints are good to spread the hype and generally get received really well on social networks...
    15 KB (1,466 words) - 22:33, 19 February 2020
  • ...ser opens it, they might even be really confused why those messages they alread saw a notification for are not displayed in the app at all). Writing incomi ...each incoming high priority push, even if the push was only for a XEP-0333 read marker).
    6 KB (888 words) - 19:18, 4 February 2023
  • I tend to read the XEPs before voting on them (despite peer pressure not to!). I tend to challenge and propose alternatives to when I don't believe a XEP's ready.
    5 KB (930 words) - 12:03, 30 September 2009
  • To read more thorough on my xmpp history look on user page
    1 KB (182 words) - 00:52, 8 November 2023
  • ...interact with devices a good interface is needed to edit control data and read sensor data to show diagrams of collected data and even to act as a [http:/ ...[http://xmpp.org/extensions/xep-0325.html XEP-0325] creates possibility to read and write fields to IoT devices. To let this create smart services there ne
    8 KB (1,124 words) - 09:34, 23 June 2017
  • To read more thorough on my xmpp history look on user page
    1,021 bytes (182 words) - 20:49, 25 October 2022
  • Kev - You want to forget everything and re-fetch MAM - Almost ready to say Carbons should echo your message ...gs, delivery vs read receipts - Chat markers in MAM? - PubSub node with 'I read up to here' pointers
    3 KB (485 words) - 10:50, 29 May 2015
  • * Read the [https://summerofcode.withgoogle.com/help Google Summer of Code 2022 gu .../help/student-advice Google Summer of Code 2022] are highly recommended to read first.
    16 KB (2,497 words) - 17:25, 6 January 2023
  • If you are interested in how I became involved in XMPP, please read my [[Matthew Wild January 2008|initial application]]. In particular my long
    1 KB (168 words) - 11:03, 22 February 2019
  • Make sure you read the [[Basic communication guide for XMPP techies]] #* Read and validate the content
    3 KB (412 words) - 21:44, 5 January 2021
  • * Read the [https://summerofcode.withgoogle.com/help Google Summer of Code 2023 gu .../help/student-advice Google Summer of Code 2023] are highly recommended to read first.
    17 KB (2,652 words) - 20:55, 14 March 2023
  • I started reading XEPs when I was in the second year of engineering in 2018. Since then in
    1 KB (204 words) - 02:24, 1 December 2020
  • ...t reading AGAIN from the beginning, and NOT JUST from the place where your reading was interrupted, since such a TRANSFORMATION indicates that a correction * sessions are ready
    10 KB (1,588 words) - 21:25, 24 July 2010
  • If you are interested in how I became involved in XMPP, please read my [[Matthew Wild January 2008|initial application]]. In particular my long
    1 KB (178 words) - 21:16, 17 February 2020
  • === PLEASE READ THIS === ...ed that code obscurity does not finally protect against attackers. Further readings on GitHub [https://github.com/schirrmacher/files/blob/master/WhatsApp%2
    15 KB (2,203 words) - 21:08, 29 March 2020
  • ...or a greatly shortened application this year, to try to save everyone time reading it. For those interested, not much is different to http://wiki.xmpp.org/
    1 KB (194 words) - 12:16, 6 February 2015
  • * Dino, Conversations and converse.js send to bare JID already. ==== 1.3 Unread state ====
    10 KB (1,759 words) - 21:34, 3 February 2018
  • I espoused on these themes in two blog posts, if you care to read more:
    1 KB (232 words) - 09:00, 21 February 2019
  • If you are interested in how I became involved in XMPP, please read my [[Matthew Wild January 2008|initial application]]. In particular my long
    2 KB (246 words) - 16:17, 5 January 2015
  • If you are interested in how I became involved in XMPP, please read my [[Matthew Wild January 2008|initial application]]. In particular my long
    2 KB (246 words) - 20:12, 6 February 2014

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