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
Hi Team,
Please find attached our proposal for a new XEP related to post-quantum
encryption.
Please let me know if you have any questions.
We also have a working client-side application implementation of the
protocol described in the draft XEP.
Best regards,
*Jamieson O'Reilly*Founder / CEO
*DVULN Pty Ltd*Level 1, Suite 1A
802-808 Pacific Hwy, Gordon,
<https://maps.google.com/?q=66+Clarence+Street+Sydney+NSW+2000&entry=gmail&s…>
Sydney, NSW, Australia 2072
<https://www.google.com.au/maps/place/802%2F808+Pacific+Hwy,+Gordon+NSW+2072…>
p: +61 405 820 888 <+61405820888>
e: jamieson@ <jamieson(a)dvuln.com>dvuln.com <jamieson(a)dvuln.com>
We are committed to protecting the privacy of the personal information you
may provide to us by ensuring your e-mail address and any other personal
information about you will only be disclosed to relevant staff and
contractors and used for the purpose of responding to a request or to carry
out instructions. We will not sell or give your e-mail address to anyone
else. Please be aware that e-mail is not necessarily secure against
interception so you should only send information necessary for us to
provide you with the assistance you require.
This transmission or any part of it is intended solely for the named
addressee. It is confidential and may contain legally privileged
information. The copying or distribution by any person other than the named
addressee is prohibited.
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
> _______________________________________________
>
Hi all,
I've had a quick cleanup of the roles on GitHub. Jonas and Sam have both
retired from Editorship, so I've removed them. Additionally, Flow, JC
and Martin aren't active in merging people's PRs so on 'least privilege'
I've removed them too (Peter isn't active either, but as he's org admin,
removing him would have little efect, AFAIK). Obviously, any of this is
trivially reversed if someone *is* doing work that needs write to the
repo - please shout if so and I shall place my tail between my legs and
fix it.
/K
Dear Editor,
please note that council has accepted the proposed XEP 'MUC Avatars'
into the historical track.
(A previous submission into standards track has been rejected by the
council at that time)
https://xmpp.org/extensions/inbox/muc-avatars.html
cheers
Daniel