editor July 2024

editor@xmpp.org

1 participants
2 discussions

by John Livingston

Dear Editor Team, Please find bellow an url to a new ProtoXEP (MUC Slow Mode) that I want to submit: https://github.com/JohnXLivingston/xeps/blob/xep-slow-mode/xep-slow-mode.xml As you may have seen, i asked a question on xmpp:xsf@muc.xmpp.org about your policy on using nicknames as author name. John Livingston is actually a nickname (and my official "commercial name" in France), and I don't want to have too obvious public disclosure of the relation between my nickname and my real name. It appears that you have no clear policy about this question (in any case, it seemed to be the subject of debate in the discussion room). In my case, there are multiple ways to check that I am John Livingston (website, PGP key, email, social network accounts, ...), but absolutely no way to check my real name online. In such case, is "John Livingston" acceptable as author name? If not, is there a way to publish as anonymous author? (given all copyright to the XSF if necessary). Best regards, John Livingston

4 months

XEP Fwd: [Standards] Re: Proposed XMPP Extension: Communicate & Ask to AI

by Abdurrahman Eker

Hey list, I think the list will not be updated when I reply to the mail. Could you forward the latest update? kind regards, Abdurrahman ---------- Forwarded message --------- From: Abdurrahman Eker <abdurrahmaneker58(a)gmail.com> Date: Sun, Mar 17, 2024 at 2:04 PM Subject: Re: [Standards] Re: Proposed XMPP Extension: Communicate & Ask to AI To: XMPP Standards <standards(a)xmpp.org> Hey list, I am attaching the update on the issues discussed in the thread. kind regards, Abdurrahman Jonas Schäfer <jonas(a)wielicki.name>, 15 Kas 2023 Çar, 19:25 tarihinde şunu yazdı: > Hi list, hi Abdurrahman, > > On Montag, 30. Oktober 2023 17:15:52 CET kevin.smith(a)isode.com wrote: > > The XMPP Extensions Editor has received a proposal for a new XEP. > > > > Title: Communicate & Ask to AI > > Abstract: > > This document defines a protocol for asking questions to an artificial > > intelligence or requesting it to make predictions. > > > > URL: https://xmpp.org/extensions/inbox/xep-ai.html > > Thank you for your submission, Abdurrahman. > > We discussed this in the Council and I want to share a few suggestions for > improvement with you. > > The mandatory <ai> element, as Nicolas already pointed out, seems like an > odd > requirement: there are already LLM-based entities out there which would > immediately be non-compliant. In adddition, the model selection is > underspecified: How would I know which models are even available at that > particular agent? > > I think it would be better to: > - Specify a new XEP-0030 identity based on the already existing > bot-identity > which identifies an account as a bot. > > This builds on already existing mechanisms, which is always good. > > - Define a XEP-0030 feature or XEP-0128 service discovery extension which > describes the model used by the "AI" account > > This allows clients/users to discover information about the specific > type > of model used, which is useful. > > - Then use separate accounts for different models. > > This is probably debatable; if there is a compelling usecase for > hosting > multiple models on the same account, the model selection could be made > part of > the XEP-0004 form you already suggest in the document. The available > models > could be made part of a XEP-0128 extension, so that clients can basically > just > copy the form over and select a model. > > Other than that, I think this is an acceptable submission. The idea of > passing > along parameters using an embedded form to the model is novel and a good > one > in my opinion. > > kind regards, > Jonas_______________________________________________ > Standards mailing list -- standards(a)xmpp.org > Info: Unsubscribe: %(real_name)s-unsubscribe@%(host_name)s > _______________________________________________ >

8 months, 1 week

2025

2024

2023

editor July 2024 ----- 2025 ----- March 2025 February 2025 January 2025 ----- 2024 ----- December 2024 November 2024 October 2024 September 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 ----- 2023 ----- December 2023 November 2023

editor July 2024